From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 29 Jun 2009 15:27:10 +0100 From: Ethan Grammatikidis To: 9fans@9fans.net Message-Id: <20090629152710.77b57d9a.eekee57@fastmail.fm> In-Reply-To: References: <20090626194523.aff8f4db.eekee57@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [9fans] timesync -r not working? Topicbox-Message-UUID: 10e79b52-ead5-11e9-9d60-3106f5b1d025 On Mon, 29 Jun 2009 09:31:51 GMT Balwinder S Dheeman 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