> I vaguely remember there was once a problem with that date. So can you please 
> try again with a recent version of ELOG?

i just entered a new message and it's doing the same thing...

the version showing at the bottom of the listing is v2.1.2 (even though i updated to 2.1.3)

> Hi,
> 
> I am having trouble modifying the elog client to allow larger 
attachment.  I
> have elogd configure for attchment sizes of 10Meg and I would like the
> option to be able to use the elog client.  Can anyone give me key points 
as
> to how to go about doing this?  I have tried but I must be missing 
something.
> 
> Also, as a suggestion, it might make sense to add a MAX_ATTACHMENT_SIZE 
def
> in a common header file.
> 
> Thanks
> Kevin

I modified the elog program such that the attachment buffer is dynamically 
allocated which means that it works with any size. Please find the updated 
version at

http://midas.psi.ch/cgi-bin/cvsweb/~checkout~/elog/elog.c?rev=1.10

Note that for attachments larger than ~2MB, one hase to increase the 
WEB_BUFFER_SIZE in elogd.c.

- Stefan

> if you have a site that requires authentication to the smtp server, how do 
> you specify this info in elog???
> 
> thanks,
> eric

This is not implemented right now. Unfortunately, I don't hve an smtp server 
here which requires authentication, so I cannot develop this. If anyone has a 
server from which I have *remote* access from here (pc810.psi.ch), I will put 
this additional authentication in.

> I noticed a long url got hard-wrapped when I entered a long one, I patched 
> the source code. I don't know if this was done intentionally, otherwise you 
> might want to change this also.
> 
> diff elogd.c elogd.c.org 
> 4468c4468
> <     rsprintf("<textarea rows=20 cols=%d wrap=soft name=Text>", width);
> ---
> >     rsprintf("<textarea rows=20 cols=%d wrap=hard name=Text>", width);

If the wrap=soft is used, users tend to enter very long lines (without 
hitting return in between). If this line then gets displayed, it can be very 
wide and the user has to horizontally scroll the browser window. What I can 
do is in the display (not the entry) to concatenate URLs which are separated 
only by a CR/LF. But you then have some cases where you have an URL to the 
end of the line, then some other text starting on the next line, which then 
get concatenated falsely (unless you use some clever code which scans 
for ".html" or "xxx/xxx" or something like that.

> Now I don't like both parameters. 20 is too long for my display (1024x768) 
> and 76 is too short. Something dynamically would be cool, but a parameter 
> somewhere in a config file would also be acceptable. (just a thought, makes 
> it easier to upgrade)

You always had the option "Message width = xx" to change the width on the 
text box, and I added in V 2.2.2 the parameter "Message height = xx" where 
you can change the 20 to something else.

> When I make a new entry I get an email with 
> 
>    subject: New ELOG entry
> 
> But when I or someone else changes an entry I also get an email with a 
> 
>    subject: New ELOG entry
> 
> I would prefer to see "Changed" , "Edited", or "Updated". This is beyond my 
> programming capabilities so I enter this request.

I have implemented this feature in V2.2.2.

> Hello,
> I am running Elog V2.1.3 on Solaris 8 and I was very pleased about this 
> tool.But now I have a problem: Sometimes it takes a lot of time submitting 
> an entry into a logbook, up to 3 minutes. This behaviour does only occur 
> sometimes. Did anyone of You experience something like this?

I have seen that behaviour only with certain versions of Netscape, running on 
the same machine than the elogd server. Since I did not observe this with IE 
or Opera, I attributed this to a Netscape flaw. Have you tried different 
versions of Mozilla?

- Stefan

> Encoding  problem:
> 
> How to make ELOG generate HTTP pages with 
> 
> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=XXXX">
> 
> tag in header. With charset=XXX selectable via config.

I added this option, so now you can specify in the [global] section of 
elogd.c something like

charset = windows-1252

To switch to Cyrillic. The modification will be contained in the next version 
of elog (2.2.3), and is now available from the CVS repository at:

http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c

- Stefan

We had the same problem here. What worked in our case was:

Traffic to port 113 (identd) was blocked. Because the server didn't give any
response at all there was a time-out to which we were waiting.  Opening up
the 113 port significantly speeded things up. Even when no ident-deamon was
running on the system. (it now gets an immediate no deamon running msg, and
can go on with it's processing instead of having to wait for a time-out)