> Hello Folks,
> 
> Found an interesting problem with 2.3.7 under redhat 9.0 linux.
> 
> When you take the elogd.cfg file and the menu commands = <list> and guest 
> menu commands = <list>, the config menu for edit the elogd.cfg stops 

are you logged
if you have a guest menu there is no access in the admin
access is restricted with 
Admin user = 'your login name' 
in Global section



> working, yet if I change the URL manually, I can still get to the file 
and 
> the menus do not change.  If I delete all menu commands, then all works 
> without errors, yet the menus do not match default.
> 
> Also, the self registration function equal to 3 does not always send 
email.

it is send to the admin user list
be sure that smtp parameter is ok

> 
> Cheers,
> Roberto

does anybody has interest with a full synchronisation 
between elog logbook
on mySQL and SQL database

> I guess this question got somehow lost.
> So once again : Is there a possibility to EDIT an existing message with 
> elog.exe ?

This message did not get lost, but I'm on a conference right now in Elba and 
will come back next week, when I have time to answer all questions. Only so 
much for now: Editing in elog.exe is right now not implemented, but I will 
put it on the wishlist.

- Stefan

Used to deny a certain command to a list of users. This can be used to 
deny a guest user to enter new messages or modify a message. 


Hosts allow = <list> 
Hosts deny = <list> 

could you deny guest user like this 

guest is not loggeg ?
hubert is logged

Hosts deny = guest,hubert
does anybody has experience with deny based on IP adresse ?

> I guess this question got somehow lost.

Got not lost, but I was on two consecutive conferences and just returned.

> So once again : Is there a possibility to EDIT an existing message with 
> elog.exe ?

Not at the moment. But I will put it on the wishlist.

I was wondering if there is a way to have a more detailed log of users' 
activities?
Current Logfile = <file> gives a good base for information about 
logins/access to 'protected' logbooks. 

What we would like to have is information about when a user reads an ELOG 
entry (to be able to determine the reaction/response time). 

For instance the LOG could look sg like this: 
%%user %%datetime %%logbook %%record read/edit/new/delete 

> Used to deny a certain command to a list of users. This can be used to 
> deny a guest user to enter new messages or modify a message. 
> 
> 
> Hosts allow = <list> 
> Hosts deny = <list> 
> 
> could you deny guest user like this 
> 
> guest is not loggeg ?
> hubert is logged
> 
> Hosts deny = guest,hubert
> does anybody has experience with deny based on IP adresse ?

You probably mixed up deny of a command to a certain user and deny of hosts 
based on their IP. This has nothing to do with each other except the 
word "deny". Please read the documentation about how to set up IP 
based "hosts deny". This works only for certain IPs, but not for certain 
users. 

If you want guests not to be able to enter messages, but allow this to 
registered users, you should set up a password file, and a guest menu. 
Please refer to the elogd.cfg file for this forum which is done in this way. 
Have a look at elog:Config%20Examples/4 .

> When you take the elogd.cfg file and the menu commands = <list> and guest 
> menu commands = <list>, the config menu for edit the elogd.cfg stops 
> working, yet if I change the URL manually, I can still get to the file and 
> the menus do not change.  If I delete all menu commands, then all works 
> without errors, yet the menus do not match default.

There was a recent bug which made "Edit elog.cfg" stop working if the 
language is not English. This has been fixed and the update is in CVS. If 
you use English, this might be another problem. Can you send me your 
complete elogd.cfg so I can try to reproduce your problem?

> Also, the self registration function equal to 3 does not always send email.

"Not always" is hard to understand. Either it works or it does not for a 
certain configuration. What you can do is start elogd with the "-v" flag, 
which outputs all communication to the console window. Among this 
information, you have the communication with the SMTP server when sending an 
email. Maybe you see some problem there which only sometimes occurs (like 
wrong email addresses or so...)