But that's not a problem with time-admin, which is not supposed to control ntpdate at all. It's just that ntpdate shouldn't run by ifup when interfaces are enabled. Else, there's no point in optionally installing the ntp daemon.
I suspect ntpdate is not run when your connections are managed using NetworkManager instead of ifup, which could explain why this bug has gone unnoticed. If it's the case, that would be a workaround, anyway NetworkManager is the preferred way to handle connections on desktops now. I don't think disabling ntpdate by default would hurt, no application should rely on it. >From https://help.ubuntu.com/10.04/serverguide/C/NTP.html: > Ubuntu comes with ntpdate as standard, and will run it once at > boot time to set up your time according to Ubuntu's NTP server. So it may well be that server settings are used on desktops, where it doesn't really make sense, since we get an inconsistent behavior with the GUI. ** Package changed: gnome-system-tools (Ubuntu) => ntp (Ubuntu) ** Changed in: ntp (Ubuntu) Status: Incomplete => Triaged ** Summary changed: - no user interface to configure whether time synchronisation is always made on establishing the network connection. + ntpdate shouldn't be run by ifup on desktops (conflict with time-admin's NTP options) -- ntpdate shouldn't be run by ifup on desktops (conflict with time-admin's NTP options) https://bugs.launchpad.net/bugs/585053 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in ubuntu. -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
