Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon8.gif   elogd does not exit on SIGTERM, posted by Heiko Scheit on Wed Feb 18 16:54:27 2004 
    icon8.gif   Re: elogd does not exit on SIGTERM, posted by Stefan Ritt on Thu Feb 19 09:38:13 2004 
       icon8.gif   Re: elogd does not exit on SIGTERM, posted by Heiko Scheit on Fri Aug 27 00:49:27 2004 
          icon2.gif   Re: elogd does not exit on SIGTERM, posted by Stefan Ritt on Wed Sep 8 17:38:54 2004 
             icon2.gif   Re: elogd does not exit on SIGTERM, posted by Heiko Scheit on Wed Sep 8 23:03:36 2004 
                icon2.gif   Re: elogd does not exit on SIGTERM, posted by Stefan Ritt on Thu Sep 9 21:40:47 2004 
Message ID: 678     Entry time: Fri Aug 27 00:49:27 2004     In reply to: 480     Reply to this: 695
Icon: Angy  Author: Heiko Scheit  Author Email: h.scheit@mpi-hd.mpg.de 
Category: Bug report  OS: Linux  ELOG Version: 2.5.0 
Subject: Re: elogd does not exit on SIGTERM 
> Noee. Here it works immediately.
> 
> Can you try with a fresh server from the distribution, with the example 
> elogd.cfg, to see if there is any difference?
> 
> The killing is handled in the funciton ctrlc_handler(), which sets _abort = 
> TRUE. This  is checked in line 16195, just after the select(), and the main 
> loop is exited. The select finishes after one second, although I believe 
> that the kill signal also terminates the select prematurely. The kill 
> command and a Ctrl-C keystroke should work the same way, they both generate 
> a SIGTERM or SIGINT signal.

elogd does not exit if there is an 'unprocessed' HUP.  So when you do 

kill -HUP <pid>
kill <pid> 

elogd will only exit after it was accessed.
ELOG V3.1.5-fe60aaf