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: Mon, 29 Jun 2009 15:27:10 +0100	[thread overview]
Message-ID: <20090629152710.77b57d9a.eekee57@fastmail.fm> (raw)
In-Reply-To: <uinfh6xpoh.ln2@news.homelinux.net>

On Mon, 29 Jun 2009 09:31:51 GMT
Balwinder S Dheeman <bsd.SANSPAM@cto.homelinux.net> wrote:

> On 06/27/2009 12:16 AM, Ethan Grammatikidis wrote:
> > I'm running plan 9 in qemu, I want to use the qemu-emulated hardware clock for the plan 9 time because it keeps the same time as the host.
> >
> > I made a script to be sourced from cpurc:
> >
> > 	#!/bin/rc
> >
> > 	echo '> starting timesync'
> >
> > 	if (! test -e '/dev/rtc')
> > 		bind -a '#r' /dev
> > 	aux/timesync -r
> >
> > 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.
> >
> > Should I not use timesync at all? I ask because $boottime (which is set before timesync is started) contains a reasonable date.
>
>
> I also run Plan 9 in qemu, the:
>
> 	aux/timesync -n pool.ntp.org
>
> solved a similar problem here.

ty. That's what was in my cpurc, I don't know whether as a default or from tinkering with it a few years ago. I didn't want to load ntp.org with multiple requests from the same machine.


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



  reply	other threads:[~2009-06-29 14:27 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
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 [this message]
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=20090629152710.77b57d9a.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).