Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 534 of 808  Not logged in ELOG logo
icon4.gif   not proper HTML, posted by Heiko Scheit on Thu Jul 31 16:02:41 2003 

I just upgraded from 2.3.5 to 2.3.9.
icon4.gif   problem with boolean attributes, posted by Heiko Scheit on Fri Aug 1 13:18:42 2003 elog.diff
Boolean attributes were not displayed correctly in version 2.3.9.
Patch is attached.
icon4.gif   width of the textarea is too large (after reply), posted by Heiko Scheit on Mon Aug 4 14:02:52 2003 
The width of the textarea after pressing reply is too large. 
The problem is that the algorithm that searches for the longes line
looks for the next '\r' which it does not find and therefore takes the
icon4.gif   speed is very slow if logbook contains many entries, posted by Heiko Scheit on Wed Nov 12 12:25:44 2003 gmon.txt
This is not really a bug, but elogd was getting really slow with our
logbook.  It took about 4 1/2 seconds just to get the default page in
threaded mode with 15 entries.  The logbook has in total about 2000
icon8.gif   segmentation fault, posted by Heiko Scheit on Fri Feb 13 12:18:19 2004 

Around line 2240 (in loc()) in elogd.c the following is written, 
which results in an infinite loop, since loc() recursively with
icon8.gif   elog (not elogd) submit does not work anymore, posted by Heiko Scheit on Fri Feb 13 12:21:25 2004 
Somehow elog does not use the -s option (subdir) anymore,
resulting in a 'HTTP/1.1 404 Not Found' error.
icon4.gif   -W -Wall options (using gcc), posted by Heiko Scheit on Fri Feb 13 12:25:15 2004 

Maybe consider using the options -W -Wall when compiling elogd.
There are several warning messages.
    icon5.gif   Re: -W -Wall options (using gcc), posted by Heiko Scheit on Mon Feb 16 16:40:50 2004 
> So I fixed all compiler generated warnigns except these:

> [midas@pc2075 ~/elog]$ gcc -g -O -W -Wall -o elogd src/elogd.c
ELOG V3.1.5-3fb85fa6