Bug 606805 - mon_statd: wrong exit code on stop already stopped service
mon_statd: wrong exit code on stop already stopped service
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: s390utils (Show other bugs)
6.0
All Linux
high Severity medium
: rc
: ---
Assigned To: Dan Horák
Yulia Kopkova
:
Depends On:
Blocks: 633349
  Show dependency treegraph
 
Reported: 2010-06-22 10:20 EDT by Yulia Kopkova
Modified: 2010-11-10 17:19 EST (History)
2 users (show)

See Also:
Fixed In Version: s390utils-1.8.2-26.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-10 17:19:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Yulia Kopkova 2010-06-22 10:20:17 EDT
Description of problem:
mon_statd init scripts returns wrong exit code on stop already stopped service

Version-Release number of selected component (if applicable):
s390utils-mon_statd-1.8.2-24.el6

How reproducible:
100%

Steps to Reproduce:
1. service mon_statd stop
2. service mon_statd stop
3. echo $?
  
Actual results:
3

Expected results:
0

Additional info:
According guidance https://fedoraproject.org/wiki/Packaging/SysVInitScript running stop on a service already stopped or not running should return an exit status of zero.
Comment 2 RHEL Product and Program Management 2010-06-22 10:33:15 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 6 releng-rhel@redhat.com 2010-11-10 17:19:55 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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