Bug 467189

Summary:	configuring run levels: provide accurate data
Product:	[openSUSE] openSUSE 11.1	Reporter:	macias - <bluedzins>
Component:	YaST2	Assignee:	Neil Brown <nfbrown>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2logs.tgz

Description macias - 2009-01-18 10:41:19 UTC

configuring run levels: provide accurate data

Example, nfs. It is listed as "yes*" status (no help to explain "*" meaning, but I guess it is mixed enabled status). Anyway -- I would like to disable it. I clicked on "disable" and I get error, that nfs is not configured (not true, it is not running really), but on the main list it is still shown as "yes".

And "of course" nothing is changed (you can switch to expert mode to see all runlevels for nfs are intact).

Please respect user wish, if user wants to disable service, it means she/he wants to disable it. Period. No matter if it is mixed mode (enabled for some run levels, disabled for others), or normal (the same for all levels) -- it has to be disabled.

Comment 1 Jiri Srain 2009-02-18 15:05:34 UTC

Can you attach the YaST logs? For me it works as expected.

Comment 2 macias - 2009-02-18 21:14:24 UTC

Created attachment 273730 [details]
y2logs.tgz

Jiri, do you have the same nfs status as mine, I mean do you have it _not_ running (I mean really, not as shown in yast).

Btw. I observed this behaviour also in 10.3.

Comment 3 Lukas Ocilka 2009-02-19 09:36:21 UTC

(In reply to comment #0)
> Example, nfs. It is listed as "yes*" status (no help to explain "*" meaning,

Quote from help:
An asterisk (*) after a service status means that the service is enabled but not running or is disabled but running now.

Comment 4 Lukas Ocilka 2009-02-19 09:43:57 UTC

BTW: Attached logs do not contain anything, just an empty file.

If there is an error while disabling the nfs, it's a nfs error.
Runlevel calls this before disabling the nfs service:

/etc/init.d/nfs stop

That service should not report an error that no services are configured
when stopping an already stopped service (it makes sense for starting,
not stopping).

Comment 5 Neil Brown 2009-02-19 10:02:43 UTC

This was fixed in early February
Fix should be available as an update I believe.

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