Installation problems, posted by George B. on Mon Oct 27 13:05:13 2008
|
Hello,
I just upgraded to elog 2.7.5 from 2.6.4 on my Debian system. Here is some feedback:
|
Re: Installation problems, posted by Stefan Ritt on Wed Oct 29 05:53:39 2008
|
> 1) "make" fails if libssl-dev package is not installed. Documentation does not mention SSL library requirements.
I added a note to the documentation, thank you.
|
|
Re: Elogd crashes, posted by Stefan Ritt on Wed Oct 29 07:07:47 2008
|
soren poulsen wrote:
|
|
Re: elogd crashes when creating new logbook using existing logbook as template, posted by Stefan Ritt on Thu Oct 30 03:10:00 2008
|
> elogd is crashing with a segv when I try to create a new logbook by clicking the "Create new logbook" button
> with an existing logbook selected in the dropdown list as a template. I've attached my config file for
> reference. As a specific example, I'm logged in as the admin user, viewing logbook "1248", which has no entries,
|
|
Re: Installation problems, posted by George B. on Wed Nov 5 10:32:07 2008
|
> The elogd (or elogd.init in the distribution) is written for RedHat based systems where echo_success gives the
> typical output with a green [OK] at the end of the line. For Debian, there is (was) in principle a Debian package
> which has it's own startup script. Since the package maintainer is not active any more (I guess), the Debian
|
elog client can set arbitrary values to locked attributes, posted by David Potterveld on Mon Nov 10 16:56:08 2008
|
When submitting entries via the elog client, I find that I can set arbitrary values for attributes that are supposedly "preset" and "locked".
As an example, I have in my elogd.cfg file:
[global] |
|
Show/Hide links are displayed but don't work if Show attachments = 0, posted by Dennis Seitz on Mon Nov 10 19:40:43 2008
|
If I add this statement to a logbook config file:
Show attachments = 0
When viewing and individual entry, attached images are not displayed, which is as intended, but the links Show/Hide and Show All/Hide All are still |
elogd dies after receiving second SIGHUP, posted by Kester Habermann on Tue Nov 11 16:45:04 2008
|
elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates.
This was observed on Solaris 10 (SPARC).
The documentation states that elogd should re-read configuration after receiving SIGHUP. |