Looks like it's actually quite easy to take the fallback option. The attached patch makes ntpdate use /etc/ntp.conf only if it's readable and non-empty. This fixes the breakage in case a tool has created an empty configuration file for ntp.conf. The ntp configuration in /etc/ntp.conf is still used if the ntp package is installed and brings with it a proper configuration file (or if one happens to exist for some other reason).
** Attachment added: "Only use ntp.conf for servers if it's non-empty" http://launchpadlibrarian.net/12732123/ntpdate-dont-use-empty-ntp-config.patch -- ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file. https://bugs.launchpad.net/bugs/83604 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
