From: quanstro@quanstro.net (erik quanstrom)
Subject: [9fans] time zones
Date: Sun, 27 Mar 2011 22:04:43 -0400 [thread overview]
Message-ID: <17e041451f66dd88d5ffd91161fc0857@brasstown.quanstro.net> (raw)
In-Reply-To: <6ae2ef4c91c9f590952b54e2dfb27134@gandalf.orthanc.ca>
[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
next prev parent reply other threads:[~2011-03-28 2:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 22:35 Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-03-28 2:04 ` erik quanstrom [this message]
2011-03-28 4:25 ` Lyndon Nerenberg
2011-03-31 19:32 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-03-31 19:55 ` erik quanstrom
2011-03-31 20:26 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-03-31 23:08 ` erik quanstrom
2011-03-31 23:24 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-04-01 7:21 ` Richard Miller
2011-03-31 20:26 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
-- strict thread matches above, loose matches on Subject: below --
2011-03-27 22:33 Lyndon Nerenberg (VE6BBM/VE7TFX)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17e041451f66dd88d5ffd91161fc0857@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).