Bug 814788

Summary: jetty initscript status doesn't retun 3 if not started
Product: [Fedora] Fedora Reporter: Nicolas Chauvet (kwizart) <kwizart>
Component: jettyAssignee: Mikolaj Izdebski <mizdebsk>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: java-sig-commits, kdaniel, mizdebsk, patrickm, sochotni
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-22 09:04:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
fix initscript status - jetty none

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