> Is it possible to add a flag in the configuration file, to specify the 
> maximum size of an attachment?

I implemented a "max content length = xxx" flag, which defaults to 10MB. If an
attachment is larger, an error gets displayed. The problem is that elogd can
only send the error message to the browser *after* it received the whole
request, so it has to "drain" the 240 MB first, which could take quite some
time on a slow connection.

Alternatively, I can cut the connection to the browser immediately, since the
HTTP header contains the content length after the first ~500 bytes, but in
that case the browser only shows a message box "Document contains no data"
which gives the user noe clue of what's wrong.

Anyhow the biggest problem of elog in high stress environments is that it's
single threaded. So if someone issues a search in a large logbook, it could
take some time, in which elog cannot respond to other requests. Maybe I will
find time in the future to make elog multithreaded, but certainly not in the
near future.

Something to add to the wishlist:

- Type <attribute> = user

This would define an attribute as being of the type "user" which is a list
of login id's as defined in a password file or on the "Login user =" line. 
In a dataentry form the presence of this ATTRIBUTE would result in a
picklist of loginid's and/or fullnames.

Acknowledged. Added your vote to the wishlist.

> Acknowledged. Added your vote to the wishlist.

Thanks!

> Ok, I added the option
> 
> Tooltip <attribute> = ...
> 
> I apply the HTML "title" tag to the whole table row, so the tooltip appears on the
> whole line, not only the attribute name. I guess this is much more intuitive. Give
> it a try. New version under CVS and available as a snapshot.

I like the implementation, especially with the tooltip popping up anywhere in the
area.  Thanks.

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 ;->

EX: 
#define VERSION "2.5.4-4"
BECOMES
#define VERSION "2.5.4-4-1.483" or something like that?

Just a thought.

Thanks

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
to take more care in the future (:-)))

Having the CVS revision in the executable is however a good idea and I will
put it in.

> 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 ;->
> 
> EX: 
> #define VERSION "2.5.4-4"
> BECOMES
> #define VERSION "2.5.4-4-1.483" or something like that?
> 
> Just a thought.
> 
> Thanks

I have the following in a local logbook config: 
 
  append on edit = "\n\n[$date: $short_name]\n" 
 
When I upload an attachment to an entry, it appears like the page is 
getting refreshed in the browser and the 'append on edit' action is called 
again. This results in two appended strings in the text entry, one for the 
initial edit and one for the upload. 
 
Is this by design or an inadvertent result of uploading an attachment? 
 
My preferred handling of this - and perhaps a more intuitive behavior - 
would be to have the append/prepend actions happen once and only once for 
each edit or reply. 
 
BTW Stephan, many thanks for the great program.