Unfortunately I don't have access to a FreeBSD box so I cannot try. But I 
thought the GNU make is the same on Linux and FreeBSD??? 

Has anybody successful compiled under FreeBSD?

- Stefan

> I would very much like to list groups instead of the individual logs on the
> firs page you see after login.
> 
> Is there a way to do this? 

What would you like to see exactly?

a) Only groups. When you click on a group, you are taken to the first logbook 
in that group

b) Only groups. When you click on a group, a secondary page shows up showing 
a logbook selection page from that group

c) Two colums: First column group, second colum logbook, a bit like a 
directory structure like:

  Demo
    Linux
    Database
  Discussion
    Forum
    Archive
    Config Examples
    Contributions

Other uses might also vote...

- Stefan

> I think I would like: Only groups. When you click on a group, a secondary page
> shows up showing logs in that group. 
> 
> I would also have the option to list all logs so you could see logs that are not
> in a group or locate a log where you didn't know what group it was in. I would
> also like to have the option to sort logs and groups.
> 
> I am using Elog to keep track of application servers. The log names are the server
> names and they are grouped by application. The list on the first page is getting
> very long.

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

> impossible to create the moptions with 
> 
> -a Type#0="%D1%"
> -a Itel#0="%zItel%"
> 
> the variable are set to 
> set D1=Tel
> set zItel=Tel.gif
> 
> other standard option work fine

Sure it works. But in your elogd.cfg, you have ROptions, not MOptions! I 
changed this to 

...
IOptions Itel = Tel.gif, TelDirect.gif, Fax.gif, Gsm.gif, Tel2.gif, 
TelHome.gif,TelFax.gif,TelHelp.gif
MOptions Type = Tel,TelDirect,Fax,Gsm,Tel2,Home,Combine,TelHelp
...

Then I added a batch file elog_submit.bat with following contents:

elog -h 'my site elo' -p 83 -l 'my logbook' -a Phone=%1 -a Contact="%2 %3" -a 
Type#0="%TYPE% -a Cat="%4" -a Itel#0="%ITEL%" %5 %6 %7

Then I made a 

set TYPE=Tel
set ITEL=Tel.gif

and a 

elog_submit 123 a b CAT Test Message

ans all worked fine. Please change your ROptions to MOptions and try again.