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: How to enforce line breaks in plain text entries?, posted by Stefan Ritt on Wed Apr 27 14:39:28 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
|
support "authentication = webserver, kerberos", posted by Devin Bougie on Wed May 18 16:19:07 2016
|
The elog client binary does not work with webserver authentication. One fix would be to support both webserver and kerberos authentication (authentication
= webserver, kerberos), similar to how you currently support
"authentication = kerberos, file".
|
More than 100 attributes , posted by JD on Wed Jun 29 16:07:32 2016
|
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options"
line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual. |
|
Re: More than 100 attributes , posted by Stefan Ritt on Wed Jun 29 16:58:15 2016
|
The limit is in the variable
#define MAX_N_ATTR 100
in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically |
|
Re: More than 100 attributes , posted by JD on Thu Jun 30 14:00:43 2016
|
Thank you Stefan, I think then I will leave it at the default value. I need a stable Systen
Stefan
Ritt wrote:
The limit is in the variable |
|
Re: inserting pictures into a post, posted by JD on Fri Jul 22 09:58:47 2016
|
I know this thread is realy old. Anyways I would like to give a +1 on this request. As a workaround I currently wrote a small PHP Image Hosting/Upload
Script and embedded a link to it in the Menue.
On that page the user uploads the image and gets a link which he/she can embedd using the |