From: erik quanstrom <quanstro@quanstro.net>
To: corey@bitworthy.net, 9fans@9fans.net
Subject: Re: [9fans] how to fix: 'arena arenas00 creation time after last write time'
Date: Tue, 28 Jul 2009 21:04:02 -0400 [thread overview]
Message-ID: <7a8ccd132befffa2a88cd575a4bfe8ea@quanstro.net> (raw)
In-Reply-To: <200907281742.23251.corey@bitworthy.net>
> Approximately how long is 'some time'? (so I know how long to wait)
5-10 minutes. /sys/log/timesync should be informative.
> 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...
impossible. venti doesn't even share a namespace with you.
if you want to prove me wrong, modify /sys/src/cmd/vent/srv/utils.c:/^now
like so (untested)
u32int
now(void)
{
uint t;
static uint t0, jump;
t = time(nil);
if(t < t0){
if(jump == 0)
fprint(2, "now earlier than before: %ud %ud\n", t0, t);
jump = 1;
return t0;
}
jump = 0;
t0 = t;
return t;
}
- erik
next prev parent reply other threads:[~2009-07-29 1:04 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
2009-07-29 1:04 ` erik quanstrom [this message]
[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=7a8ccd132befffa2a88cd575a4bfe8ea@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=corey@bitworthy.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).