[java-sig-commits] [Bug 814788] New: jetty initscript status doesn't retun 3 if not started

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: jetty initscript status doesn't retun 3 if not started

https://bugzilla.redhat.com/show_bug.cgi?id=814788

           Summary: jetty initscript status doesn't retun 3 if not started
           Product: Fedora
           Version: 16
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: unspecified
          Priority: unspecified
         Component: jetty
        AssignedTo: sochotni at redhat.com
        ReportedBy: kwizart at gmail.com
         QAContact: extras-qa at fedoraproject.org
                CC: overholt at redhat.com, sochotni at redhat.com,
                    java-sig-commits at lists.fedoraproject.org,
                    kdaniel at redhat.com, mizdebsk at redhat.com
    Classification: Fedora
      Story Points: ---
              Type: Bug
        Regression: ---
        Mount Type: ---
     Documentation: ---


Created attachment 579054
  --> https://bugzilla.redhat.com/attachment.cgi?id=579054
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.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.