Okay, I solved it.

Seems that new squidguard sits somewhere in path now, so that /usr/bin/update/squidguard script runs the new one. I have edited the script, put the full path to distributional squidguard there and it works now.

However, it shouldn't happen I think.

Peter


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to