First thing we have been using the Elog for 2 yr for a shift carryover and it has works out great.

Now for the problem I have. I heave the message width set to 80.  It works for plain Encoding but it does not work for HTML or ELCode. The text does not wrap around when viewing using Explorer or Fire Fox or printing out the Elog.  Is this a problem or do I need to modify the Config file?

Thanks

That is the the problem the text does not resize with the window or sending to the printer.

I went to upgrade to the new version of elog I receive a error message that is.

error: Failed dependencies:
	libssl.so.6 is needed by elog-2.7.5-1.i386
	rtld(GNU_HASH) is needed by elog-2.7.5-1.i386

Do I need these dependencies for elog to work? If I do need them where do I get them for Suse 10.2.

Thank you for any help.

Carl

error: Failed dependencies:
	libssl.so.6 is needed by elog-2.7.5-1.i386
	rtld(GNU_HASH) is needed by elog-2.7.5-1.i386

 Thank you

I will look into it.

Carl

Hi, 
I also have this problem, when a non admin user logs in he does not have access to
the config file but if he logs out he can then access the config file as non logged
user.
I also tried to upgrade to version 2.5.3 but running under this version does not ask
for passwords so I reverted to 2.5.2.

Besides these few details, your software is great !

Thank you,

Alexandre

> > For some reason if I define a "login user" that is allowed the configure
> > option he is also allowed to change the configuration file. According to the
> > documentation it seems like this should NOT be the case. Any ideas as to
> > what the problem might be? 
> 
> Unfortunately I cannot reproduce your problem. This leaves few possibilites:
> 
> - any login user CAN change his/her full name, email address etc. but only admin
> users can change ALL OTHERS as well. Admin users should see a "change elogd.cfg"
> button on the config page, whil normal users will not
> 
> - are you sure you logged out as admin user and loggin in again as non-admin
> user? Under some circumstances, the browser keeps old cookies which can confuse
> things. Best is if you delete all browser cookies and try again (Tools/Internet
> Options/Delete Cookies in IE).
> 
> - Stefan

Dear Stefan,
I eventually tried the latest version from the CVS. 
And it is odd because like when I tried version 2.5.3, it is like it ignores
the passwd file. I guess I must have a problem in my cfg file.
So I can't really test if 2.5.3 or 2.5.4 have the same problem.

Right now I'm still using 2.5.2 which works fine, if i log out and click on
the logbook tab. I get the page which ask for the username and password. The
thing is I don't get returned to the username/password when I hit log out. I
arrive in the state you can see in the unlogged.jpg.
From here if can go into all the logbooks as long as I don't hit the
logbooks tab and worse I can access to all the config files.

Is there something really badly configured in my config file ? I guess it is
not supposed to work that way.

Thank you,

Alexandre

The elogd.cfg is attached in the previous message as attachement 3. Sorry it is a
little bit buried between pictures.
The reason I put the picture of the global elogd.cfg is to show that the not logged
user has access to elogd.cfg which is some kind of trouble...

> I just see your [global] part of elogd.cfg, could you send me the complete file?
> 

Hi I tried to remove the cookies and it still did not ask for password under 2.5.4.
Has the password file format changed between 2.5.2 and 2.5.3 ?

> What you also could try is to delete all cookies stored in your browser. The way
> cookies are formed changed between 2.5.2 and 2.5.3, so the system could be
> confused by old cookies.
> 
> - Stefan

Thank you, I misunderstood how the "Guest menu commands" worked I thought I had to specify
a limited set of commands to actually limit guest users.

Thanks again for your wonderful work on this program too.

Regards,

Alexandre

> Ok, now I see your problem. You defined a "Guest menu commands" which explicitly allows
> not-authorized access (that's what it's for). If you only want to allow authorized
> access, remove the "guest menu commands" from the logbook sections and also from the
> [global] section.
> 
> Please note that if an option is not preent in a logbook section, it is looked for in
> the [global] section. I see that most of your logbooks have similar settings. Just put
> them into the [global] section, and override it in the logbook section if they are
> different.