<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=598222815-17032004><FONT face=Arial color=#0000ff
size=2>All,</FONT></SPAN></DIV>
<DIV><SPAN class=598222815-17032004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=598222815-17032004><FONT face=Arial color=#0000ff size=2>If you
have ssh'd from machine1 to machine 2, t</FONT></SPAN><SPAN
class=598222815-17032004><FONT face=Arial color=#0000ff size=2>here is a way to
get out of the session on machine 2, but it is brutal. Use the interrupt
built into SSH ~. (tilde dot)</FONT></SPAN></DIV>
<DIV><SPAN class=598222815-17032004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=598222815-17032004><FONT face=Arial color=#0000ff
size=2>L.</FONT></SPAN></DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
Alexei_Roudnev@exigengroup.com [mailto:Alexei_Roudnev@exigengroup.com]
<BR><B>Sent:</B> 15 March 2004 23:32<BR><B>To:</B> Osiris
Developers<BR><B>Cc:</B>
osiris-devel-bounces+alexei_roudnev=exigengroup.com@lists.shmoo.com;
osiris-devel@lists.shmoo.com<BR><B>Subject:</B> Re: [osiris-devel] Bug:
osirisd 3.0.4 does't daemonize correctly...<BR><BR></FONT></DIV><BR><FONT
face=sans-serif size=2>I saw it in 2.2.0 and I was sure that problem was
resolved. </FONT><BR><BR><FONT face=sans-serif size=2>Temporary
solution:</FONT> <BR><BR><FONT face=sans-serif size=2>(1) NEVER start and stop
daemons by this way, do it by running /etc/init.d/daemon start or ...
stop</FONT> <BR><FONT face=sans-serif size=2>/File name depends, of
course/</FONT> <BR><BR><FONT face=sans-serif size=2>(2) In this init file,
use 'nohup' or some other method to get rid of the control
terminal.</FONT> <BR><BR><FONT face=sans-serif size=2>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 face=sans-serif size=2>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 face=sans-serif
size=2> <BR>Alex Roudnev<BR>Exigen Group <BR></FONT><BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<TD><FONT face=sans-serif size=1><B>"Yazz D. Atlas"
<yazz@osdn.com></B></FONT> <BR><FONT face=sans-serif size=1>Sent
by:
osiris-devel-bounces+alexei_roudnev=exigengroup.com@lists.shmoo.com</FONT>
<P><FONT face=sans-serif size=1>03/15/2004 03:07 PM</FONT> <BR><FONT
face=sans-serif size=1>Please respond to Osiris Developers</FONT>
<BR></P>
<TD><FONT face=Arial size=1> </FONT><BR><FONT
face=sans-serif size=1> To:
osiris-devel@lists.shmoo.com</FONT> <BR><FONT
face=sans-serif size=1> cc:
</FONT> <BR><FONT face=sans-serif size=1>
Subject: [osiris-devel] Bug:
osirisd 3.0.4 does't daemonize
correctly...</FONT></TR></TBODY></TABLE><BR><BR><BR><FONT face="Courier New"
size=2>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></BLOCKQUOTE></BODY></HTML>