Craig Falconer wrote:
> Thats weird - it appears to be stopping squidguard as soon as it is
> started....
Thinking back on things, I recall why it stopped soon after starting. I was
trying out step 10 of the "less impatient" install, which seems to be much the
same thing that you asked me to do below...
> what happens if you try running squidguard at the command
> line, then type in
>
> URL IPorFQDN ident method
> eg
> http://www.good.com/ 192.168.1.1/- - GET
> http://www.bad.com/ 192.168.1.1/- - GET
> where 192.168.1.1 is a local IP.
>
> If its allowed then squidguard will return nothing, else it will return the
> redirection url.
Well, I tried it. Well, I tried set 10 of the "less impatient" install again,
then I tried what you recommended. Both worked the way it is suppose to work.
How for the interesting part...
> Also... do a
> ps auxw | grep squidGuard
> to confirm that squidGuard is still running.
Yep, squidGuard IS running
The interesting part...
After running the tests once I killed squid all together and rm'ed the
squidGuard.log file after making sure that squidGuard was not running. When I
started squid backup, the squidGuard file was NOT created, but squidGuard WAS
running. It was not until I did the tests a second time that the squidGuard
file got created.
Something just popped into my head... My squid server is on my
gateway/firewall. I am using IP Filter to redirect ALL traffic coming in on
port 80of the internal NIC to port 3128 to send it through squid. I had to make
changes to squid to make this work correctly, some type of redirect, don't
recall exactly. Because squid is stealth, might there be something other then
the following config line that I need to do with squid?
redirect_program /usr/local/bin/squidGuard -c
/usr/local/squidGuard/squidGuard.conf
Sam
