Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 601 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject Text Attachments
  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
  
  688   Wed Sep 8 12:19:00 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.5.4-2Re: URL bug in elogd.cfgThis problem has been fixed in revision 1.462   
  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 
  
  696   Wed Sep 8 17:39:43 2004 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.5.4-2Re: URL bug in elogd.cfg> This problem has been fixed in revision
1.462
  
  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
  
  703   Wed Sep 15 07:42:23 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.4Re: too many <table> tags> > > Couldn't one include the extra <table>
tag only when there is really more than
> > > one attribute per line.  All other
  
  717   Sat Oct 9 14:25:23 2004 Warning Mike Stolovemstolove@rogers.comBug reportLinux2.5.4-5deleting the sole single entry in log causes crash with xreallocWhen creating new logbooks, I will create
a single entry to test the  
configuration. After revising the configuration
  
ELOG V3.1.5-3fb85fa6