Bug 245328 - Wrong init script
Wrong init script
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: sysklogd (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Peter Vrabec
Brian Brock
Depends On: 245327
  Show dependency treegraph
Reported: 2007-06-22 10:32 EDT by Michal Marciniszyn
Modified: 2014-02-10 18:03 EST (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2008-0162
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-09 12:15:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2008:0162 normal SHIPPED_LIVE sysklogd bug fix update 2008-07-23 17:59:40 EDT

  None (edit)
Description Michal Marciniszyn 2007-06-22 10:32:54 EDT
+++ This bug was initially created as a clone of Bug #245327 +++

Description of problem:
The syslog init script returns some incorrect error codes. Some part of it also
prevent the correct status command call. For example:
[ -f /sbin/syslogd ] || exit 0
[ -f /sbin/klogd ] || exit 0

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

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 7 errata-xmlrpc 2008-04-09 12:15:10 EDT
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 the 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.