When ROptions items contain the same substring and this substring is also an ROptions item (ex: notdone, 
done), the value of the entry could change in the edit page. 
It depends on the item order in the config file. 

If Options is used (instead of ROptions), it works as expected.

Is it a bug?


Examples : 

#Insert "notdone" as new entry. When you try to edit the entry, the displayed value is "done".

[test_bad]
Attributes = Author, Category
ROptions Category = notdone, done

#No problem if you change the item order 

[test_good]
Attributes = Author, Category
ROptions Category = done, notdone

Can you try the following:

• Put your "password file = xxx" option from the [global] section in elogd.cfg into each individual logook, remove it from [global] 
• Remove all cookies from your browser
• Try again to log in to the individual logbooks

The login is handled through cookies. Once you log in, you get two cookies unm (for user name) and upwd (for user password). Each cookie contains a "path" which controls to which URL the browser sends that cookie. If you "password file = xxx" statement is under [global], then "path=/", meaning the cookie is sent for all logbooks. This confuses you if you have different rights for different logooks. If "password file = xxx" is however in each individual loogbooks configuration, then you get "path=/<lobook>". You can check that by inspecting your browser's cookies. In that case the login name and password cookies are only sent to the URL for that specific logbook. I have not tested that extensively (different browsers, with/without Apache proxy), but if it works reliably, I will put this into the documentation.

    for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; )
        if (i < (int) sizeof(cookie)-1)
            cookie[i++] = *p++;

    for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n';)
        if (i < (int) sizeof(cookie) - 1)
            cookie[i++] = *p++;
        else
            break;

    for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; ++p)
        if (i < (int) sizeof(cookie)-1)
            cookie[i++] = *p;

 thanks Grant, but I dont see the solution.  your last entry still states users being logged out when switching logbooks.

Are you suggesting that every user within our orginization needs to be on the deny list of logbook1 if they have rights to logook2?

 Have a look at this thread Hal, worked well for me:  Link

 You can pass numerical attributes to an external command via "Execute new =...".  This external command can then do the math and pass the result _back_ to the logbook either as a new entry or as an edit with the command-line client "elog".

For example, given a new entry with (numerical) attributes A and B, if you have

Execute new = add_them.pl $A $B $message id

in your elog.cfg file, then $A and $B will be passed to the add_them.pl perl script.  Now have the perl script (or bc, or whatever you want to use) do the appropriate math and submit the result.  For example, your perl script might include

$C=$A+$B

$D=$A*$B

elog -a C=$C ... -e "$message id" "Sum as edit"

elog -a D=$D ... "Product as new entry"