Red Hat Bugzilla – Bug 245307
Wrong init script
Last modified: 2016-07-26 19:46:30 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): all How reproducible: always Steps to Reproduce: 1. 2. 3. 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: http://intranet.corp.redhat.com/ic/intranet/InitscriptsSpec.html http://intranet.corp.redhat.com/ic/intranet/InitscriptGuidelines.html For an example of the script that returns the error codes correctly and always runs status see: http://devserv.devel.redhat.com/~mmarcini/amd This bug is tracked by 237789.
Re-proposed to 4.7
Created attachment 294023 [details] Patch for squid.init Patched init script will return correct codes and additionally, it will also check if /usr/sbin/squid is executable.
Created attachment 294030 [details] Patch for squid.init New one.
Fix checked in CVS.
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. http://rhn.redhat.com/errata/RHBA-2008-0230.html