Bug 232887
| Summary: | service xinetd status always returns success | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tobias Oed <tobiasoed> |
| Component: | xinetd | Assignee: | Jan Safranek <jsafrane> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | xinetd-2.3.14-9.fc6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-06-19 05:22:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
xinetd-2.3.14-9.fc6 has been pushed for fc6, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. |
Description of problem: I tried to use my standard if service X status; then service X reload; else service X start; fi with X=xinetd today and it failed because service xinetd status always returns success even when xinied is stopped. Version-Release number of selected component (if applicable): xinetd-2.3.14-8 How reproducible: 100% Steps to Reproduce: 1. service xinetd stop 2. service xined status 3. echo $? Actual results: 0 Expected results: Something else than 0 Additional info: Quick patch to adress the issue --- xinetd.orig 2006-10-01 22:33:47.000000000 +0200 +++ xinetd 2007-03-19 10:46:49.000000000 +0100 @@ -103,6 +103,7 @@ ;; status) status $prog + RETVAL=$? ;; restart) restart