James Nesbitt (IHQ Network) wrote:
I tried on mine to. The ./squid status command reported it was stopped. So I started it with the ./squid start command and it succeeded. When I did a ./squid stop command I got errors saying: IGNORING invalid ACL: acl Cips dst IGNORING invalid ACL: acl Cdomains dstdomain ERROR: no copy running I got the same error then when I did the ./squid status again. I didn't reboot the Qube at all. Any ideas of what is going on anyone? Regards, James Nesbitt -----Original Message-----
cant tell you what exactly is wrong, but i can tell you where those lines come from. They are the only custom cobalt thing in the squid.conf file:
# -*- COBALT-FILTER-RULES -*- acl Cips dst acl Cdomains dstdomain http_access deny !Safe_ports http_access deny CONNECT !SSL_ports # -*- END-COBALT-FILTER-RULES -*-i guess the Cips dst Cdomain and dstdomain var's have to be filled in somehow by the gui, and looking from the names they contain the source ips's and perhaps domains allowed to use the proxy. maybe someelse knows more how these "thingy's" get there content. Another option is to remove these lines and just add your ranges hard-coded. The gui will problay re-add them every time you start/stop squid from it.