Re: Ignoring SIGHUP when becoming a daemon?

From: James Carlson (james.d.carlson_at_sun.com)
Date: 05/23/03 

Date: 23 May 2003 10:00:27 -0400

Rich Teer <rich.teer@rite-group.com> writes:
> So, once a daemon has called setsid() (and therefore lost its
> controlling terminal), the other processes will NOT be sent a
> SIGHUP.

Yep. This may well be corrected in the next edition. ;-} 

-- 
James Carlson, Solaris Networking         <james.d.carlson@east.sun.com>
Sun Microsystems / 1 Network Drive         71.234W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.497N   Fax +1 781 442 1677

Relevant Pages

  • Re: Ignoring SIGHUP when becoming a daemon?
    ... Rich Teer writes: ... once a daemon has called setsid() (and therefore lost its ...
    (comp.unix.solaris)
  • Re: daemon helper
    ... You need fork() and setsid() to start a daemon. ... I use dh to start shell and perl scripts which read FIFOs fed by syslog. ...
    (comp.lang.awk)
  • Re: daemon helper
    ... You need forkand setsid() to start a daemon. ... As the wikipedia "daemon" article explains, there is common setup code ... I use dh to start shell and perl scripts which read FIFOs fed by syslog. ...
    (comp.lang.awk)
  • Re: Who sends SIGHUP ?
    ... Sven Mascheck wrote: ... that) and because the `daemon' program loses his control TTY I ... The latter supposition I proved by putting setsid() in the ...
    (comp.unix.misc)
  • Re: Daemon Questions
    ... >> Does the proceedure for daemon mode and running as a foreground process ... you should also include a call to setsid(). ... for daemon initialization and for running as a foreground process. ...
    (comp.os.linux.development.apps)