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.

Sorting is not something I have to have but it would make the servers names a little easier
to find. However, I can get them into any order I want buy rearranging them in the config
file. I've already done that for some of them. 

Groups on the front page would make navigation easier but it really isn't necessary.

I was hoping their was a way to do this that I had overlooked.


> OK, I'm willing to give a shot but I don't know how to do it. I'll look in the docs and
> see if I can figure it out.  Thanks.
>  
> > Before I go and implement additional features, I would like to check if your problem 
> > cound not be solved easier. Whey don't you define your server as an attribute inside 
> > a logbook instead of having separate logbooks for each server? You know that you can 
> > sort by attributes (just by cliking on the column header for that attribute), so that 
> > would satisfy your need for sorting.

> 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.

What I meant was having only one logbook, and having the server as an attribute like

Attributes = Server, Type, ....
Options Server = Server1, Server2 (just the names of your current logbooks)
...

If you have already 50 logbooks this would require quite some work of course, but it might 
something for the future. I don't know if this fits into your requirements. If not, please 
let me know your complete scheme (current attributes and logbooks), then I can think about.

>   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 
> days.  We first replied to the original thread and then each subsequent 
> reply was a reply of the previous reply.  When the thread reached above 13 
> of these, the elogd.exe would crash everytime a user attempted to select 
> the logbook that contained the enormous thread.  
>   I found the only workaround was to manually delete the offending entry 
> from the log file and to instruct my users to not reply to replies unless 
> absolutely necessary.  I have been able to replicate this error across the 
> rest of my logbooks as well.  If there is any more information you may 
> need, please feel free to contact me.

Sorry my late reply, I was pretty busy these days...

I tried to reporduce your problem, but without success. Have a look at

http://midas.psi.ch/elogdemo/Linux/32

where I replied 20 times producing a very long thread without any problem. So 
can you reproduce your problem? I suspect that there was some other problem, 
since the number of replies is internally not limited in any way. If you 
again get into a situation where elodg.exe crashes on the *DISPLAY* of some 
message, you can send me the offending file xxxxxxa.log directly by email and 
I can analyze it. Only if I can reproduce a problem, I can fix it.

- Stefan

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.

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
entries, though.

After playing around with the compiler option '-gp' and gprof the
problem was found: loc() is called about 18000 times per logbook
access!  (Attached you can find the gprof output.  There might be
other places where to save time: e.g. getcfg().)  The function loc()
calls stat every time to check if the language file was updated and
this takes a long time especially over NFS.

The quick solution for me was to just replace loc() with 'char
*loc(char *orig) {return orig;}'.  Therefore, I cannot use the
localization that I used anymore, which is not a big problem at the
moment.  After that the time to download the default page was only
0.16 s; almost a factor of 30 faster!

I would suggest to only read the language file (AND also the config
file!) once upon startup.  After changing things one has to restart
elogd, which is not so nice, but the long delay is not acceptable.
Another option not to restart elogd is to make elogd respond to a
signal (e.g. kill -HUP) to reread the config and language files.

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 
do is to check for new configuration/language file once every access, not 
once every loc() or getcfg(). I till think about.

Thanks again,

  Stefan

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.

I have
some requests for the Administrator's Guide: "Running elogd under Apache". 
I'm hoping a few little notes will save others the trouble I've gone
through. Neither of these are any fault of elog's or Apache's, but of my own
ignorance. (I am using elog 2.3.9, and Apache 2.something, if that matters)

1) When doing "ProxyPass ..." when setting up elog under Apache, do NOT put
"ProxyRequests On".  This is not needed, if it is enabled and not set up
correctly, it allows spammers to send spam via Apache's proxy.  More
information on this is here: http://www.apacheweek.com/issues/03-07-25,
about halfway down the page, under "Spammers use open Apache proxies"

Even though it doesn't mention ProxyRequests in the guide, I think there
should be a little side note mentioning that "ProxyRequests On" is NOT
needed, because I put it in, thinking it was - I am probably not the only one.

2) I have found that mod_proxy_http.c must be loaded in addition to
mod_proxy.c and mod_alias.c for the proxy to work, otherwise I get a 403
error.  I think this should be mentioned as well.

Thanks, I added a note into the admin guide.