elogd does not exit on SIGTERM, posted by Heiko Scheit on Wed Feb 18 16:54:27 2004
|
When trying to stop elogd processes with the kill command
elogd exits only after access to the logbook.
|
|
Re: elogd does not exit on SIGTERM, posted by Stefan Ritt on Thu Feb 19 09:38:13 2004
|
Noee. Here it works immediately.
Can you try with a fresh server from the distribution, with the example
|
|
Re: elogd does not exit on SIGTERM, posted by Heiko Scheit on Fri Aug 27 00:49:27 2004
|
> Noee. Here it works immediately.
>
> Can you try with a fresh server from the distribution, with the example
|
Re: elogd does not exit on SIGTERM, posted by Stefan Ritt on Wed Sep 8 17:38:54 2004
|
> elogd does not exit if there is an 'unprocessed' HUP. So when you do
>
> kill -HUP <pid>
|
|
Re: elogd does not exit on SIGTERM, posted by Heiko Scheit on Wed Sep 8 23:03:36 2004
|
> > elogd does not exit if there is an 'unprocessed' HUP. So when you do
> >
> > kill -HUP <pid>
|
|
Re: elogd does not exit on SIGTERM, posted by Stefan Ritt on Thu Sep 9 21:40:47 2004
|
> kill -HUP <pid>; sleep 2; kill <pid>
Thanks, I could reproduce the problem. It had to do that a SIGHUP aborts the select()
|
URL bug in elogd.cfg, posted by Steve Jones on Mon Aug 16 23:49:13 2004
|
Under 2.5.4-2 build1.460, when I edit the demo elogd.cfg the following happens:
- I start with
|
|
Re: URL bug in elogd.cfg, posted by Stefan Ritt on Wed Sep 8 12:19:00 2004
|
| This problem has been fixed in revision 1.462 |
Re: URL bug in elogd.cfg, posted by Steve Jones on Wed Sep 8 17:39:43 2004
|
> This problem has been fixed in revision 1.462
Thank you! |
PostScript Files shown as text., posted by Bryan Moffit on Fri Sep 3 20:17:35 2004
|
At some point, in the last week or so, I upgraded the debian-unstable
version (r1459-1) of elog. Now, PostScript files (as attachments) are
displayed (shown in ascii text, instead of just showing the link).
|
|
Re: PostScript Files shown as text., posted by Stefan Ritt on Wed Sep 8 15:52:00 2004
|
> At some point, in the last week or so, I upgraded the debian-unstable
> version (r1459-1) of elog. Now, PostScript files (as attachments) are
> displayed (shown in ascii text, instead of just showing the link).
|
|
Locking entries, posted by filantoro on Wed Sep 1 03:42:22 2004
|
I have a question about ELOG. Let's say after the user finishes his shift
and passess on to the next user on duty. A staff member would want to look
through the entries and vet them. The staff could lock the entries to
|
|
Re: Locking entries, posted by Stefan Ritt on Wed Sep 8 15:48:47 2004
|
One possibility is to use the option "Restrict edit time = <hours>". This way
an entry can only be edited let's say 8 hours after it has been created.
|
|
ELOG with stunnel won't show logbook, posted by Bartjan Wattel on Wed Aug 25 13:36:56 2004
|
Hi,
I have an ELOG installation on a RedHat linux server, called myserver. I
|
|
Re: ELOG with stunnel won't show logbook, posted by Stefan Ritt on Wed Sep 8 15:37:09 2004
|
| That bug has been fixed recently, please update to the newest version. |
|
write access for elogd, posted by Dave Becker on Thu Aug 19 06:21:38 2004
|
Newly installed elog gives this response when I try to submit a new record:
New entry cannot be written to directory "./logbooks/Linux/"
|
|
Re: write access for elogd, posted by Stefan Ritt on Wed Sep 8 12:36:08 2004
|
> Newly installed elog gives this response when I try to submit a new record:
>
> New entry cannot be written to directory "./logbooks/Linux/"
|
|
Admin rights lost after upgrade 2.5.2 to 2.5.4, posted by nait tauh on Wed Aug 18 11:12:56 2004
|
The upgrade was done by just replacing elogd from 2.5.2 to 2.5.4 from the rpm.
Somehow elogd 2.5.4 treat all users as normal user. When clicking on
|
|
Re: Admin rights lost after upgrade 2.5.2 to 2.5.4, posted by Stefan Ritt on Wed Sep 8 12:25:20 2004
|
> Somehow elogd 2.5.4 treat all users as normal user. When clicking on
> "config". All admin users has no "change elogd.cfg" button. Revert back to
> 2.5.2 OK.
|
|
Q: on 'FIND MENU commands =' <menu list>, posted by Steve Jones on Wed Aug 11 18:02:22 2004
|
The help text on the website says the following:
"The command Select can be used to select multiple messages for deletion of
|
|
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Stefan Ritt on Thu Aug 12 21:10:29 2004
|
> The help text on the website says the following:
>
> "The command Select can be used to select multiple messages for deletion of
|
|
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Steve Jones on Thu Aug 12 22:17:01 2004
|
> > The help text on the website says the following:
> >
> > "The command Select can be used to select multiple messages for deletion of
|
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Stefan Ritt on Thu Aug 12 22:24:04 2004 
|
> Thank you. I had added the "Move To" and this works at the log entry
level (i.e., "Move
> To <name>) but in the threaded view one does not get the enumerated list
|
|
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Steve Jones on Thu Aug 12 23:55:00 2004
|
> > Thank you. I had added the "Move To" and this works at the log entry
> level (i.e., "Move
> > To <name>) but in the threaded view one does not get the enumerated list
|
|
Re: Q: on 'FIND MENU commands =' <menu list>, posted by Stefan Ritt on Wed Sep 8 11:44:56 2004
|
> Hmmm. I like the little buttons with the pull-downs for selections.
> Unfortunately, I don't get that. With a config of:
>
|