If I start squid as a runlevel 5 service, either from the command line with "/sbin/service squid start" (as >root) or from FC4's GUI Service Configuration, or from boot, squid chokes on squidGuard.
If however I start it as root with the command
"/usr/sbin/squid -NCd 1"
then magically squid works and squidGuard too!
So, the question is, how does the init script call squid ? with wich flags ? can you post the script ?

then I can do this:
[EMAIL PROTECTED] mark]# su - squid
-bash-3.00$ /usr/local/squidguard/bin/squidGuard -d
2006-01-26 20:47:29 [6046] squidGuard 1.2.0 started (1138308449.370)
2006-01-26 20:47:29 [6046] squidGuard ready for requests (1138308449.372)
Ok

and this:
[EMAIL PROTECTED] mark]# /usr/sbin/squid
[EMAIL PROTECTED] mark]# ps -ef | grep squid
root      6017  5105  0 20:46 pts/3    00:00:00 su - squid
squid     6018  6017  0 20:46 pts/3    00:00:00 -bash
root      6195     1  0 21:11 ?        00:00:00 /usr/sbin/squid
squid     6197  6195  0 21:11 ?        00:00:00 (squid)
squid 6198 6197 0 21:11 ? 00:00:00 (squidGuard) -c /etc/squidguard.conf squid 6199 6197 0 21:11 ? 00:00:00 (squidGuard) -c /etc/squidguard.conf squid 6200 6197 0 21:11 ? 00:00:00 (squidGuard) -c /etc/squidguard.conf squid 6201 6197 0 21:11 ? 00:00:00 (squidGuard) -c /etc/squidguard.conf squid 6202 6197 0 21:11 ? 00:00:00 (squidGuard) -c /etc/squidguard.conf
squid     6203  6197  0 21:11 ?        00:00:00 (unlinkd)
root      6209  5055  0 21:12 pts/2    00:00:00 grep squid
[EMAIL PROTECTED] mark]#
Here you called squid using a root shell, can you try calling squid from the "squid" user right just you have done with squidguard ?

seems to show that everything works when done this way.

Without shell access for user "squid" it still won't work.
I don't know if this is the problem, but my squid user has "/bin/true" as shell and all works, give it a try.

One suggestion from the squid list was to try the command "/usr/sbin/squid" in the /etc/rc.d/rc.local file at >boot - but as yet that still fails with the same error...
Can you try to strace the squid process to understand the real syscall error that generates that warning ?

Best Regards
Francesco Ranieri



Reply via email to