Re: Links to images in notification message, posted by Devin Bougie on Fri Feb 26 18:11:14 2016
|
From the notification I received, it looks like "2" is a problem with this server. In the email notification, we would like images to
be a link to a URL displaying the full-size image (as they are in v2.9.2).
Thanks, |
|
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
|
|
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 |
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 |