Enhanced "eLog Version" Variable, posted by Steve Jones on Fri Sep 24 19:17:52 2004
|
Stefan, would it be ok to add the "minor" revision level to the VERSION
constant? I've been doing this after I download source just so I can keep
things straight, you keep cranking out versions ;->
|
Re: Enhanced "eLog Version" Variable, posted by Stefan Ritt on Fri Sep 24 22:37:01 2004
|
Sorry for that. The idea is that the -4 is the minor number between releases
(mainly for bug fixes and impatient users (;-) ). I accidently overwrote the
-4 version several times when testing a new RPM building scheme, but I promise
|
Re: Enhanced "eLog Version" Variable, posted by Steve Jones on Wed Oct 6 06:14:36 2004
|
No big deal - I looked at the code and you did a much more thorough job than I
would have done. Appreciate all of the hard work -- this product is masterful!
|
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 |
too many <table> tags, posted by Heiko Scheit on Mon Aug 2 14:56:56 2004 
|
There are too many <table> tags when displaying a singel entry. E.g.
in http://midas.psi.ch/elogs/Config+Examples/1 the row 'Configuration Name'
is not aligned with the others (see attachment).
|
|
Re: too many <table> tags, posted by Stefan Ritt on Tue Aug 3 11:16:46 2004
|
> There are too many <table> tags when displaying a singel entry. E.g.
> in http://midas.psi.ch/elogs/Config+Examples/1 the row 'Configuration Name'
> is not aligned with the others (see attachment).
|
|
Re: too many <table> tags, posted by Heiko Scheit on Tue Aug 3 13:06:54 2004
|
> > There are too many <table> tags when displaying a singel entry. E.g.
> > in http://midas.psi.ch/elogs/Config+Examples/1 the row 'Configuration Name'
> > is not aligned with the others (see attachment).
|
|
Re: too many <table> tags, posted by Stefan Ritt on Tue Aug 3 13:31:08 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.
|
|
Re: too many <table> tags, posted by Steve Jones on Thu Aug 12 23:32:46 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.
>
|
|
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.
|
|
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: 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: 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: 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: 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.
|
|
Use Email From not Working as Before..., posted by Christopher Jones on Mon Sep 13 20:44:35 2004
|
Hi,
We just recently upgraded from an older version of Elog to the latest and
|
, posted by on Wed Sep 15 00:16:19 2004
|
| I g |
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).
|