On 30/10/18 4:15 PM, Angus J. wrote: > Hi Amos > > Can I just copy the all squid configure file at /etc/squid/ from 2.7 to 3.5 > ? > Sometimes, but usually not *just* that. The problem is that Squid-2.7 very old and also 2.6 & 2.7 was a fork of the even older Squid-2.5 code. There have been quite a lot of changes to squid.conf in the 12 years between 2.5 and 3.5, and v2.7 does some things a bit differently to both. The squid -k parse mechanism was added to help reduce the problems encountered with upgrades. So you can have the squid-3 tell you what it understands about the older config files. As you should have noticed when I got you to run -k parse earlier there were things coming up as FATAL and ERROR in your particular config file. That means Squid will not even start until the config is changed to the Squid-3.x settings. FWIW: Marcus and I are trying to get you to the point where your Squid will run and do what you have told us it is supposed to be doing. The problems you are having in the latest few days are because you went and changed other things (the cache_peer lines) beside what we pointed out - which broken the proxy again in a different way. It's okay that you don't know what you are doing. This list is in part for helping people learn to operate Squid. Just try not to go too fast of more breakage will occur. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
