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: text display of ascii files not a good idea, posted by T. Ribbrock on Tue Sep 7 13:05:49 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: Options Items limits, posted by Stefan Ritt on Tue Sep 7 17:49:50 2004
|
> > Hello friends,
> >
> > Exist some form to increase limits of items (100) in the Options List
|
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.
|
|
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: 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>
|