Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 728 of 801  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject
  638   Fri Jul 30 09:15:39 2004 Reply Stefan Rittstefan.ritt@psi.ch   Re: ?cmd=New&pType=PC does not work
> according to the users guide,
> 
> http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC
> 
> should create an entry with the type value set to PC, but this doesn't work

Now it works. Updated elog version under CVS and as a snapshot (see Download Page)
  637   Fri Jul 30 02:03:59 2004 Warning Guenter NowakGuenter.Nowqak@t-systems.at   ?cmd=New&pType=PC does not work
according to the users guide,

http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC

should create an entry with the type value set to PC, but this doesn't work
  635   Wed Jul 28 22:33:08 2004 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.5.3Re: BUG?: Preset text = causes replication of text when re-editing a logbook entry.
> > With the "Preset text = " specified, when re-editing a logbook entry (say to
> > correct a spelling error) the text of the "Message" is replicated and placed
> > directly below the original text.
> 
> That should be fixed since revision 1.370 from Jul 7th, 2004. Please update.

Thanks!
  634   Wed Jul 28 22:32:39 2004 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.5.3Re: Date format problem in "Thread display = "
> > I get the following in my THREADED logbook view:
> > 
> > "Adding new services, planned for 1090519200. Last revised: Thu Jul 15
> > 18:03:52 2004"
> 
> That should be fixed by the current version. Please update.

Thanks!
  633   Wed Jul 28 22:12:03 2004 Reply Todd Corsatcorsa@bnl.govBug reportLinux2.5.3Re: Bugs in newer updates w/ Debian install?
> > I just updated ELOG using the latest elogd.c, and now my Quick Filters seem 
> > to stop working after the first or second filter attempt.
> 
> Can you try if you can reproduce the problem with the current version? I tried
> your settings and could not reproduce it. I remember that I fixed some problems
> with quick filters, but that was some time ago (Apr 04). If the problem
> persists, can you send me your exact elogd.cfg?

Recai Oktas replied to me and let me know that I needed to use dpkg to create the 
new Debian package instead of manually compiling it. I reverted to the original 
Debian package to get everything running normally again, but I haven't had a 
chance to try the upgrade again. As soon as I went back to the original elogd 
everything worked fine (no changes to the elog.cfg required). I'm assuming that 
the problem came from attempting to recompile a Debian package install manually. 
Sorry for the bug scare!

Todd
  632   Wed Jul 28 22:08:16 2004 Agree Steve Jonessteve.jones@freescale.comRequestAll2.5.3Re: WISHLIST: Type <attribute> = user
> Acknowledged. Added your vote to the wishlist.

Thanks!
  631   Wed Jul 28 22:07:31 2004 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.5.4?Re: getcfg problem in v1.410: Truncation of long config strings
> > Just compiled 1.410 and have run into an issue that *may* have been
> > introduced in 1.393.
> > 
> > Config file directives such as "Welcome title" could be very long strings. 
> > After compiling 1.410, our "Welcome title" is truncated and, while I haven't
> > counted the actual chars, I suspect that the truncation happens at 1024
> > characters.  The procedure 'getcfg' has a declared passed paramater "int
> > vsize". 
> 
> Actually before 1.393 you got a buffer overflow if any string in the
> configuration file was longer than 500 chars, so it's a miracle that your elogd
> did not crash on the long Welcome Title. I added the "vsize" parameter to avoid
> such crashes. To satisfy your need for a long Welcome title, I increased the
> string size for that particular case to 10000 chars. Hope this is enough.

Hmmm, it is a wonder.  Our welcome text was not significantly longer (about 20
chars longer) so perhaps . . . ?

Thanks, will recompile and report back.
  630   Wed Jul 28 21:54:36 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.5.4?Re: getcfg problem in v1.410: Truncation of long config strings
> Just compiled 1.410 and have run into an issue that *may* have been
> introduced in 1.393.
> 
> Config file directives such as "Welcome title" could be very long strings. 
> After compiling 1.410, our "Welcome title" is truncated and, while I haven't
> counted the actual chars, I suspect that the truncation happens at 1024
> characters.  The procedure 'getcfg' has a declared passed paramater "int
> vsize". 

Actually before 1.393 you got a buffer overflow if any string in the
configuration file was longer than 500 chars, so it's a miracle that your elogd
did not crash on the long Welcome Title. I added the "vsize" parameter to avoid
such crashes. To satisfy your need for a long Welcome title, I increased the
string size for that particular case to 10000 chars. Hope this is enough.
ELOG V3.1.5-3fb85fa6