https://bugzilla.novell.com/show_bug.cgi?id=337075#c6
--- Comment #6 from Martin Burnicki
1) (yes, i'm native german) the person in the thread you pointed above used networkmanager so the bug finding is simple :-D
2) comment #1 reffers partly on the nm-ntp problem but the initial problem is the same as here.
3) i'm not sure which kind of network managment tool is used as standard (nm or ifup/ifdown)
From my observations nm is used as default on laptops whereas ifup/ifdown is preferred on workstations/servers. This makes sense, IMHO.
4) if you type in rcntp restart the init script will stop and start the service. the stop contains in line #211 a killproc. the "old" ntp should not listen on the device/port.
Yes, I know. If I type "rcntp restart" after the final runlevel has been reached then ntpd starts up and works fine, even if it ntpd has not been running before.
5) ntp will be restarted _only_ with networkmanager enabled. please check this with # grep NETWORKMANAGER /etc/sysconfig/network/config
pc-martin5:~ # grep NETWORKMANAGER /etc/sysconfig/network/config NETWORKMANAGER=no # This variable has no effect if NETWORKMANAGER=no # This variable has no effect if NETWORKMANAGER=no The output above is from the same systen as the messages in my initial report, so this clearly indicates that it is started twice even though networkmanager is _not_ used.
6) i take a look on the "-g" option but i'm working on a other solution to fix the nm-ntp problem. this bugfix should fix your problem (if you are not using nm), too.
I'm involved in the development of the NTP package (search for "burnicki" in NTP's bugzilla), though I'm mainly testing and trying to find/fix bugs. So if you let me know some details I can give you some hints or comments from NTP's point of view ... -- 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.