Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 693 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded  Show all entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 692, 693, 694 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject Text Attachments
  477   Mon Feb 16 16:47:55 2004 Question Stefan Rittstefan.ritt@psi.ch Linux2.5.0Re: -W -Wall options (using gcc)> Have a look at the gcc info pages:
> 
> $ info gcc "invoking gcc" "warning options" 		  
  478   Mon Feb 16 17:18:39 2004 Question Heiko Scheith.scheit@mpi-hd.mpg.de Linux2.5.0Re: -W -Wall options (using gcc)> > Have a look at the gcc info pages:
> > 
> > $ info gcc "invoking gcc" "warning options" 		  
  479   Wed Feb 18 16:54:27 2004 Angy Heiko Scheith.scheit@mpi-hd.mpg.deBug reportLinux2.5.0elogd does not exit on SIGTERMWhen trying to stop elogd processes with the
kill command
elogd exits only after access to the logbook. 		  
  480   Thu Feb 19 09:38:13 2004 Angy Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.0Re: elogd does not exit on SIGTERMNoee. Here it works immediately.

Can you try with a fresh server from the		   
  678   Fri Aug 27 00:49:27 2004 Angy Heiko Scheith.scheit@mpi-hd.mpg.deBug reportLinux2.5.0Re: elogd does not exit on SIGTERM> Noee. Here it works immediately.
> 
> Can you try with a fresh server from the		   
  695   Wed Sep 8 17:38:54 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.0Re: elogd does not exit on SIGTERM> elogd does not exit if there is an 'unprocessed'
HUP.  So when you do 
>  		  
  697   Wed Sep 8 23:03:36 2004 Reply Heiko Scheith.scheit@mpi-hd.mpg.deBug reportLinux2.5.0Re: elogd does not exit on SIGTERM> > elogd does not exit if there is an 'unprocessed'
HUP.  So when you do 
> >  		  
  699   Thu Sep 9 21:40:47 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.0Re: elogd does not exit on SIGTERM> kill -HUP <pid>; sleep 2; kill <pid>

Thanks, I could reproduce the problem. It		   
Goto page Previous  1, 2, 3 ... 692, 693, 694 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6