ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68292
|
Wed Mar 23 11:40:52 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | All | ELOG V2.9.2-245 | Re: Width of text field | 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
Edward Diehl wrote: |
I use a elog which has a text field to show log entries: https://classis01.roma1.infn.it/elog/calib/ In the "Summary" view there are only 3 lines of about 40 characters shown, so often the entry is cut off even though there is plenty of space in the text box for longer lines. To see the full entry you must click on the ID number. Is there any way to configure the Text box to show longer lines? Thank you.
|
|
68304
|
Wed Apr 27 14:07:52 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | All | V3.1.1 | How 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? |
68305
|
Wed Apr 27 14:15:19 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | All | V3.1.1 | Re: How 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 |
68306
|
Wed Apr 27 14:36:42 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | All | V3.1.1 | Re: How 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
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. |
68317
|
Fri May 6 22:30:56 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | V2.7.8-2278 | Re: Merge duplicate types | 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 Mund wrote: |
Hello,
We have accumulated some duplicate 'types' in one of our logbooks. Is it possible to merge them?
Thanks,
John
|
|
68321
|
Sun May 22 11:56:21 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3 | Re: elog service crashes frequently | 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.
Stan Turner wrote: |
We have always had issues with eLOG crashing intermittently... I upgraded from Server 2003 to Server 2008 about a year ago to try to reduce the issues... which really didn't help.
The service now seems to crash every week... (getting worse)... Is anyone seeing these issues in Windows servers? Any suggestions??
|
|
68329
|
Wed Jun 8 16:01:11 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 3.113 | Re: Self register = 0 not working , | 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
rudy wrote: |
I have Split Elog to Two Top Group [Check the Config Below].
Problem =
After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.
[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1
Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing
[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01
[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01
|
|
68331
|
Wed Jun 8 18:49:28 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 3.113 | Re: Self register = 0 not working , | 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.
Andreas
rudy wrote: |
Hi Andreas
I'm following the instruction from https://midas.psi.ch/elog/config.html#groups , please scroll to the Top Groups
Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL
Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
[global engineering]
Password file = engineers.pwd
Admin user = stefan
[global administration]
Password file = admin.pwd
Admin user = bill
Andreas Luedeke wrote: |
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
rudy wrote: |
I have Split Elog to Two Top Group [Check the Config Below].
Problem =
After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.
[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1
Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing
[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01
[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01
|
|
|
|
|