On 12/05/18 07:45, Richard Laager wrote:
> We definitely need to avoid using the config file if it exists, or else
> a reboot to clear /run, or a manual deletion of /run/ntp.conf.dhcp,
> would be necessary for the IGNORE_DHCP=yes change to take effect.
I'd probably call it DISABLE_DHCLIENT_HOOK or something a touch more
descriptive, but happy to go with whatever
> You make a good point about spurious restarts, which are especially
> harmful to ntpd. How do you feel about the following patch (untested):
...
> diff --git a/debian/ntp.dhcp b/debian/ntp.dhcp
> index eedf6d9..7ca0927 100644
> --- a/debian/ntp.dhcp
> +++ b/debian/ntp.dhcp
> @@ -3,7 +3,13 @@ NTP_DHCP_CONF=/run/ntp.conf.dhcp
>
>
> ntp_server_restart() {
I'd put the test at the start of ntp_servers_setup_add myself, but
again, up to you.
That still means the remove hook is active, but that should already only
trigger a restart if there was actually a config to remove.
