> Ah, you test me!  Perhaps I will attempt to dig into this but I may have to leave the
> integration up to you, Stefan.  Seems that there would be two roads to go:
> 1> Move away from standalone and start to rely on Apache
> 2> Continue with the standalone theme and build in LDAP authentication (which could
> also give you groups functions as well). 
> 
> I think I would opt for <2>

<1> would only make sense if the functionality could be completely implemented inside
Apache, without (much) modification of elog. Otherwise I agree that <2> would be more
following the general lines of elog. I was considering to implement PAM (pluggable
authorization module) support into elog, which is quite easy to implement and gives you
to power of having LDAP, Kerberos, Unix username, Windows NT Domain and much more. But
that would them be restricted to elog running under Linux (and Solaris I guess), since
I'm not aware of a PAM implementation under Windows.

Implementing LDAP directly into elog gives me the problem that we don't use LDAP
authentication at our institute (it's Kerberos in fact). So I would have to set up my own
LDAP server for testing, plus we at our institute don't have a direct benefit from that,
which would make it hard for me to justify to spend time on.

> I think you should be using tcp_hostname instead of gethostname if it is 
> specified.

Sorry my late reply, I was ill for some time. I implemented your suggestion in
revision 1.522 which is available from CVS.

Note that there is also the "URL = xxx" option in the configuration file which
lets you specify the whole URL including the host name.

> I happened to find something interesting when trying my perl script. it hangs the
> elog system with hand-crafted http header.

This bug has been fixed in revision 1.524 of elogd.c available from CVS.

Ok, I changed that in version 2.5.5-3. Note that one can also use the "elog:..."
substitution, like

Display ThisURL = elog:$logbook/$message id

> Could you implemet and option 'admin menu' which gets displayed
> when an 'admin' is logged in.  This menu could e.g. also include 'Delete'
> while the normal menu would not.

You can achieve the same via

Allow delete = <admin name>

Thanks, the file will be contained in the next release.

> The <pubDate> item doesn't appear to be a valid RFC-822 date.  Causes some
> aggregators to fail when parsing.

I fixed that, now it passes the Feedvalidator. New version is under CVS.

> Have set up 3 top level groups, each with their own password file.
> Ever since users have to 'login' twice to get to the appropriate elog.
> You click on top level group, get to log book and click on the one you want 
> and get login/password dialog box, click ok and and you get it again and 
> then you finally get into the elog book.
> 
> Anything I can check on this behavior?

Sorry my late reply, was very busy these days... (;-) Can you send me your
elogd.cfg so that I can see how you defined your groups?

- Stefan