Bug 237831 - Wrong init script
Summary: Wrong init script
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: isdn4k-utils
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Ngo Than
QA Contact: BaseOS QE
: 242481 (view as bug list)
Depends On:
Blocks: 237789 237832 237833 242493 242495
TreeView+ depends on / blocked
Reported: 2007-04-25 15:37 UTC by Michal Marciniszyn
Modified: 2014-02-10 23:02 UTC (History)
4 users (show)

Clone Of:
Last Closed: 2009-06-17 14:47:54 UTC

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:1112 normal SHIPPED_LIVE isdn4k-utils bug fix update 2009-06-17 14:47:51 UTC

Description Michal Marciniszyn 2007-04-25 15:37:49 UTC
Description of problem:
Through the script, following constructions are used:
[ -f /sbin/capiinit ] || exit 0
[ -f /etc/capi.conf ] || exit 0
Effectively, they return 0 even when the service is not started or running
(start/status command). Also wrong return codes are present through the script.

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

How reproducible:

Steps to Reproduce:
1. remove capi.conf file
2. service capi start/status
3. echo $?
Actual results:

Expected results:
non-zero error code/correct service status

Additional info:
When fixing this bug, please obbey our init script guidelines and be sure that
status command is run correctly.
Our guidelines are on following two pages:

For an example of the script that returns the error codes correctly and always
runs status see:

This bug is tracked by 237789.

Comment 1 Phil Knirsch 2008-04-29 15:32:25 UTC
Proposing for RHEL-5.3, waiting with final ACK on developer review.

Read ya, Phil 

Comment 2 Ngo Than 2008-05-28 15:04:35 UTC
+devel ack

Comment 6 Ngo Than 2008-07-28 09:55:47 UTC
*** Bug 242481 has been marked as a duplicate of this bug. ***

Comment 15 errata-xmlrpc 2009-06-17 14:47:54 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. 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.