> Is is possible to postdate the Entry Date for an entry?
> 
> The documentation lists the ability to forward date an entry, but I don't 
> see any ability to backdate an entry (edit the date to a date in the past).
> 
> Given that the entry date is part of the logbook entry file structure, it 
> wasn't obvious how to make this change.

The date is part of the logbook entry file structure because it's considered 
as a "stamp" which cannot be changed, so to document the real date when the 
message was written. In some installations this is very important.

If you need to change the date more freely, I would recommend to add another 
attribute which can be changed at will. Up to now this has to be a string 
variable so users have to make sure to enter the date in proper format, but 
you can prepopulate that with the current date like:

Attributes = Author, ..., Real date
Preset Real date = $date

This way the current date occurs in that field, but can be changed 
(backdated).

Note that the entry date can be changed directly in the YYMMDDa.log files in 
the data directory, if one has write access there and the elogd daemon is not 
running.

Hi Stefan,

I have a question concerning the Email notification in ELOG.

I have been testing various combinations of the parameters you describe in 
your documentation :

Email <attribute> <value> = <list> 
Use Email Subject = <string> 
Use Email From = <string> 
Omit Email To = 0|1 
Suppress Email to users = 0|1 

And I have encountered a problem using the Email <attribute> <value> = 
<list>. While this works fine for me when the <attribute> is of a type 
textfield, Options or ROptions, I don't seem to be able to have it working 
for the MOptions <attribute> = <list>.

The aim is to have an email notification sent only to selected people 
instead of everybody. I was hoping that this would work :

[MyLogBook]
MOptions Message_To = NB,LW,EC,MD,CD,TV,AH,TR,JS
...
...
Suppress Email to users = 1
Email Message_To TR = tomas@mba.be
Email Message_To EC = etienne@mba.be
...
...

Of course, the tricky part is that it is "multiple choice" so any 
combination of recipients is possible.

Am I missing something? 
Thanx for any ideas how to solve this,

Tomas

This problem has been fixed as well (elog:233).

Dear Friends,

Anyone managed to compile elog on AIX 5.2 or 5.1 ... is there a binary 
anywhere?

new to "C"

kind regards Aamir

When I use the <Login user => option to specify what users I want to be 
able to login into the different logbooks it does not seem to work.  Is 
there something else you are supposed to do to restrict what logbooks users 
can log into?

> When I use the <Login user => option to specify what users I want to be 
> able to login into the different logbooks it does not seem to work.  Is 
> there something else you are supposed to do to restrict what logbooks users 
> can log into?

First, you need version 2.3.4 or later, second, you need a "password file = 
xxx" entry in your elogd.cfg to turn on user-level password access. If both 
is true and you still don't succeed, send me your elogd.cfg.

- Stefan

> > When I use the <Login user => option to specify what users I want to be 
> > able to login into the different logbooks it does not seem to work.  Is 
> > there something else you are supposed to do to restrict what logbooks 
users 
> > can log into?
> 
> First, you need version 2.3.4 or later, second, you need a "password file = 
> xxx" entry in your elogd.cfg to turn on user-level password access. If both 
> is true and you still don't succeed, send me your elogd.cfg.
> 
> - Stefan

Ok, I installed the latest version and this is fixed.  Thanx!

Hi,

I am new to elog so please bear with me if this sounds like a stupid
question... 

I would like to run elogd under Apache because I don't want to open another
port (eg. 8080) on the firewall for incoming http traffic. I followed the
special instructions for that sort of setup but the user logon screen always
comes up again, even after using a valid username/password.

I am testing on a Redhat 7.2 based distribution (called SME server) in a
test domain (tuxhome.co.nz). 
"Apache modules mod_proxy.c and mod_alias.c are activated", Yes.
There seems to be a problem here with the Apache Redirect statement. When I
try with
Redirect permanent /elog http://www.tuxhome.co.nz/elog/
ProxyPass /elog/ http://www.tuxhome.co.nz:8080/
Mozilla responds "Redirection limit for this URL exceeded" and IE6 says
"cannot find server or DNS error" so I have commented out the redirect
statement for now.
I might misunderstand the required URL statement in elogd.cfg 
"URL = http://your.proxy.host/subdir/" ?
which I understand it would have to be 
URL = http://www.tuxhome.co.nz/elog/ for my above example?

Maybe someone could help me with an example that includes all 3 of the
statements together, the redirect + proxypass from httpd.conf plus the URL
from elogd.conf?
Thanks for any help.

Michael