Bug 814788 - jetty initscript status doesn't retun 3 if not started
jetty initscript status doesn't retun 3 if not started
Product: Fedora
Classification: Fedora
Component: jetty (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Mikolaj Izdebski
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-04-20 12:52 EDT by Nicolas Chauvet (kwizart)
Modified: 2012-07-22 05:09 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-07-22 05:04:32 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
fix initscript status - jetty (255 bytes, patch)
2012-04-20 12:52 EDT, Nicolas Chauvet (kwizart)
no flags Details | Diff

  None (edit)
Description Nicolas Chauvet (kwizart) 2012-04-20 12:52:20 EDT
Created attachment 579054 [details]
fix initscript status - jetty

Description of problem:
If jetty is not started, the status code for the command must return 3.

Version-Release number of selected component (if applicable):
current jetty in f16

How reproducible:

Steps to Reproduce:
1.service jetty stop
2.service jetty status
3.echo $?
Actual results:
It return 0

Expected results:
It must return 3

Additional info:
As systemctl is used in current f16, I expect that the problem doesn't exibit that way. There is in mind that this package should potentially a base of an EL (EPEL?) branch. Nevertheless the correctness of the return code might still be valid anyway.
Comment 1 Mikolaj Izdebski 2012-07-22 05:09:06 EDT
Fixed in Fedora 17

Note You need to log in before you can comment on or make changes to this bug.