[no subject]

mdhirsch at gmail.com wrote:
> Are you sure it's still running?  I would expect it to die the first
> time it actually tried to print anything out and found that stdout no
> longer existed.  At the least, I'd expect it to hang forever trying to
> find a terminal.  I don't know a way to give it one.

When you log out, don't the children of the login process get killed by 
SIGHUP signals? I thought you had to use "nohup" (or have the program 
handle signals) to prevent this from happening. Do I have a provincial 
world view?

What about running the program with "nohup" and redirecting STDOUT to a 
file? Then you could "tail" the the file across logins.

S

-- 
Stephen Cristol
cristol at emory.edu


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00644" href="msg00644.html">[ale] Shell process control : Manipulating a process after having logged out and then logging in again</a></strong>
<ul><li><em>From:</em> sriad at uab.edu (Aditya Srinivasan)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00657.html">[ale] Java going bonkders</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00659.html">[ale] firefox on Linux questions (middle click close tab)</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00648.html">[ale] Shell process control : Manipulating a process after having	logged out and then logging in again</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00654.html">[ale] Synaptics Mouse pad</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00658"><strong>Date</strong></a></li>
<li><a href="threads.html#00658"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>