Control: tags -1 moreinfo Hi Christian,
On Thu, Feb 01, 2018 at 09:43:07AM +0100, Christian Ehrhardt wrote:
Package: chrony Version: 3.2-2 Description: Conversions of old $network behavior should be on online target [2]. And I think for chrony it makes sense to start when it really is online to not rely too much on the hooks to set it online.
Prior to the 3.0-1 release, we used to heavily rely on the hooks as the time sources weren’t polled by chronyd due to the use of the “offline” option. This behaviour wasn’t satisfactory to me, so I decided it was time to change it for Debian Stretch so what's happening now is: - If the network is up:
- chronyd starts
- chronyc online runs, but doesn't actually do anything
- names are resolved
- sources are added as online
- burst is executed
- If the network is down:
- chronyd starts
- chronyc online doesn't run
- chronyd is periodically trying, in exponentially increasing
interval, to resolve the pool.ntp.org name, but fails
- network is up
- chronyc online runs from the hooks
- chronyd resolves the name
- sources are added as online
- burst is executed
Also, I think chronyd should be started quite early so the clock
frequency offset is set from the drift file. It should also be noted
that when used with a reference clock, chronyd does not necessarily need
network nor DNS.
However, if starting chronyd after the network is fully up is something you really are looking for, I think you should start it after nss-lookup.target‽
Ubuntu-Bug: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1746458 Fix-in-Review: https://git.launchpad.net/~paelzer/ubuntu/+source/chrony/commit/?id=2baea8e0bde5d6a1de60098019fb658a4a94d489[1]: https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/336844 [2]: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ -- Christian Ehrhardt Software Engineer, Ubuntu Server Canonical Ltd
Cheers, Vincent
signature.asc
Description: PGP signature
