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/"
|
Re: text display of ascii files not a good idea, posted by Stefan Ritt on Wed Sep 8 13:46:56 2004
|
> [...]
> > Probably it is fine to display only files ending in '.txt' per default.
> > In addition a file that has more than say 1000 lines should probably
|
|
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. |
|
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.
|
|
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).
|
|
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 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()
|
|
Re: text display of ascii files not a good idea, posted by Stefan Ritt on Wed Sep 15 04:08:46 2004
|
> So a configurable size limit seems appropriate, from which on
> only 'Display attachment' is displayed. And/Or, for files
> exceeding this limit, the first N (new config option) lines could be displayed.
|