Guy Harris wrote:
>If a trace file has a time stamp that contains the number of seconds
>between midnight GMT, January 1, 1970, GMT, and 10:30 UTC, {whatever the
>date is supposed to be}, then, if Ethereal is not displaying that
>correctly for your time zone, either
>
>1) your machine's time zone is not configured correctly;
>
>2) there's a bug in the time zone code in your OS.
>
>If a trance file that has a time stamp that *doesn't* contain that value -
>for example, if it's in the current time for the UK, with the DST offset
>applied to UTC - then it won't display as 11:30 in the Western European
>time zone.
It neither 1) nor 2) (tested on Windows and Linux) it is
3) code in wiretap module for toshiba trace format is not considering
date and lib C code in both Linux and Windows is so smart to know which
years in the past had which daylight savings time rules. No daylight savings
time in 1970 means proper behaviour of libc, but inproper behaviour of
toshiba wiretap module.
In other words it would be a bug in libc if it was showing 2 hours difference
(UTC-CEST localtime) for 1970, whereas that is what I want for April 2004.
I still don't know how to fix it, since I need date information to fix it, which
is not available in the toshiba trace format.
Thanks for your reply,
Rolf
_____________________________________________________________________
Der WEB.DE Virenschutz schuetzt Ihr Postfach vor dem Wurm Netsky.A-P!
Kostenfrei fuer alle FreeMail Nutzer. http://f.web.de/?mc=021157
