Width of text field, posted by Edward Diehl on Tue Mar 22 18:28:03 2016
|
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? |
Re: Width of text field, posted by Andreas Luedeke on Wed Mar 23 11:40:52 2016
|
Did you try the options
Summary lines = x
Summary line length = x
as
documented in https://midas.psi.ch/elog/config.html#flags ? |
|
Installation: Failed Dependencies, posted by Phil Rubin on Fri Mar 11 17:29:47 2016
|
Is there anything I can do about this?
kernel: 2.6.32-279.14.1.el6.x86_64
ldd (GNU libc) 2.12 |
|
Re: Installation: Failed Dependencies, posted by Phil Rubin on Fri Mar 11 18:59:30 2016
|
I attempted instead to build from the tar ball, and, except for a "fatal" git error, make built elogd, elog, and elconv. I put
the first in /usr/local/sbin, and the latter two in /usr/local/bin, and then restarted elogd, but this didn't work:
Service Temporarily Unavailable |
|
Re: Installation: Failed Dependencies, posted by Phil Rubin on Fri Mar 11 19:24:11 2016
|
OK. I found the source of the logbook problem in an exchange from May 2015, so no need to answer this one.
But I would like to be able to upgrade to 3.x from 2.9, so any help with this will be much appreciated.
Phil |
|
Re: Installation: Failed Dependencies, posted by Darren Hollinrake on Sat Mar 19 15:24:29 2016
|
I did the following on CentOS 6.7 (Should work for Fedora and RHEL as well):
yum install -y wget
wget http://midas.psi.ch/elog/download/RPMS/elog-latest.i386.rpm |
|
upgrade problem, posted by Tim Schelfhout on Tue Mar 15 19:53:55 2016
|
Hello there,
After several years of great ELOG usage I decided to upgrade our ELOG server. I am using it to keep
a logbook of my students. |
|
Re: upgrade problem, posted by Andreas Luedeke on Wed Mar 16 08:39:55 2016
|
Hi Tim,
starting with ELOG version 3 all entries are moved into sub-directories for each year.
If you move the files back
from the sub-directories and restart elogd, then the entries should appear again in the logbook with ELOG 2.9.2.
I don't
know how to solve your other problem. Maybe you should talk to someone locally who can administer your windows server?
Cheers, Andreas
|
Pre-populate filed based on selection, posted by Jimmy Bria on Mon Mar 14 16:00:02 2016 
|
Hi,
Is it possible to pre-populate a field based on the selection of another field. I like to have the Equipment Description field populated
when the use makes a selection on the EQ# field. |
|
Re: Pre-populate filed based on selection, posted by Stefan Ritt on Tue Mar 15 03:48:58 2016
|
Use "conditional attributes" as described in the documentation: https://midas.psi.ch/elog/config.html#conditional
Jimmy
Bria wrote:
Hi, |
|
Installation: Failed Dependencies, posted by Phil Rubin on Fri Mar 11 17:19:02 2016
|
Is there anything I can do about this?
kernel: 2.6.32-279.14.1.el6.x86_64
ldd (GNU libc) 2.12 |
|
elogd -m Error sending local entry: Error transmitting message, posted by Dave on Thu Mar 10 00:26:03 2016
|
I'm running ELOG on a seperate Windows Servers.
When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"
If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG. |
elogd -m , posted by Dave on Thu Mar 10 00:16:33 2016
|
I'm running ELOG on a seperate Windows Servers.
When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"
If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG. |
Execute new|edit doesn't seem to work, posted by Juergen Diefenbach on Fri Feb 26 17:35:54 2016
|
I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
When a new entry is created a shell script should be executed (certain attributes of the logbook entry should be passed as arguments to it). The script |
|
Re: Execute new|edit doesn't seem to work, posted by Andreas Luedeke on Sun Feb 28 18:24:58 2016
|
[quote="Juergen Diefenbach"]I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
[...]
However, I experienced unreproducible behavior when creating "new" entries. Sometimes the command specified by "Execute new=" is called, sometimes the |
|
Re: Execute new|edit doesn't seem to work, posted by Juergen Diefenbach on Mon Mar 7 13:03:13 2016
|
[quote="Andreas Luedeke"]I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour changes:
Save drafts = 0
|
|
Re: Execute new|edit doesn't seem to work, posted by Andreas Luedeke on Tue Mar 8 14:12:26 2016
|
[quote="Juergen Diefenbach"][quote="Andreas Luedeke"]I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour
changes:
Save drafts = 0
|