From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <20090626232256.0110babe.eekee57@fastmail.fm> Date: Fri, 26 Jun 2009 17:39:12 -0700 Message-ID: <7d3530220906261739g2ea172dv90602338965a8291@mail.gmail.com> From: John Floren To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] timesync -r not working? Topicbox-Message-UUID: 0fa6f3e6-ead5-11e9-9d60-3106f5b1d025 On Fri, Jun 26, 2009 at 4:57 PM, erik quanstrom wrot= e: >> > > The script runs at boot, the echo tells me that much, but the time i= s not set, perhaps as if timesync -r is not working. To be specific the dat= e a few minutes after booting is Sun Jan =C2=A02 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 stra= nge instead. > > i wouldn't classify doing what the man page says it does > as something "really strange". =C2=A0if 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. John --=20 "I've tried programming Ruby on Rails, following TechCrunch in my RSS reader, and drinking absinthe. It doesn't work. I'm going back to C, Hunter S. Thompson, and cheap whiskey." -- Ted Dziuba