> I guess we want "white-space: pre-wrap" which keeps the old line breaks.

Yep. You're right. Thanks!

For the last couple of months we are getting a random elogd crash once in a while we are getting something like the following in the middle of the night

> Sep 29 20:45:07 elog kernel: server_name686835]: segfault at 7ffd7f5a0000 ip 00007fceaeabbf06 sp 00007ffd7f577348 error 6 in libc-2.28.so[7fceaea8a000+1bc000]

I'm going to try and see if it will leave a coredump file, just thought I would ask if anyone else had seen this before?

Thanks,
Matt

Most likely these are some currupt logbook files. If you get a coredump (or stack trace) you can maybe figure out which file it was. These are plain ASCII files (YYMMDDa.log) and you can see with an editor if someting there is not in order.

Stefan

Thanks for the info! 

I expanded an elog server from 1 to 3 logbooks. For each logbook there is a separate password file defined. 

When I try to add a new user in one of the 2 new logbooks using config => new user, it adds the user to the password file for the original logbook.

Have verified that access to the logbooks is controlled via the separate password files. If it would help to provide an example of the elogd.cfg or if I need to clarify further, let me know. 

Any suggestions welcome.

Thanks. Mark.

Can you try the "top groups" option, which means putting each logbook into a separate top group as described in the documentation. For us this works well, new users are only added to the right password file. There is however the problem that as admin you might be logged in to several logbooks (as remembered in your browser via cookies), so you might want to log out from all logbooks first (or clear all cookies of elog), then log in to one logbook and add the user there. In worst case you still can modify the password file by hand, they are plain ASCII files. Only the password has to be entered later since it's encrypted.

Stefan

Hello,
  I am using template for some elogbook entries.

Is is possible to automatically change the template using the actual date in some filed. 

Something like: the template has a place-holder <start date> and this is replaced with today's date when a new entry is created.

I already have a "date" filed which is automatically filled, but I've been asked to have the date also in the template.

Thanks in advance
Stefano

This is a nice idea, but currently no text substations in templates are implemented. It only works in attributes right now.

Stefan

> Hello,
>   I am using template for some elogbook entries.
> 
> Is is possible to automatically change the template using the actual date in some filed. 
> 
> Something like: the template has a place-holder <start date> and this is replaced with today's date when a new entry is created.
> 
> I already have a "date" filed which is automatically filled, but I've been asked to have the date also in the template.
> 
> Thanks in advance
> Stefano