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

> could you add command for main menu guest user
> Selection Page guest = ....

I added "Guest Selection Page" coming in version 2.3.8

> When you take the elogd.cfg file and the menu commands = <list> and guest 
> menu commands = <list>, the config menu for edit the elogd.cfg stops 
> working, yet if I change the URL manually, I can still get to the file and 
> the menus do not change.  If I delete all menu commands, then all works 
> without errors, yet the menus do not match default.

Has just been fixed. Available under CVS and soon in 2.3.8.

Ive just been alerted to a bug with email notifications in Elog.

Basically if your log book contains a space then the URL that is sent in 
emails when creating tickets or updating old entries doesnt put %20 (IEs 
space) inthe URL it leaves a space hense breaking the link.

for example

Correct Way prior to 2.3.8

http://192.168.0.1:99/Provisioning%20Request/35

Broken way with new version

http://192.168.0.1:99/Provisioning Request/35
                                 ^
Link is broken at this point

My config looks like this

Email Status Assigned = $Owner@abc.co.uk
Email Status Re-Assigned = $Owner@abc.co.uk
Email Status Completed = $Requester@abc.co.uk
Email "Send Update Email" Yes = $Requester@abc.co.uk
Use Email Subject = A Provisioning Ticket has been assigned to you or 
completed
Use Email From = NetworkTeam@abc.co.uk

> Correct Way prior to 2.3.8
> 
> http://192.168.0.1:99/Provisioning%20Request/35
> 
> Broken way with new version
> 
> http://192.168.0.1:99/Provisioning Request/35

Exactly this problem has been fixed between 2.3.7 and 2.3.8, so can it be 
that you mixed up these two versions? To be precise, the fix happend in 
Revision 1.113 from 2003/06/04 08:17:35. So are you sure that you use a 
version of elogd after that modification? I tried to reproduce your problem 
with the official 2.3.8 version, but I got the correct result.