|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2 runlevel does not show a status for all services | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Andreas Klein <asklein> |
| Component: | YaST2 | Assignee: | Lukas Ocilka <locilka> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | vetter |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
yast2 logs
/tmp/runlevel-2-simple-000.png |
||
|
Description
Andreas Klein
2006-01-23 17:28:37 UTC
Created attachment 64578 [details]
yast2 logs
Created attachment 64579 [details]
/tmp/runlevel-2-simple-000.png
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... Ups... couldn't have been fixed in Beta3 I hope for Beta4. 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. |