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: text display of ascii files not a good idea, posted by Heiko Scheit on Wed Sep 8 23:35:01 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: 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.
|
|
Re: too many <table> tags, posted by Stefan Ritt on Wed Sep 15 07:42:23 2004
|
> > > Couldn't one include the extra <table> tag only when there is really more than
> > > one attribute per line. All other lines could then be aligned properly.
|
Attachment file "" empty or not found, posted by roets on Tue Sep 28 22:44:50 2004
|
I am getting the following error message with version 2.5.4-4 when I try to
add a new entry to a log book.
|
|
Re: Attachment file "" empty or not found, posted by Stefan Ritt on Wed Sep 29 01:28:22 2004
|
| That problem has been fixed in 2.5.4-5 |
|
deleting the sole single entry in log causes crash with xrealloc, posted by Mike Stolove on Sat Oct 9 14:25:23 2004
|
When creating new logbooks, I will create a single entry to test the
configuration. After revising the configuration I want to delete that
single entry and create a new one based on the revised config.
|