On 07/14/2018 10:56 PM, Richard Laager wrote:
> Have you tried removing ntp-servers from /etc/dhcp/dhclient.conf?
>
> ntpsec's README.Debian (inherited from ntp) says that is the place to
> turn off this behavior.
>
> Does that work? If so, is an option in the ntpsec package still necessary?
Have you tried removing ntp-servers from /etc/dhcp/dhclient.conf?
ntpsec's README.Debian (inherited from ntp) says that is the place to
turn off this behavior.
Does that work? If so, is an option in the ntpsec package still necessary?
--
Richard
On 12/05/18 06:02, Richard Laager wrote:
> I looked through the git history, and I can't find a good reason for why
> this "-nt" test existed. It's unclear if that came from an older version
> of ntp or was something I cooked up.
I'd guess it predates /run's existence where a lagged file in
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
On 05/11/2018 02:56 AM, Julien Goodwin wrote:
> Please either add a method to disable the entire hook (I'd prefer this
> to avoid additional service restarts), or at least add a variable to
> /etc/default/ntp that will cause /run/ntp.conf.dhcp to not be used.
For the ntp package, there's a
On 05/11/2018 02:56 AM, Julien Goodwin wrote:
> I also think the test in the init script should probably change to
> if -e /run/ntp.conf.dhcp, since /run is created on boot, otherwise
> there's surprising behaviour if the admin edits ntp.conf, restarts the
> service, then discovers a DHCP
Package: ntpsec
Version: 1.1.0+dfsg1-1
Severity: normal
The DHCP hook[1] is currently unconditionally used if a machine has a DHCP
assigned address.
Please either add a method to disable the entire hook (I'd prefer this
to avoid additional service restarts), or at least add a variable to
7 matches
Mail list logo
