Did you try the options

• Summary lines = x
• Summary line length = x

as documented in https://midas.psi.ch/elog/config.html#flags ?

It works nicely with plain text entries; it has some difficulties with HTML, since it has to remove the formatting and that disturbs the line count.

Cheers Andreas

We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
entries made during the shift and files the printouts. If one entry in the shift was plain text without
appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the width
of this line and either the printout is cut off at the right side, or the whole content is scaled down to very
tiny scale, which makes it unreadable.

Is there a way to enforce line breaks in plain text entries?

> We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> entries made during the shift and files the printouts. If one entry in the shift was plain text without
> appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> very tiny scale, which makes it unreadable.
> 
> Is there a way to enforce line breaks in plain text entries?

Obviously there is: this logbook does add line breaks?!?

Maybe it is only a problem with entries made by the "elog" command?
I'll find it out and re-post.

Cheers
Andreas

> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> > width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> > very tiny scale, which makes it unreadable.
> > 
> > Is there a way to enforce line breaks in plain text entries?
> 
> Obviously there is: this logbook does add line breaks?!?
> 
> Maybe it is only a problem with entries made by the "elog" command?
> I'll find it out and re-post.
> 
> Cheers
> Andreas

Okay, I found two ways to add very long lines:
- if the very long line does not contain a space then this will screw the printout.
- if the line has been added as plain text using the elog command, there will be no line breaks added.

It would be nice if the elog command would have an option to break lines to a maximum line length.
But for the moment I'll just modify the applications that make use of the elog command.

I'm not sure I understand your question correctly.

If you want to remove options from an extendable option attribute, then you can just edit the logbook configuration file.

We do run ELOG on a Linux server and see about weekly crashes, too. It seems to be connected to the authentication process (Kerberos, File), but we could not nail it down yet.

But we have set up a supervision process that checks every minute if the "elogd" process is still running. If not, it simply restarts it.

If ELOG is down for two minutes a week, this is fine for our users.

It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.

If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).

Andreas