On 13/05/2013 8:22 p.m., Pieter De Wit wrote:
On 13/05/2013 11:34, Amos Jeffries wrote:
On 13/05/2013 2:26 a.m., Fix Nichols wrote:
Heh if you are running Debian and lazy, you could 'apt-get install
squid -y ; apt-get install squid3 -y' Youd have squid 2.7 and squid3
both installed.
And wont work for much longer. We are in the process of replacing
"squid" with a transitional package to squid3.
But I know, thats just being lazy, you can install two squids just
change the name and location of your binaries on one of them, and
its cache directories, as well. Assuming squid is resident on a pc
and not a router that is. It should be pretty straight forward.
Or do it properly and install Squid once. Just start it twice with two
squid.conf files containing different settings. Ta-Dah!
If, I'm understanding the original poster right though it sounds like
traffic is leaving the Squid and being diverted back into them in a
forwarding loop. Or that the traffic flows are getting mixed up somehow
in other ways.
Amos
While you are busy with the deb packages, how about not putting in a
squid.conf and rather calling it squid.conf.default, or do "include"
configs like Apache ? Pretty please ? :)
I'm not sure I understand the first suggestion there about squid.cofn
and squid.conf.default?
I've tried to convince people to follow the Apache config include style.
But it gets really nasty to manage related directive ordering. Or did
you mean something else entirely?
Amos
