| [chrony-users] Handling offset when Mac wakes from sleep |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] Handling offset when Mac wakes from sleep
- From: Bryan Christianson <bryan@xxxxxxxxxxxxx>
- Date: Sun, 13 Jun 2021 11:38:57 +1200
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpcorp.com; s=a1-4; h=Feedback-ID:X-Smtpcorp-Track:To:Date:Message-Id: Subject:From:Reply-To:Sender:List-Unsubscribe; bh=AuusPb4z0xDUzG/ufbA1GBiAXVfq/uSD4MEGAZVGvts=; b=vXNI8/uCRcWeCmW9PbDRKnkn07 lIv+iSgk+ijkQcrIE6d6l7egIqGLkSG8cYtZtG2gip7MxgYLOXJLwi+v9xsG4bFi7cpBlc7XViQbI 89KWwYbv/78S4S1It1D5ISTfdpou1Rxvni80VGeMwDlgFf/6jP0+O59HFmREef1dXWtwnfpxFk2sP PeF/kKxK9dacqiZAbccJdZ2TOnAEYdBWYZfharM5FMBocyjV+4YO5sGq2FolzbHUhNkoJEgtes6oW fTas5IKUIj/eiRCCbLm0DhcWhc3FO4Ygs+l2Z9qP0es1UWs8VA89zVVZUkT6iz4m5eMqLCcopwhQm +PhQl6ZA==;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=whatroute.net; i=@whatroute.net; q=dns/txt; s=s149811; t=1623541160; h=from : subject : to : message-id : date; bh=AuusPb4z0xDUzG/ufbA1GBiAXVfq/uSD4MEGAZVGvts=; b=Tfyfwf5M0fFlE0VsR2HA/o7mpJDhR3SCITd1qrRzVTojqnGrG2olvQmN/GuvhJm86vUUmk BUGhYMPExdL3IPa82jGEkY26VAI3Ypk0b2+5+EuorZNIOGxcgjI6kS8JUkIDbZe45vWpsjeB 81vylHLuVezuMi1iHGSWppACViGSMOZYvprUf8fIY+d9GTj57CUJg7E0kMjzjDp7e0rsNU8w wNg/Z2Oj7fJnKXH17NvoyPVuYf9NI9yakbF+Cf/YNwsxBMMnPgj+NC7UE7Pz+0NRnSVESgMV ObH4MEZ8DIAlHMDoIySZaCs2Aufi3JAaZljq8i83a0K4vbGweyqeTkgw==
- Feedback-id: 149811m:149811acx33YQ:149811spoRpZHZU_
I have had a number of requests/complaints from Mac users about the how long it takes for chrony to converge again after the OS has been sleeping. As far as I can tell they are using chrony to discipline the clock but are not providing NTP services to the lan - i.e. if they were providing service to a lan then it would make no sense to allow the machine to sleep.
I have written a small daemon, activated by a wakeup event from OS, that will quickly synchronise the clock, but before I release it to the wild I thought it best to get some opinions.
The daemon works by running the following commands with the default settings shown
On wakeup:
chronyc burst 4/4
sleep 10
chronyc makestep
I have allowed the user to override the arguments to the burst command and also to configure the sleep time. A network/mask can also be specified.
Will these defaults be generally useful? I have no idea how many servers users usually configure but I expect it would be 4 or 5 of they are using the time.apple.com pool or pool.ntp.org
Some public NTP servers don't like clients to 'burst'. However I have yet to receive a complaint, but is this something to be concerned about?
--
Bryan Christianson
bryan@xxxxxxxxxxxxx
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.