Tony Hoyle wrote:
David J Taylor wrote:
Interesting - it's a problem which Windows doesn't have.
Windows doesn't use or store UTC so its timezone support is purely
cosmetic (hence the well known bug where the timestamps of all the
files on the system shift +/- 1 hour during DST boundaries).
Unix has the ability for each process/user to operate within their own
You either have the ability for each user (indeed each process) to
have its own timezone. OTOH 99% of services really don't care - they
operate on UTC. The for the most part the timezone is a user level
artefact that affects the shell.
It's simply a different way of looking at it - a single user centric
vs. a multi user centric.
Tony
Tony,
Thanks for your insight, but you are wrong about Windows.
Windows uses UTC throughout internally, and the time zone setting controls
how the internal UTC time is presented to the user. As the file
timestamps (with NTFS etc.) are stored in UTC, you would /expect/ the
presented timestamp to change when DST is, or is not present. It's not a
bug, but correct behaviour, IMHO. [Otherwise you could have two files
created an hour apart showing the same timestamp].
UNIX is doing the same thing - storing UTC internally and presenting to
the user according to their preferences. Whether allowing a per-process
timezone setting is a "good thing" or not is an argument for another day!
David
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
