timestamps in sasl
Tue Aug 26 07:14:12 CEST 2003
> Con: potential for human error; people looking at the timestamps
> surprised by what they see.
The utc_log flag should still be used.
> Con: I've been told that Windows doesn't actually _know_ what the
> is; was that true and if so is it still true?
This is not true.
>From the platform SDK "The system bases system time on coordinated
universal time (UTC). UTC-based time is loosely defined as the current
date and time of day in Greenwich, England."
" Windows NT: Requires version 3.1 or later.
Windows: Requires Windows 95 or later.
Windows CE: Requires version 1.0 or later.
Header: Declared in winbase.h.
Import Library: Use kernel32.lib."
> Con: UNIX doesn't actually know what the UTC time is either; UNIX
> believes that every day has exactly 86,400 seconds and in UTC that
> just isn't true. Up to two days in a year may have an extra
> and there is no formula saying which years get leap seconds. I
> to have a table giving historic leap seconds, but it is way out of
> date and I don't remember where to get current information.
This is true, OS people are planning/working on a move towards TAI
(International Atomic Time) nowadays.
Use of NTP corrects leap seconds, but the final solution would be to
use TAI. Until TAI support is more spread in OS'es I'll guess we will
have to set for UTC.
Synapse Systems AB
Phone: +46 709 686 685
More information about the erlang-questions