In the password file, I see several same username, such as:

<user>

    <name>test</name>

    <password encoding="SHA256">iXhH.</password>

    <full_name>test me</full_name>

    <last_logout>Tue Apr 14 14:12:44 2009</last_logout>

    <last_activity>Wed May 19 09:39:32 2010</last_activity>

    <email>maqm@ihep.ac.cn</email>

    <email_notify/>

  </user> 

<user>

    <name>test</name>

    <password encoding="SHA256">iXhH.</password>

    <full_name>test me</full_name>

   <last_logout>0</last_logout>

    <last_activity>0</last_activity>

      <inactive>0</inactive>

    <email>maqm@ihep.ac.cn</email>

    <email_notify/>

  </user> 

<user>

    <name>test</name>

    <password encoding="SHA256">iXhH.</password>

    <full_name>test me</full_name>

    <last_logout>0</last_logout>

    <last_activity>0</last_activity>

      <inactive>0</inactive>

    <email>maqm@ihep.ac.cn</email>

       <email_notify/>

  </user> 

I don't know the reason why eLog can have the same username.

And what should I do to prevent these things happen?

Thanks!

Thanks for reporting that bug. It has been fixed in SVN revision 2404.  

Can you tell me how to reproduce this? If I do it here, I just get back to the login page:

Maybe it has to do with your specific Kerberos implementation? What server are you using?

 I am sorry but I cannot reproduce this any more. It happened several times when I was testing different kinds of wrong user input to the authentication dialog but now there is no issue any longer. However, there has been other issues lately in this domain and it may be that the Kerberos installation has been patched by our automatic update installation.

Case closed! Thanks anyway for responding.

Soren

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