text display of ascii files not a good idea, posted by Heiko Scheit on Mon Aug 23 13:43:58 2004
|
I think the text display of ASCII files, which is new in version
2.5.4, is not a good idea. E.g. I had a large ps file attached
to one entry and it took a long time display this entry (over DSL).
|
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 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: some things for your wishlist, posted by Heiko Scheit on Sun Oct 31 20:09:31 2004
|
> > - Use "and" and "or" operands in queries
>
> Elog supports now regular expressions. So for a "<str1> OR <str2>" one can write
|
compiling elog on AMD64, posted by Heiko Scheit on Wed Nov 17 18:52:40 2004
|
When compiling elogd on AMD64 (in 64 bit mode) there are many
warnings like these:
|
|
Re: compiling elog on AMD64, posted by Heiko Scheit on Sun Nov 21 00:46:28 2004
|
> > When compiling elogd on AMD64 (in 64 bit mode) there are many
> > warnings like these:
> >
|
|
implement 'hide attribute' and 'sort attribute', posted by Heiko Scheit on Thu Dec 2 14:39:50 2004
|
Could you implement a 'hide attribute' and 'sort attribute' config option?
While sort is probably not so easy to do the hide option would already
be very useful. What I want to do is to use elog to collect bibtex entries
|