Roy Marples <roy%marples.name@localhost> writes: > On 11/10/2020 11:42, Havard Eidnes wrote: >> The question is whether we ought to do something to break this >> circular dependency in our default install by specifying one or two >> (depending on "minsane" and resiliency conciderations) ntp servers >> via IP address? The issue then becomes "which IP address(es)" and >> "how can that scale"? > > So the 50-ntp.conf dhcpcd hook script sets up ntp.conf with the IP > addresses of NTP servers to use given from DHCP. > If the ntp.conf file has changed as a result, the hook script will restart ntpd. > If ntpd was passed the -g option to startup then it will ensure that > the initial sync works no matter the state of the clock. > > We might want to consider adding -g to the default ntpd_flags. That makes sense to me. As I understand it, the lack of -g (refusal to make a big adjustment) is based on a notion of the system being more stable than systems typically are. I think we are not running into this more only because of the custom of ntpdate.
Attachment:
signature.asc
Description: PGP signature