> thx, I'm getting these messages: > > # squid3 -k check > 2009/02/17 01:25:39| WARNING: '0.0.0.0/0.0.0.0' is a subnetwork of > '0.0.0.0/0.0.0.0' > 2009/02/17 01:25:39| WARNING: because of this '0.0.0.0/0.0.0.0' is > ignored to keep splay tree searching predictable > 2009/02/17 01:25:39| WARNING: You should probably remove > '0.0.0.0/0.0.0.0' from the ACL named 'all' > > > > possibly I must put all my internal networks instead of acl all src > 0.0.0.0/0.0.0.0 > No. The 'all' ACL is now pre-defined. The definition you have in squid.conf can be removed. Amos > > > > On Mon, Feb 16, 2009 at 11:01 PM, Amos Jeffries <squid3@xxxxxxxxxxxxx> > wrote: >>> hi >>> >>> what happens with /etc/squid3/squid.conf after squid upgrade normally? >>> does squid 3.0 PRE5 use the same config file like 3.0 STABLE 8-3? >>> >>> kind regards >>> Piotr >>> >> >> Define "normally". >> >> The same config _should_ work for all 3.0.*. Only a few exceptions which >> have been marked with new WARNING deprecation lines (squid uses them >> fine, >> but later releases may have issues). >> >> Run squid -k check to have it verify the new squid.conf before >> restarting. >> >> If squid has already restarted on you, check the cache.log for any >> warnings or fatal problems. >> >> Amos >> >> >> >
