From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <66e17ca3544b3b475439dbd93f5999f7@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cron and timesync
From: rog@vitanuova.com
In-Reply-To: <Pine.LNX.4.44.0307171223310.7478-100000@fbsd.cpsc.ucalgary.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Thu, 17 Jul 2003 20:26:07 +0100
Topicbox-Message-UUID: fa9d6286-eacb-11e9-9e20-41e7f4b1d025

>     ...                                 # time set by rtc (1am)
>     aux/timesync -n ntp.ucalgary.ca     # time still 1am
>     ...
>     auth/cron                           # time still 1am

i came across this problem in for another reason, and my assessment
was not that /dev/rtc wasn't being set (after all, everything reads
/dev/time, not /dev/rtc), but that aux/timesync returns immediately
without having synced the time.

it wouldn't be hard to do: it just requires a little synchronisation
between the forked process and its parent.  i'm afraid i didn't get
around to it (story of my life!).