According to section "Syntax of elogd.cfg" of the "Administrator's Guide" Options <attribute> = <list> and  ROptions <attribute> = <list> should be the same. But there is a litle difference, because choosing an entry of the Options-pull-down menu causes a reload of the entry mask while choosing a ROption-radio-button the entry mask is not reloaded. This causes a problem using conditional attributes. The condition is only paid attention to in case of Options but not in case of ROptions. In my case I would like to use ROption, as it is faster to set a radio button than to choose an item in a pull-down menu, but I can't as I have also to use conditional attributes. Is there any solution?

Hello @all,

for a logbook I have also to set up a guest access. As I want to have a login page first opening the logbook,  I created a second logbook entry in the elog.cfg that points to the same subdir as the original logbook. The idea of this guest access is, that users who have no login rights can read selected items with selected attributes. Therefor I restricted the guest account with all available "Guest"-commands in the elog.cfg.

But this is not sufficient. Let's suppose I have an attribute called 'Accessibility' with options 'public' and 'private'. What I am searching for is a filter command for the list display, i.e. if an entry has the accessibility flag 'public', a guest sees this entry in the list and can access it. But if the entry has the accessibility flag private, the entry should not be displayed for guests but for users, that are logged in.

I read the administrator guide carefully, but I didn't found a command that provides for that. Does such a filtering command for the list exist? If not, is it possible to implement one?

Best regards,

Wolfgang Bayer

 Hi,

I have a MacOSX 10.6.7 laptop that periodically synchronizes my logbook with that on a Debian linux web server.  Both instances of ELOG are 2.9.0-2396.

When I create a new entry on the laptop, the indicated time stamp is correct.  When I click Synchronize on the laptop, the entry that gets mirrored to the Debian server has a time stamp exactly one hour earlier (in the past) on the Debian side.

Likewise, when I create a new entry on the Debian server, the indicated time stamp is correct.  When I click Synchronize on the laptop, the entry that gets mirrored from the Debian machine to the laptop has a time stamp that is exactly one hour in the future on the laptop.

This appears to be due to an incorrect handling of times with regard to "summer" (daylight savings) and "standard" time when mirroring between these two different machines.

Is there a straightforward workaround to immunize against this sensitivity?

Thanks!

Andreas

After patching a windows 7 computer with MS12-006, can no longer connect to elog, get page cannot be displayed

See

http://support.microsoft.com/kb/2643584

 A little more information here

We are running elog on an Ubuntu server

Elog was working fine, then, on a windows 7 machine, MS12-006 was installed, rebooted, and could no longer connect to the elog web page.

Discovered that in Internet Explorer 8, by unchecking the use TLS 1.0 in options advanced tab, and making sure that SSL 3.0, TLS 1.1, TLS 1.2 were checked, that the page once again worked.  I'm guessing the elog does not support SSL 3.0, otherwise, I assume I would have to uncheck that as well.  Things do appear to still work on XP, thus far, only Windows 7 appears to break.  While we have a work around, ideally we would like to see a bug fix so that (for legacy reasons), elog will still work with TLS 1.0 on Windows 7.

 Also, strangely, I am able to use the elog forum page https://midas.psi.ch/elogs/Forum while TLS 1.0 is checked.  I notice the version number is 2.9.0-2425, while we are using 2.9.0-2396, so wondering if this is fixed in this newer version.

The forum does not use TLS, but has Apache in front of it which works as a proxy. So TLS is actually handled by Apache, which might have a newer implementation of TLS. The ELOG version number certainly does not make a difference, I did not touch the SSL functionality in a while. But when you compile ELOG on your Ubunto server, you can maybe play with different versions of OpenSSL and see if that changes anything?

- Stefan 

Hello,

we used Admin and write passwords. Now this is no longer supported in ELOG 2.9.0 and I tried to change to File or Kerberos Autentication. But nothing worked. I tried the following lines in elog.cfg

[Serverlogbuch]
Authentication = File
Password file = C:\Program Files\ELOG\logbooks\Serverlogbuch\pwd.txt
Self Authentication = 1

So the self Autentication site opens and I can put in all informations. But if I click on save he tries to save the information in the password file and after a time he stops and Internet Explorer says that the page cannot be reached.

The file is not saved. If I remove the 3 lines the logbook opens without any problems.

I tried also kerberos but it didn't work. But there I think some entries in the krb5.ini are wrong.

Would you please help solving the File password problem?

Best Regards

Michael