https://bugzilla.novell.com/show_bug.cgi?id=774502 https://bugzilla.novell.com/show_bug.cgi?id=774502#c19 --- Comment #19 from Marius Tomaschewski <mt@suse.com> 2013-01-17 10:13:15 UTC --- (In reply to comment #18)
I dont feel that this is a configuration issue, but correct me if I'm wrong. IMHO ntp should restart after each network connection (i.e. after resume from suspend)
Not any more: - Fixed netconfig/ntp-runtime to not use try-restart as its start may block for a while, so just add servers ourself in background. When ntpd is not running (not yet started), the ntp init script will pickup our servers later at ntp start (bnc#780644). In another words, when the network starts, and gets a lease including an ntp server, 'echo "addserver xxx" | ntpdc' is used now to sync the time and the ntp servers are written to /var/run/ntp/servers-netconfig. When ntpd is already started [e.g. lease renew], ntpdc makes the sync, otherwise the ntp init script will pick up the server list from the /var/run/ntp/servers-netconfig file when it (re)starts. So (at boot) first the network starts and does nothing with ntp (ntpdc addserver fails). Then, the ntpd starts and the init script makes the ntpdc addserver call. Further, as I wrote in e.g. comment 9, do not use STARTMODE='ifplugd' (On-Cable-Connect or something like this in yast2). With STARTMODE='ifplugd', it is required to disable ntp & nfs start (all services which can't be started without network up) at boot time and use ifup(8) or ifservices(5) hooks to start them when network goes up. AFAIS, there is no dependency (Required-Start, Should-Start) to ntp ($time) in /etc/init.d/nfs at all and this is IMO the problem here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.