Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 746 of 796  Not logged in ELOG logo
ID Datedown Icon Author Author Email Category OS ELOG Version Subject Text Attachments
  452   Tue Nov 18 23:19:57 2003 Warning Justin Dietersenderak@yahoo.comCommentLinux2.3.9Update request for Admin GuideHeya, I've been using elog for a year or so,
with a proxy through Apache,
but recently I've ran into some trouble with
  
  451   Wed Nov 12 12:34:02 2003 Reply Stefan Rittstefan.ritt@psi.chBug fixLinux2.3.9Re: speed is very slow if logbook contains many entriesThis is a very nice measurement you made and
helps me a lot. I will 
incorporte your suggestions into the next
  
  450   Wed Nov 12 12:25:44 2003 Warning Heiko Scheith.scheit@mpi-hd.mpg.deBug fixLinux2.3.9speed is very slow if logbook contains many entriesThis is not really a bug, but elogd was getting
really slow with our
logbook.  It took about 4 1/2 seconds just
 gmon.txt 
  449   Wed Nov 12 07:52:45 2003 Question Etienne Van Caillieetienne.vancaillie@mba.beBug reportWindows12/7/2003elog.exe impossible to create the moptions with 

-a Type#0="%D1%"
  
  448   Tue Nov 11 13:49:50 2003 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.3.9Re: Elogd.exe Crashes When There are too Many Replies to Replies...I found a stack overflow if there are too
many replies. This has been fixed in 
the current CVS verson of elogd.c and will
  
  447   Tue Oct 28 22:40:28 2003 Agree Glevineg@med.govt.nzCommentOtherelog2.3.9Re: FreeBSD InstallThanks for that mate, compiled elog on FreeBSD
5.1 myself no problems just like 
you said, great!
  
  446   Sun Oct 26 18:32:17 2003 Reply Dave Truesdelldavet@ttfn.comCommentOtherelog2.3.9Re: FreeBSD Install> I got elog 2.3.9 running on FreeBSD 5.1
successfully,
> I compiled elog on a redhat box and then
  
  445   Sun Oct 26 17:04:59 2003 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.3.9Re: Elogd.exe Crashes When There are too Many Replies to Replies...>   We have been using Elog successfully as
a shiftlog book for over a month 
> now, but I recently ran into an annoying
  
ELOG V3.1.5-2eba886