Bug 1371723 - nsca init script is not lsb compliant
Summary: nsca init script is not lsb compliant
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: nsca
Version: el6
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Xavier Bachelot
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-31 00:01 UTC by ellison.marks
Modified: 2016-09-29 19:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-29 19:31:37 UTC
Type: Bug


Attachments (Terms of Use)

Description ellison.marks 2016-08-31 00:01:40 UTC
Description of problem:

When running any actions using the nsca init script, the return value is always 0. This is due to the last line in the file being `exit 0`. This is affecting us when trying to manage nsca with puppet. No matter what state nsca is actually in, puppet believes it is running, as `service nsca status` returns 0.

Version-Release number of selected component (if applicable):

2.7.2-8

How reproducible:

Always

Steps to Reproduce:
1. ensure nsca is stopped
2. run `service nsca status`
3. run `echo $?`

Actual results:

0

Expected results:

3

Additional info:

Comment 1 ellison.marks 2016-09-29 19:31:37 UTC
Looks like this is fixed in the version in epel-testing, 2.9.1-4 at the time of this writing. Closing.


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