<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 13: process ID
</title><link>https://sourceforge.net/p/explab/feature-requests/13/</link><description>Recent changes to 13: process ID
</description><atom:link href="https://sourceforge.net/p/explab/feature-requests/13/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 15 Oct 2002 15:44:01 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/explab/feature-requests/13/feed.rss" rel="self" type="application/rss+xml"/><item><title>process ID
</title><link>https://sourceforge.net/p/explab/feature-requests/13/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be nice, if one could figure out the PID of a&lt;br /&gt;
running experiment (labrun with --batch), in case one&lt;br /&gt;
wants to kill the program. &lt;br /&gt;
Perhaps a PID of the labrun process could be enough.&lt;br /&gt;
But&lt;br /&gt;
I am not sure whether killing the labrun is enough to&lt;br /&gt;
kill&lt;br /&gt;
the process.&lt;br /&gt;
Figuring out the PID of the experiment could be&lt;br /&gt;
difficult,&lt;br /&gt;
if not impossible (labrun labmex runsave.py ...).&lt;br /&gt;
But anyway, it should be easy to guess the right PID &lt;br /&gt;
of the experiment from the PID of the labrun.&lt;br /&gt;
Idea: additional file: {basefilename}.id holds the ID&lt;br /&gt;
of the&lt;br /&gt;
parent process (hopefully you can guess the right&lt;br /&gt;
subprocess&lt;br /&gt;
from that). The file is removed after completion.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Polzin</dc:creator><pubDate>Tue, 15 Oct 2002 15:44:01 -0000</pubDate><guid>https://sourceforge.netaa498b8ab6d004cb64e6cf72df4779895f0bbe8b</guid></item></channel></rss>