Bugzilla – Bug 139589
yast: NTP setup. Restarting fails
Last modified: 2006-01-11 13:20:29 UTC
GNOME default installation via SLP. Select 'Use Random Server from pool' and 'Finish'. Results in error msg "Cannot adjust 'NTP' Service" (BTW, do not quote NTP). The same error occurs if you lookup a local server successfully and try to save it. See log.
Created attachment 61081 [details] ntp cfg log
This is probably a NetworkManager-related bug. Enabling (insserv) the NTP service requires somehow 'network' in the dependencies but it should be '$network' instead. It is a bug of init scripts, NTP client uses common Service YCP Module for adjusting the service. See the log file: --- cut --- Service.ycp:195 Unable to enable service ntp: insserv: Service network has to be enabled for service ntp insserv: exiting now! --- cut ---
The same problem is also with enabling the service SuSEfirewall2_setup (SuSEfirewall2_init works well). I'm not opening a new bugreport because it might be exactly the same one bug deep in the same dependencies. cmdline: `insserv SuSEfirewall2_setup` returns the same as for the ntp service
Why I've gotten this bug? The scripts of the ntp and the SuSEfirewall services are buggy.
erm. i dont think so. $ grep Required /etc/init.d/ntp # Required-Start: $remote_fs $syslog $named # Required-Stop: $remote_fs $syslog $ grep named /etc/insserv.conf $named +named +dnsmasq +lwresd $network why is $network disabled ion your installation?
network (not $network) must be disabled because of the networkmanager might be wrong handling around network/networkmanager in $network?
well then somebody has to fix /etc/insserv.conf. werner?
NO,there is nothing to fix. *** This bug has been marked as a duplicate of 135595 ***