Re: [chrony-dev] Wake from sleep on OS X |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] Wake from sleep on OS X
- From: Bryan Christianson <bryan@xxxxxxxxxxxxx>
- Date: Wed, 2 Dec 2015 11:01:18 +1300
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpcorp.com; s=a0-2; h=Feedback-ID:X-Smtpcorp-Track:To:Message-Id:Date: From:Subject; bh=UMIgGLh3/JOvHUKYl/obwP+qphyXJ5TS/w7uBaKwkF8=; b=0XpIXLB4zzX2 Dsk/Br4eCU8jo/iTW1i7CLwGYNN4iYENucqRR3OFGDydDC10SWEfP//OM4UHtbrPgOa+/rseOF/fx oJ+MW8dSG/dDAnWRuqrkIrUadytUM23tsl7C3YhjFSVHIFVQFDILRfSZ9MVLPj/IGTLIkgOOoKgB3 K2WC0LttUM5XsJSKpsFVLtJLoGElqk0TgztEJH+s2EsjOVTsPWq7bUstKBHVZAVK8ney57d0xDSpO K84qvrWfol3ZEhu6P/IQrFDV4V1BSTkSN6WVWLZ4w17wW9JGVO2AmvqHasGaBI4FJTm38KjYA1itE PBUK3iGCF8EFv7bNNKW1RA==;
- Feedback-id: 149811m:149811acx33YQ:149811sT3zs2fOqZ:SMTPCORP
> On 2/12/2015, at 10:40 AM, Bill Unruh <unruh@xxxxxxxxxxxxxx> wrote:
>
>
>
> William G. Unruh | Canadian Institute for| Tel: +1(604)822-3273
> Physics&Astronomy | Advanced Research | Fax: +1(604)822-5324
> UBC, Vancouver,BC | Program in Cosmology | unruh@xxxxxxxxxxxxxx
> Canada V6T 1Z1 | and Gravity | www.theory.physics.ubc.ca/
>
> On Wed, 2 Dec 2015, Bryan Christianson wrote:
>>
>> As for keeping the RTC clock in sync, ntpd appears to do this by calling settimeofday() each time it updates its stats files.
>>
>> I can add a scheduled event in the Mac OS X driver to call settimeofday() at regular intervals to force the RTC update. I would think an update every 15 minutes would not be too expensive.
>>
>>
>
> One of the features of chrony is that it can keep track of the rtc and its
> rate difference from 1 and its offset and use that information next time the
> rtc is used. However, if you keep resetting the rtc, that does not work. Thus if you switch your computer off for 3 days, this would allow chrony to
> compensate for the rate difference of the rtc clock from unity (ie 1 sec/sec) There is a problem with this in that the rate depends on tempreture, and the
> tempurature when the rate of the rtc is detrmined ( while the computer is
> running) and rate when it is off and cold can be different by a few PPM (eg
> second per month). The natural rtc rate can be off by up to 100PPM (seconds
> per day) Thus if you keep resetting the rtc (eg if you have the kernel's
> resetting of the rtc every 11 min) you do not have the rate correction. If you
> have the rate correction, the rtc can be out by many seconds. I do not know if
> the OSX kenel has that 11 min mode that the linux kernel has. chrony
> deliberately disables that mode on linux so it can measure the rtc clock drift
> rate.
I didn't know that - thanks.
In light of that, I am not sure how the RTC should be synchronised. As far as I can tell there is no equivalent to hwclock to force synchronisation and that it is dependent on the user either setting the time manually or running ntpd
--
Bryan Christianson
bryan@xxxxxxxxxxxxx
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.