Re: How to enforce line breaks in plain text entries?, posted by Andreas Luedeke on Wed Apr 27 14:15:19 2016
|
> 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
|
|
Re: How to enforce line breaks in plain text entries?, posted by Andreas Luedeke on Wed Apr 27 14:36:42 2016
|
> > 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
|
|
Re: Merge duplicate types, posted by Andreas Luedeke on Fri May 6 22:30:56 2016
|
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.
John |
|
Re: elog service crashes frequently, posted by Andreas Luedeke on Sun May 22 11:56:21 2016
|
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 |
|
Re: Self register = 0 not working , , posted by Andreas Luedeke on Wed Jun 8 16:01:11 2016
|
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). |
|
Re: Self register = 0 not working , , posted by Andreas Luedeke on Wed Jun 8 18:49:28 2016
|
Aparently I've missed that one :-)
In order to test your problem it would be useful to have a minimal config file to reproduce the problem. Yours does not include any actual logbook,
only [global *] sections. |
|
Re: Custom input forms implementation, posted by Andreas Luedeke on Sat Jul 9 10:44:45 2016
|
You might try to specify an absolute path to the password file in the configuration.
I would need a complete minimal configuration that creates that problem.
|
|
Re: Multiple outcomes to a conditional attribute, posted by Andreas Luedeke on Tue Jul 12 08:31:37 2016
|
Hi Sofian,
it should work like this:
Options Type = Fault{1}, Test{2}, Report{3} |