From: Corey <corey@bitworthy.net>
To: 9fans@9fans.net
Subject: Re: [9fans] how to fix: 'arena arenas00 creation time after last write time'
Date: Tue, 28 Jul 2009 17:42:23 -0700 [thread overview]
Message-ID: <200907281742.23251.corey@bitworthy.net> (raw)
In-Reply-To: <09c88626d985457ecaa621715f4f1af0@quanstro.net>
On Tuesday 28 July 2009 16:50:15 erik quanstrom wrote:
> > #6 - reboot, (first-time login), as glenda:
> > - remove -L switch from $TIMESYNCARGS in /rc/bin/termrc
>
> if the time was already correct modulo timezone, why did you do this?
>
My (ill-founded?) reasoning went like this:
* -L is for if "the real time clock is in local time rather than GMT"
* my bios rtc is not set in local time, it is in UTC time
* therefore, I do not want the -L switch passed to aux/timesync
> also, after allowing the machine to run for some time, does timesync
> cause the system time (date -n) to jump? i.e. is the nvram time wrong.
>
I do not know. I'll try this though.
Approximately how long is 'some time'? (so I know how long to wait)
> you don't say, but i'm quite sure that on reboot you'll find
> that date -n will have jumped by 7 hrs + whatever time
> it took to do the reboot. bios time will not be affected.
>
I'll look into this also, thanks for the suggestion.
> > - as an adm user: cp /adm/timezone/US_Arizona
> > /adm/timezone/local
>
> you should note that this has absolutely zero to do with
> timesync, the bios clock or tea in china. this changes the
> human readable time only. fossil and venti just don't care.
>
Please see below. My experience is indicating a different reality,
or I'm still not interpreting my experience correctly.
Clearly no one's under any obligation to help me see the light, but
I do value the time and effort spent attempting to do so!
And I realize that it's entirely possible I'm just incurably chrono-impaired.
> just as a note, you can make timezones appear instantly by
> ; timezone = `{cat /adm/timezone/local}
> ; date
>
Yes I was aware of this, although I did it more naively (cp
/adm/timezone/local /env/timezone).
My point though is that yes, it makes the timezone change take
effect immediately - and it likewise causes the 'creation time after
last write time' /dev/kprint's to appear instantly as well...
And yet, timezone does not affect venti?
> and you can always get gmt time by
> ; timezone=() date
>
Good to know - thank you.
next parent reply other threads:[~2009-07-29 0:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <09c88626d985457ecaa621715f4f1af0@quanstro.net>
2009-07-29 0:42 ` Corey [this message]
2009-07-29 1:04 ` erik quanstrom
[not found] <664879e97485933b3ca1bc9e37760730@quanstro.net>
2009-07-28 5:05 ` Corey
2009-07-28 13:22 ` erik quanstrom
2009-07-28 15:16 ` Russ Cox
2009-07-28 22:14 ` Dave Eckhardt
2009-07-28 22:16 ` erik quanstrom
2009-07-28 22:56 ` Corey
2009-07-29 1:42 ` Russ Cox
2009-07-29 4:24 ` Corey
2009-07-29 8:54 ` Corey
2009-07-29 14:02 ` Steve Simon
2009-07-29 14:48 ` Russ Cox
2009-07-28 22:42 ` Corey
2009-07-28 23:50 ` erik quanstrom
[not found] <26a2b1a9fb6ec5947c440b48b8bde174@quanstro.net>
2009-07-27 23:56 ` Corey
2009-07-28 0:35 ` erik quanstrom
2009-07-28 8:52 ` Steve Simon
2009-07-27 1:03 Corey
2009-07-27 16:28 ` Russ Cox
2009-07-27 20:31 ` Corey
2009-07-27 20:38 ` erik quanstrom
2009-07-27 20:58 ` Corey
2009-07-27 22:49 ` Corey
2009-07-27 22:52 ` erik quanstrom
2009-07-27 20:56 ` Lyndon Nerenberg
2009-07-30 4:15 ` Corey
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=200907281742.23251.corey@bitworthy.net \
--to=corey@bitworthy.net \
--cc=9fans@9fans.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).