[chrony-dev] chronyd feature request: aggressive mode |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-dev] chronyd feature request: aggressive mode
- From: "Gerriet M. Denkmann" <gerrietm@xxxxxxxxxx>
- Date: Wed, 11 Dec 2019 15:57:50 +0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=1a1hai; t=1576054675; bh=mlKUnWG9v/iAW6OprRopLf0TeURm+PgeFUSUI6c+NWY=; h=From:Content-Type:Subject:Message-Id:Date:To; b=igGen6GIvf2X0UqHAI1zhOCcLBDwxWOjljRVcgYTnv33wyg0Tl+dZ0d5hy0z7nIQR iulMPGIHHgRUqNy8IgSGBT1CKrydxCT9ohEYJ16s+jY+AlEfyl+KMIKI6kvGb1rIuK ZVtpVTuQOmK8ahmlCInOx3GONa7nvQasGn7Djd9Pcdfv9gfnpHAaChtHZ2HI+AtSEC rcK0Akl1ws3tvY6xQzPniJyZudNQUmOA5e+B9l8E0gTM+HZfYgWZeUEY370VURJx5P Epw77LGL0ko/a9urQ44ViYfM077qG4TpJgvfkw9DEePjicenTZD+Cunn+RJ2cX5AVy Qrs0zR1jiGXeA==
chronyd does a good job of keeping the time in sync without big changes in the drift (freuquency).
But there are a few situations, where an “aggressive mode” (i.e. drastically increasing the frequency) would be more appropriate:
(1) at start
(2) when there is a big time-error (ntp-time - cpu-time) (e.g. > 2 sec)
(3) (at least on macOS) when the computer wakes up from sleep.
(1) my computer usually runs for months without shut-down or reboot.
So maybe chronyd already does the right thing in this situation.
(2) I have seen rather big frequencies (up to 20-fold of normal drift resulting from a time-error of 45 sec).
So this case also seems to be handled ok.
(3) On macOS there is usually a time-error of -1 … +2 seconds upon wake up. (rarely more than 2 sec) (this is only true with rtcsync working).
The problem here: when chronyd thinks that all is stable, the next check with ntp might by delayed by up to 17 min (sometime up to 53 min).
And for usual errors < 2 sec, case (2) does not apply. This results in almost an hour (depending of course on the wake-up error) until the time is correct again.
Here I would like to see an “aggressive mode” until the time-error is down to a few msec.
Would this be possible?
Or are there reasons, why this is *not* a good idea?
Gerriet.
--
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.