From mboxrd@z Thu Jan  1 00:00:00 1970
From: quanstro@quanstro.net (erik quanstrom)
Date: Sun, 27 Mar 2011 22:04:43 -0400
Subject: [9fans] time zones
In-Reply-To: <6ae2ef4c91c9f590952b54e2dfb27134@gandalf.orthanc.ca>
References: <6ae2ef4c91c9f590952b54e2dfb27134@gandalf.orthanc.ca>
Message-ID: <17e041451f66dd88d5ffd91161fc0857@brasstown.quanstro.net>
Topicbox-Message-UUID: c2690bbc-ead6-11e9-9d60-3106f5b1d025

[no matches in 365 files]
On Sun Mar 27 18:35:55 EDT 2011, lyndon at orthanc.ca wrote:
> Even stranger, newfie time is not making sense.  The Newf's have
> been half an hour off the rest of the world for ages. Yet:
> 
> lyndon at frodo% cat Canada_Newfoundland | tzdump
>                          NST	                         NDT

nope.  the timezone is correct.  i think the output of
tzdump is confusing.  for us eastern, here's an example

; for(i in 4 5)date `{echo '1081044000 + 3600*'$i|hoc}
Sun Apr  4 01:00:00 EST 2004
Sun Apr  4 03:00:00 EDT 2004

and for newfoundland

; ifs=() timezone=`{cat tz/Canada_Newfoundland}for(i in 3 4)date `{echo '1081044000 + 3600*'$i|hoc}
Sun Apr  4 01:30:00 NST 2004
Sun Apr  4 03:30:00 NDT 2004

the reason for the confusion, is that the localtime
applies the offset before applying the dstpairs.
(/sys/src/libc/port/ctime.c)  i belive i tripped on this
when i did the work for the us zones.

if there's a bug, it's in tzdump.

- erik