9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] timesync -r not working?
Date: Sat, 27 Jun 2009 08:46:53 +0100	[thread overview]
Message-ID: <20090627084653.70b02cfb.eekee57@fastmail.fm> (raw)
In-Reply-To: <7d3530220906261739g2ea172dv90602338965a8291@mail.gmail.com>

On Fri, 26 Jun 2009 17:39:12 -0700
John Floren <slawmaster@gmail.com> wrote:

> On Fri, Jun 26, 2009 at 4:57 PM, erik quanstrom<quanstro@quanstro.net> wrote:
> >> > > The script runs at boot, the echo tells me that much, but the time is not set, perhaps as if timesync -r is not working. To be specific the date a few minutes after booting is Sun Jan  2 18:30:36 GMT 2000.
> >> >
> >> > i believe timesync is setting the system clock from /dev/rtc, not the other way
> >> > around.
> >>
> >> Yeah, that's what I expect timesync to do, but it's doing something strange instead.
> >
> > i wouldn't classify doing what the man page says it does
> > as something "really strange".  if you want the converse,
> > then just execute "date -n >/dev/rtc".
> >
> > - erik
> >
> >
> 
> I'm pretty sure he's *trying* to get the time from /dev/rtc, not
> trying to set it.
> 

You'd be right.

I've found I don't seem to need timesync, the system time & /dev/rtc alike seem to stay in sync with the host without it, but I'm still curious why timesync -r should mess up the system time so badly.

Perhaps /dev/rtc and the system time are linked on some architectures, so that setting one sets the other and so timesync -r gets in a mess. Just a guess.

-- 
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer



  reply	other threads:[~2009-06-27  7:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 18:45 Ethan Grammatikidis
2009-06-26 19:48 ` erik quanstrom
2009-06-26 22:22   ` Ethan Grammatikidis
2009-06-26 23:57     ` erik quanstrom
2009-06-27  0:39       ` John Floren
2009-06-27  7:46         ` Ethan Grammatikidis [this message]
2009-06-27  8:36           ` Federico G. Benavento
2009-06-27 18:02             ` Ethan Grammatikidis
2009-06-28  0:05               ` Federico G. Benavento
2009-06-28 11:43                 ` Ethan Grammatikidis
2009-06-28  0:17               ` cinap_lenrek
2009-06-28 11:43                 ` Ethan Grammatikidis
2009-06-29  9:31 ` Balwinder S Dheeman
2009-06-29 14:27   ` Ethan Grammatikidis
2009-06-29 14:38     ` erik quanstrom
2009-07-07  9:20     ` Steve Kostecke

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=20090627084653.70b02cfb.eekee57@fastmail.fm \
    --to=eekee57@fastmail.fm \
    --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).