[LINK] If a clock ticks in a Klearphelled forest, ...

[Kim Holburn]

On 2008/Mar/31, at 2:52 AM, Roger Clarke wrote:
> At 10:26 +1000 31/3/08, Jan Whitaker wrote:
>>  ... My computer also flipped, so I had to fix that.  ...
>
> Yes, we'd noticed, because the thread was turning up in the mailbox  
> out of order  (:-)}
>
> But that's odd.
>
> Surely standard time-synch utilities on MS work as well as they do  
> on Macs?


Macs, being unix based use GMT.  A time is only converted to the  
local timezone to be viewed on the screen.  Timestamps will always be  
correct and viewed time will be as accurate as your TZ file.   
Timestamps will always be correct.  For a non timezone changing  
computer the timestamps as viewed will always be correct.  On a  
computer that changes timezones (ie a laptop) the local time of a  
timestamp my not be right in terms of the original local time but  
will be correct in terms of your current local time.

Windows on the other hand normally uses local time.  When changing  
timezones or daylight saving time the underlying clock changes.   
Timestamps on files and logs are not accurate any more.

http://en.wikipedia.org/wiki/Time_zone#Microsoft_Windows
> Microsoft Windows
>
> Windows based computer systems normally keep system time as local  
> time in a particular time zone. A system database of timezone  
> information includes the offset from UTC and rules that indicate  
> the start and end dates for daylight saving in each zone.  
> Application software is able to calculate the time in various  
> zones, but there is no standard way for users from multiple zones  
> to use a single server and have their own local time presented to  
> them.


--
Kim Holburn
IT Network & Security Consultant
Ph: +39 06 855 4294  M: +39 3494957443
mailto:kim at holburn.net  aim://kimholburn
skype://kholburn - PGP Public Key on request

Democracy imposed from without is the severest form of tyranny.
                           -- Lloyd Biggle, Jr. Analog, Apr 1961