Bug 144891 - yast2 runlevel does not show a status for all services
Summary: yast2 runlevel does not show a status for all services
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 1
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Lukas Ocilka
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-23 17:28 UTC by Andreas Klein
Modified: 2006-02-13 11:24 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
yast2 logs (532.05 KB, application/x-compressed-tar)
2006-01-23 17:29 UTC, Andreas Klein 		Details
/tmp/runlevel-2-simple-000.png (135.48 KB, image/png)
2006-01-23 17:29 UTC, Andreas Klein 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Klein 2006-01-23 17:28:37 UTC 
yast2 runlevel does not show a status for all services
Comment 1 Andreas Klein 2006-01-23 17:29:04 UTC 
Created attachment 64578 [details]
yast2 logs
Comment 2 Andreas Klein 2006-01-23 17:29:54 UTC 
Created attachment 64579 [details]
/tmp/runlevel-2-simple-000.png
Comment 3 Lukas Ocilka 2006-01-24 08:11:50 UTC 
Hmm, there is a new non-blocking system for checking the service status
It seems that the background_agent is not handled correctly (dumb-proof)
It can be fixed in Beta3...
Comment 4 Lukas Ocilka 2006-02-01 22:38:45 UTC 
Ups... couldn't have been fixed in Beta3 I hope for Beta4.
Comment 5 Lukas Ocilka 2006-02-13 11:24:37 UTC 
This was because Status-checker uses the background agent with time-out enabled and even the agent reported it hadn't run, it hadn't been finished.

Added a .kill functionality at the end of every run of this function.

Fixed in yast2.rpm 2.13.28 (or 2.13.29) depends on the next submitter.