Bug 814788 - jetty initscript status doesn't retun 3 if not started
Summary: jetty initscript status doesn't retun 3 if not started
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: jetty
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mikolaj Izdebski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-20 16:52 UTC by Nicolas Chauvet (kwizart)
Modified: 2012-07-22 09:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-22 09:04:32 UTC
Type: Bug
Embargoed:


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

Description Nicolas Chauvet (kwizart) 2012-04-20 16:52:20 UTC
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:
alwsays

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 09:09:06 UTC
Fixed in Fedora 17


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