Pedro, That's a good catch. However, I don't suppose that change is going to happen for hardy since ubuntu-minimal still seems to depend on ntpdate in the current development branch. The time-admin package in hardy still seems to generate an empty /etc/ntp.conf when the synchronize button is pressed, causing further synchronization attempts to fail. Since hardy is going to be a LTS release, this functionality may be broken for a long time, and a temporary workaround (not trying to use ntp.conf or its relatives if they're empty) is easy. Getting rid of ntpdate may be the long term solution for upcoming Ubuntu releases, of course.
Even if we fixed time-admin, where the actual bug is (creating the empty configuration file), such a file would still remain in systems where a buggy time-admin has been used before. Thus working around it in the ntpdate configuration is probably the simplest way to get ntpdate working reliably, and it's also pretty much non-destructive (why would you want to have and use an empty ntp configuration file in the first place?). The patch I attached earlier was for gutsy. I'm now attaching a similar patch for hardy. ** Attachment added: "Only use ntp.conf for servers if it's non-empty (for hardy)" http://launchpadlibrarian.net/12784931/ntpdate-dont-use-empty-ntp-config-hardy.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
