Re: [9fans] cron and timesync

[David Presotto <presotto@closedmind.org>]

[-- Attachment #1: Type: text/plain, Size: 451 bytes --]

I changed timesync to not background until it's tried at least once
to sync up.  That means you'll be within 10 seconds of real time
when it returns if it managed to find a time source; timesync just
sets the time if off by more than 10 seconds and tries to sneak
up on the correct time otherwise.

I could wait for time to get within the accuracy limit, but that
could take a while.  10 seconds should be good enough for the
reported problem.

[-- Attachment #2: Type: message/rfc822, Size: 2121 bytes --]

From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cron and timesync
Date: Thu, 17 Jul 2003 13:21:34 -0700
Message-ID: <fe08afabb4b67ac2e23de776d0268256@collyer.net>

I invoke this function early in cpurc:

fn timesync {
	aux/timesync -nl -d /sys/log/timesync.d -a 100000 $*
	# the alpha port currently has no #r
	if (test -e '#r/rtc') @ {
		sleep 600				# let ntp do its thing
		awk '{print $1}' /dev/time >'#r/rtc'	# fix the hardware clock
	} &
}

I don't start cron until I've started venti and fossil, and that takes
long enough that timesync should have reset /dev/time by then.