You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Colin 't Hart <ct...@gbs.com.au> on 1999/11/09 08:31:21 UTC
mod_jserv/5274: Timestamp in mod_jserv.log one hour ahead!
>Number: 5274
>Category: mod_jserv
>Synopsis: Timestamp in mod_jserv.log one hour ahead!
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: jserv
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Mon Nov 8 23:40:00 PST 1999
>Last-Modified:
>Originator: cthart@gbs.com.au
>Organization:
apache
>Release: 1.3.6 + 1.0
>Environment:
NT4sp5
jdk1.2.2
hotspot 1.0.1
>Description:
The timestamps logged in mod_jserv.log are one hour ahead.
This is occuring to me whilst in daylight saving time.
My timezone is Hobart, Tasmania, Australia.
>How-To-Repeat:
>Fix:
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or ]
["Re: general/1098:"). If the subject doesn't match this ]
[pattern, your message will be misfiled and ignored. The ]
["apbugs" address is not added to the Cc line of messages from ]
[the database automatically because of the potential for mail ]
[loops. If you do not include this Cc, your reply may be ig- ]
[nored unless you are responding to an explicit request from a ]
[developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]