From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 27 Jun 2009 08:46:53 +0100 From: Ethan Grammatikidis To: 9fans@9fans.net Message-Id: <20090627084653.70b02cfb.eekee57@fastmail.fm> In-Reply-To: <7d3530220906261739g2ea172dv90602338965a8291@mail.gmail.com> References: <20090626232256.0110babe.eekee57@fastmail.fm> <7d3530220906261739g2ea172dv90602338965a8291@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] timesync -r not working? Topicbox-Message-UUID: 0faf5388-ead5-11e9-9d60-3106f5b1d025 On Fri, 26 Jun 2009 17:39:12 -0700 John Floren wrote: > On Fri, Jun 26, 2009 at 4:57 PM, erik quanstrom wr= ote: > >> > > 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 d= ate a few minutes after booting is Sun Jan =A02 18:30:36 GMT 2000. > >> > > >> > i believe timesync is setting the system clock from /dev/rtc, not th= e other way > >> > around. > >> > >> Yeah, that's what I expect timesync to do, but it's doing something st= range instead. > > > > i wouldn't classify doing what the man page says it does > > as something "really strange". =A0if you want the converse, > > then just execute "date -n >/dev/rtc". > > > > - erik > > > > >=20 > I'm pretty sure he's *trying* to get the time from /dev/rtc, not > trying to set it. >=20 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 ti= mesync -r should mess up the system time so badly. Perhaps /dev/rtc and the system time are linked on some architectures, so t= hat setting one sets the other and so timesync -r gets in a mess. Just a gu= ess. --=20 Ethan Grammatikidis The lyf so short, the craft so long to lerne. -- Chaucer