<br><font size=2 face="sans-serif">I saw it in 2.2.0 and I was sure that problem was resolved. </font>
<br>
<br><font size=2 face="sans-serif">Temporary solution:</font>
<br>
<br><font size=2 face="sans-serif">(1) NEVER start and stop daemons by this way, do it by running /etc/init.d/daemon start or ... stop</font>
<br><font size=2 face="sans-serif">/File name depends, of course/</font>
<br>
<br><font size=2 face="sans-serif">(2) In this init file, use 'nohup' or some other method to get rid of the control terminal.</font>
<br>
<br><font size=2 face="sans-serif">OR - don't login as a root, login as a user and then 'su' or 'sudo'. (signal, sent by user, can not kill root process).</font>
<br>
<br><font size=2 face="sans-serif">It is well known problem with many daemons, caused by SIGHUP signal and some other issues, when control terminal is closed.</font>
<br>
<br><font size=2 face="sans-serif"> <br>
Alex Roudnev<br>
Exigen Group <br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Yazz D. Atlas" <yazz@osdn.com></b></font>
<br><font size=1 face="sans-serif">Sent by: osiris-devel-bounces+alexei_roudnev=exigengroup.com@lists.shmoo.com</font>
<p><font size=1 face="sans-serif">03/15/2004 03:07 PM</font>
<br><font size=1 face="sans-serif">Please respond to Osiris Developers</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: osiris-devel@lists.shmoo.com</font>
<br><font size=1 face="sans-serif"> cc: </font>
<br><font size=1 face="sans-serif"> Subject: [osiris-devel] Bug: osirisd 3.0.4 does't daemonize correctly...</font></table>
<br>
<br>
<br><font size=2 face="Courier New">Since playing around with Osiris lately I found an item I think is a <br>
bug. Ssh into a system and stop osirisd by hand and them restart it <br>
using the command bellow. Now try to exit that ssh session, it just hangs.<br>
<br>
( example of what I'm talking about )<br>
<br>
# /usr/local/sbin/osirisd -r /usr/local/osiris/<br>
# exit<br>
logout<br>
(just hangs here)<br>
<br>
You might want to look at the following URL for some code to solve this. <br>
(I'm not a programmer so forgive me if I can't submit my own patch)<br>
<br>
http://www.erlenstar.demon.co.uk/unix/faq_2.html#SEC16<br>
<br>
(cut and pasted from above URL)<br>
<br>
A daemon process is usually defined as a background process that does <br>
not belong to a terminal session. Many system services are performed by <br>
daemons; network services, printing etc.<br>
<br>
Simply invoking a program in the background isn't really adequate for <br>
these long-running programs; that does not correctly detach the process <br>
from the terminal session that started it. Also, the conventional way of <br>
starting daemons is simply to issue the command manually or from an rc <br>
script; the daemon is expected to put itself into the background.<br>
<br>
<br>
-- <br>
Yazz D. Atlas <yazz@osdn.com> Voice: 408-802-9608 (cell)<br>
Senior Systems Engineer / Senior BOFH Fax: 510-226-8814<br>
[ O | S | D | N ] Open Source Development Network / VA Software<br>
http://www.osdn.com 47071 Bayside Parkway Fremont, CA 94538<br>
AIM:"Entropy Works 42" IRC:"Aaton irc.slashnet.org" ICQ:"11445680"<br>
gpg --keyserver wwwkeys.pgp.net --recv-key 0x0C57DDA0<br>
GPG: 644C E9FF D0AF 3C5E 5C73 5E05 00EF C7EC 0C57 DDA0<br>
_______________________________________________<br>
osiris-devel mailing list<br>
osiris-devel@lists.shmoo.com<br>
https://lists.shmoo.com/mailman/listinfo/osiris-devel<br>
</font>
<br>
<br>