Bug 245308 - Wrong init script
Wrong init script
Status: CLOSED DUPLICATE of bug 247064
Product: Fedora
Classification: Fedora
Component: squid (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Martin Bacovsky
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-06-22 06:36 EDT by Michal Marciniszyn
Modified: 2014-02-10 18:03 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-19 16:27:36 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-22 06:36:22 EDT
+++ This bug was initially created as a clone of Bug #245304 +++

Description of problem:
The squid init script returns some incorrect error codes and some part of it
prevent correct status command call. For example:
[ ${NETWORKING} = "no" ] && exit 0
[ -f /etc/squid/squid.conf ] || exit 0
[ -z "$SQUID" ] && 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 1 Martin Bacovsky 2007-07-19 16:27:36 EDT
Bug #247064 is more general so closing this as a duplicate.

*** This bug has been marked as a duplicate of 247064 ***

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