You might tell your browser to show you the source code of an ELOG page in list mode. There you'll find the class name you're looking for.

Cheers, Andreas

I have a crontab set-up for root:

crontab -e

* * * * *       if ! ps -C elogd >/dev/null;then /sbin/service elogd restart;fi

The script just checks if elogd is still running and if not, it'll restart it. We run Centos, but I'm sure it'll be easy to adapt for Ubuntu (I don't know much about Debian).

This will only help if elogd really crashed; in case it is still running at 100% cpu load this won't help.

In our case (~30 logbooks, > 100 entries per day, ~ hundred users) elogd is crashing about once a week. With the help of this script it means 1 minute downtime a week: that's acceptable.

See https://midas.psi.ch/elog/config.html on how to use a logfile with elogd. Here's the relevant excerpt:

• Logfile = <file>
  This option specifies a filename which logs all login/logout activities and successful user connections for logbooks with user level access. The the logging level (see below) is larger than 1, also read and write accesses can be logged.
• Logging level = 1 | 2 | 3
  Specifies the logging level. The higher this value, the more information is logged. Default is 2:
  • 1: Log only logins and logouts
  • 2: Log also write accesses
  • 3: Log also read accesses

It's very simple, no need for the find command. E.g.: Start page = ?Author=luedeke&Category=Question&mode=summary

in this forum would do https://midas.psi.ch/elogs/Forum/?Author=luedeke&Category=Question&mode=summary

Hm, maybe my question is silly, but why don't you just use the "Duplicate" command instead of renaming and misusing "Copy to"??

Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#general):

Menu commands = <list>
This option specifies the menu commands displayed on top of a single logbook page. For certain installations, it can be useful to disable some commands. Following commands are possible:

• New - Enter new logbook entry
• Edit - Edit current logbook entry
• Delete - Delete current logbook entry
• Reply - Submit a reply to current entry
• Duplicate - Duplicate the current entry with the possibility to change some values
• [...]
• Copy to - Copy entry to other logbook
• [...]

The commands are always in English, independent of the language = ... setting, and are automatically translated into the specified language.
If this option is not present, following default is used:

Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Config, Help

I think I understand the question (although I have no answer):

When someone uses the "Find" page search, then there is an option to limit the search to e.g. the last year. If you search for a non existing string, it'll only search entries from the past year.

If people are instead using the quickfilter to search for the same non existing string, then all entries of all past years are searched for the string.

In both cases the result page will be empty, so "Entries per page" does not change anything. But in the second case the search might need an order of magnitude longer.

> Hi,
>   I reopen this old thread since I'm having a similar problem.
> 
> I'm running ELOG V3.1.1-0767eb0 on ubuntu with webserver authentication, and I'd like to remove 'active' checkbox as well.
> 
> The problem that we found is that if any user click on the [Set None] button at the bottom of the Config page in order to unsubscribe from all mail notification,
> *all* the checkbox are toggled, not only those for the email notification. And this includes also the "active user" as well.

I can confirm that this bug is present even in this forum and in my current version (ELOG V3.1.3-aded4ae).
And I am positive that this is a bug: it was certainly not the intended behaviour.

Yes, parentheses in field content might be difficult to pass from a shell command. You did not even mention which Linux shell you are using and you did not show the actual elog command. Maybe you want to add that information?

Hi Daniel,

I agree: it should. And it does in my case; it works perfectly fine for my logbooks. Maybe you should have a closer look for special characters in you configuration? Otherwise I don't know why it does not work for you.

If you haven't figured it out already you would need to send a working snippet of your logbook configuration together with a minimal collection of entries that are filtered wrongly.

Cheers, Andreas