> The hosts in question were upgraded from prior LTS, so they would have
inherited ntpdate from there.
Thanks. We didn't have it removed for upgraders, so I guess that's not
happening by any other mechanism. I'm not sure we should do that either.
The only packaging mechanisms I can think of would
Removing ntpdate should remove the if-up script, so I imagine that would
"resolve" the bug by way of workaround.
The hosts in question were upgraded from prior LTS, so they would have
inherited ntpdate from there. I wasn't aware of the changes to sunset
it in the current release.
--
You
Please see: https://lists.ubuntu.com/archives/ubuntu-
devel/2016-August/039484.html
Summary: in Ubuntu, we don't expect to use ntpdate any more. We're
leaving bugs in ntpdate packaging behind, on the basis that ntpdate no
longer needs to be installed by default.
Can you fix the problem by
I actually think I gave a fairly thorough description of the problem and
it has nothing to do with ntpd configuration. I even said specifically
that I can manually start/stop ntpd and it works - configuration valid
and operational.
The problem is /etc/network/if-up.d/ntpdate starting and
My information may be out of date, instead of using -I you may also try
adding the following:
interface ignore wildcard
interface listen 127.0.0.1
interface listen ::1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Do you want NTP to listen on all addresses? That is not typically what
someone will want. That is why there is the -I option (e.g. -I
127.0.0.1) that can be added to the command line in /etc/default/ntp to
listen
6 matches
Mail list logo
