Bug 243287 - Wrong init script
Wrong init script
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: postgresql (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Tom Lane
Depends On:
Blocks: 237789 243288 243289
  Show dependency treegraph
Reported: 2007-06-08 08:14 EDT by Michal Marciniszyn
Modified: 2014-02-10 18:03 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-08 08:24:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Marciniszyn 2007-06-08 08:14:04 EDT
Description of problem:
The postgresql init script returns some incorrect error codes and some parts of
it also prevents correct status command call. For example:
[ "${NETWORKING}" = "no" ] && exit 1
[ -f "$PGENGINE/postmaster" ] || exit 1

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 1 RHEL Product and Program Management 2007-06-08 08:24:18 EDT
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release.  Since this
bugzilla is in a component that is not approved for the current
release, it has been closed with resolution deferred.  You may
reopen this bugzilla for consideration in the next release.
Comment 2 Tom Lane 2007-06-08 10:37:30 EDT
I'm going to close this as NOTABUG unless you get a *lot* more specific about
what you think is wrong.

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