I implemented the new scheme where 

- under Windows, the configuration is only checked once every access

- under Unix, the configuration is read initially, and on every -HUP signal

This should speed up the server considerably. The next bottleneck is the 
rsputs2() function, which requires quite some computing power in order to find 
any "http://", "//", etc. strings in every output. If anybody knows a 
more clever way of coding that, please let me know.

The new version is under CVS.

> I found a stack overflow if there are too many replies. This has been fixed in 
> the current CVS verson of elogd.c and will be incorporated into the next release.

Many thanks for your quick reply to this issue.  I have also noticed that when 
moving a log entry that contains as few as 4 replies to replies with the "Move to" 
command that the elog server will crash.  I ran into this issue many times when I 
created a new logbook and was trying to move some of the longer threads into it.  
Please let me know if you would like me to send some sample entries from our 
logbook that illustrate this.

Thanks,
Chris    

> I implemented the new scheme where 
> 
> - under Windows, the configuration is only checked once every access
> 
> - under Unix, the configuration is read initially, and on every -HUP signal
> 
> This should speed up the server considerably. The next bottleneck is the 
> rsputs2() function, which requires quite some computing power in order to find 
> any "http://", "//", etc. strings in every output. If anybody knows a 
> more clever way of coding that, please let me know.
> 
> The new version is under CVS.

may be use the logic in the 'format' attribute
like 'email', http, ftp 
so elog will test only on these attributes

Return-Path: 
Received: from ligo.phys.lsu.edu ([unix socket])
	by ligo.phys.lsu.edu (Cyrus v2.1.13) with LMTP; Wed, 28 Jan 2004 16:27:03 -0600
X-Sieve: CMU Sieve 2.2
Received: from ligo.phys.lsu.edu (ligo.phys.lsu.edu [130.39.181.231])
	by ligo.phys.lsu.edu (Postfix) with SMTP
	id 5E12A788D1; Wed, 28 Jan 2004 16:27:03 -0600 (CST)
To: ELOG@ligo.phys.lsu.edu, user@ligo.phys.lsu.edu
From: elog@ligo.phys.lsu.edu
Subject: New playground elog entry
X-Mailer: Elog, Version 2.3.9
X-Elog-URL: http://ligo.phys.lsu.edu:8080/playground/13
X-Elog-submit-type: web|elog
Date: Wed, 28 Jan 2004 22:27:03 +52182819
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <20040128222703.5E12A788D1@ligo.phys.lsu.edu>

A new entry has been submitted on ligo.phys.lsu.edu

Logbook             : playground
Author              : Joseph Giaime
Type                : Other
Category            : Other
Subject             : yet another test

Logbook URL         : http://ligo.phys.lsu.edu:8080/playground/13

> Instead of something like "Date: Wed, 28 Jan 2004 14:46:16 -0600", the
> "-0600" is replaced by a large number that doesn't correspond with anything
> I can figure out.  This is the sort of thing that does no real harm, but the
> notebook users keep complaining. 

This is caused by the elogd program itself. To produce the "-0600", it uses the 
variable "timezone", which is defined as difference in seconds between local time 
and coordinated universl time. This works find under Windows, Linux, FreeBSD, but 
apparently not under MacOSX. Although this variable is defined, it's unassigned. 

The code where this is used is in sendmail(), at the lines

   time(&now);
   ts = localtime(&now);
   strftime(buf, sizeof(buf), "%a, %d %b %Y %H:%M:%S", ts);
   offset = (-(int) timezone);
   if (ts->tm_isdst)
      offset += 3600;

The current localtime gets written into "buf", then the timzone offset gets 
corrected by the daylight savings time, then the offset is used to produce the 
"-0600".

So if anybody being familiar with MacOSX has some idea, please let me know.

- Stefan

Hi Stephan,

one of the eLOG users at our company, has problems using eLOG in combination with Google Chrome (version 2.0.172.43), log in gives no problem, when selecting the appropiate department, he get's the following error:

• Error Code: 502 Proxy Error. The ISA Server denied the specified Uniform Resource Locator (URL). (12202)
• IP Address: 130.78.137.1
• Date: 8-9-2009 07:13:55 [GMT]
• Server: NLISA1.top.local
• Source: proxy

This problem does not appear with other browsers like IE7/8 and Firefox.

Do you have any clue?

Tnx in advance.

kind regards, RJ Schrijvers.

Hi Stephan,

one of the eLOG users at our company, has problems using eLOG in combination with Google Chrome (version 2.0.172.43), log in gives no problem, when selecting the appropiate department, he get's the following error:

• Error Code: 502 Proxy Error. The ISA Server denied the specified Uniform Resource Locator (URL). (12202)
• IP Address: 130.78.137.1
• Date: 8-9-2009 07:13:55 [GMT]
• Server: NLISA1.top.local
• Source: proxy

This problem does not appear with other browsers like IE7/8 and Firefox.

Do you have any clue?

Tnx in advance.

kind regards, RJ Schrijvers.

When Chrome came out, I vaguely remember that there were some initial problems, but they have been fixed since about a year. But I see you are using a pretty old version of ELOG, so please consider upgrading.