Ok, thank you for your answer.

I guess my next question is whether it is possible to have, for example, 2 attributes:

Options Ingredient1 = 

Options Ingredient2 = 

Extendable options = Ingredients1, Ingredients2

sharing the exact same possible list of values.

Thanks agin.

If you add via an option to one Ingredient, you have to add it to the other as well. There is no automatic way to do that. 

 I've tried adding this statement to my cfg file but the attributes are still unsorted in the QuickFilter menus. Was this implemented in 2.7.7?

You need revision 2252 or later. So you have to upgrade to 2.7.8. 

 We have upgraded to 2.7.8 but this still doesn't seem to work. The quick menus are still unsorted. Does it work for you?

Sorry, there was a typo, you need

Sort attribute options <attribute> = 1

where <attribute> is the name of the attribute to be sorted (in case you want some attributes sorted, but not all). 

 That did the trick. That was a good idea, to give us the option of which attributes to sort, too. Thanks again for adding this feature!

For some odd reasons, we are experiencing frequent crashes of elogd over the past few days. It has been working fine so far, but more or less out of the blue it became rather unreliable. The current configuration is installed on two servers, one running 2.7.5.-r2174 on ClarkConnect 4 and one running 2.7.6-r2233 on Debian 4.0 - both show the same problem. Each of them has an "active" group with four logbooks and an "archive" group with three logbooks. In the "active" group, there are two logbooks that share the same index (using Subdir=...) and it looks like the crashes occur most of the time in these, though that's just a hunch so far. Also, most of the crashes seem to happen when submitting an entry that has been edited. Actually, submitting a modified entry has always been strange in our logbooks: When we hit submit, we get a pop-up window asking "Submit modified entry?". When choosing "OK", the entry that has been edited is duplicated. When choosing "Cancel", it is submitted correctly.

I've been running elogd like this (to get more info)

elogd -v > elog-2233-2.log 2>&1

The last entry I get in the log when elogd crashes is:

  Same index as logbook Machine Log
elogd: src/elogd.c:727: xfree: Assertion `*((unsigned int *) (temp - 4)) == 0xdeadc0de' failed.
Received unknown cookie "wikidb_mw__session"
Received unknown cookie "wikidb_mw__session"

I did actually make a few changes to the configuration before we noticed the crashes: I added one extra attribute and a few more conditionals.

Any additional information you need: Just let me know.

Regards,

Thomas