Red Hat Bugzilla – Bug 104697
Squid init script sends useful console startup messages to /dev/null
Last modified: 2014-08-31 19:25:21 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR
Description of problem:
The initscript for squid currently reads something like this:
$SQUID $SQUID_OPTS 2> /dev/null
This is less than perfect - if squid starts up but dies soon after, nothing
will be logged and the end user will be none the wiser as to what went wrong.
A good example is if the permissions on the logging directory are wrong and
squid is unable to write any log out, or if the file system is full.
This output should be logged to a file, say for
Patch attached which changes the init script to resolve this issue.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start squid
2. Silently dies and restarts...
3. Eventually it gives up ;-)
Actual Results: Nothing is logged when ideally a console message should be.
Expected Results: Console output or alternatively, to a log file..
Created attachment 94594 [details]
Patch to replace references to /dev/null to squid.out
A similar patch is included in the latest rawhide squid RPM.