Re: Groups on the first page, posted by Stefan Ritt on Sat Oct 25 10:01:14 2003
|
> I don't see anyway to define a log as an attribute. May be I just don't understand
> something. I have more than 50 logs anyway.
|
|
Re: Elogd.exe Crashes When There are too Many Replies to Replies..., posted by Stefan Ritt on Sun Oct 26 17:04:59 2003
|
> We have been using Elog successfully as a shiftlog book for over a month
> now, but I recently ran into an annoying bug, I think.
> We had a thread that was created and was being replied to over several
|
|
Re: Elogd.exe Crashes When There are too Many Replies to Replies..., posted by Stefan Ritt on Tue Nov 11 13:49:50 2003
|
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 be incorporated into the next release. |
speed is very slow if logbook contains many entries, posted by Heiko Scheit on Wed Nov 12 12:25:44 2003 
|
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
|
|
Re: speed is very slow if logbook contains many entries, posted by Stefan Ritt on Wed Nov 12 12:34:02 2003
|
This is a very nice measurement you made and helps me a lot. I will
incorporte your suggestions into the next version. Under Windows however,
there is no -HUP signal, so that won't work for them. But what I can easily
|
|
Update request for Admin Guide, posted by Justin Dieters on Tue Nov 18 23:19:57 2003
|
Heya, I've been using elog for a year or so, with a proxy through Apache,
but recently I've ran into some trouble with my Apache config, where
spammers were using my incorrectly configured proxy to send spam.
|
|
Re: Update request for Admin Guide, posted by Stefan Ritt on Thu Nov 20 17:51:53 2003
|
| Thanks, I added a note into the admin guide. |
|
Re: speed is very slow if logbook contains many entries, posted by Stefan Ritt on Thu Nov 20 17:55:57 2003
|
I implemented the new scheme where
- under Windows, the configuration is only checked once every access
|