Bug 139589

Summary:	yast: NTP setup. Restarting fails
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Karl Eichwalder <ke>
Component:	YaST2	Assignee:	Dr. Werner Fink <werner>
Status:	RESOLVED DUPLICATE	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None	CC:	hvogel, lnussel, locilka
Version:	Alpha 4
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Documentation	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	ntp cfg log

Description Karl Eichwalder 2005-12-16 14:20:53 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.

Comment 1 Karl Eichwalder 2005-12-16 14:21:30 UTC

Created attachment 61081 [details]
ntp cfg log

Comment 2 Lukas Ocilka 2006-01-02 09:10:45 UTC

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 ---

Comment 3 Lukas Ocilka 2006-01-02 10:52:20 UTC

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

Comment 4 Dr. Werner Fink 2006-01-09 10:27:22 UTC

Why I've gotten this bug?  The scripts of the ntp and the SuSEfirewall
services are buggy.

Comment 5 Hendrik Vogelsang 2006-01-09 12:40:13 UTC

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?

Comment 6 Lukas Ocilka 2006-01-09 12:56:58 UTC

network (not $network) must be disabled because of the networkmanager
might be wrong handling around network/networkmanager in $network?

Comment 7 Hendrik Vogelsang 2006-01-09 13:05:48 UTC

well then somebody has to fix /etc/insserv.conf. werner?

Comment 8 Dr. Werner Fink 2006-01-11 13:20:29 UTC

NO,there is nothing to fix.

*** This bug has been marked as a duplicate of 135595 ***