I have configured the tproxy as follows, but it appears packets are
not hitting squid. Please note, the wccp configuration on the router
is already working with squid http_port transparent configuration and,
obviously, different iptables configuration. Any help is appreciated.
Thanks in
Please, ignore this post. I found I need to add more configuration as
in
http://wiki.squid-cache.org/ConfigExamples/UbuntuTproxy4Wccp2#Linux_and_Squid_Configuration
On Wed, Feb 6, 2013 at 9:27 AM, Roman Gelfand rgelfa...@gmail.com wrote:
I have configured the tproxy as follows, but it appears
On 02/05/2013 05:09 AM, Silamael wrote:
I just noticed that the squid -z command seems to fork and the child is
creating the cache directories. The parent immediatly returns with exit
code 0. Is this behaviour intended?
Yes, it is. In old Squids, -z implied no-daemon mode. Then folks wanted
I want to store all my cache dir on a ram disk. I have this in my config:
cache_dir ufs /dev/shm/squid 1024 16 256
Is there any reason NOT to do this? All the stuff in my cache is time
sensitive (expires after 15 minutes) so I'm not worried about losing
data, just worried about best practices.
On 02/05/2013 06:08 PM, Amos Jeffries wrote:
On 6/02/2013 3:58 a.m., Simone Levy wrote:
should this issue be reported as a bug or otherwise dealt with?
It is already reported as http://bugs.squid-cache.org/show_bug.cgi?id=3763
Amos, bug 3763 is not about setuid(0) warnings, although both bugs
On 02/06/2013 02:48 PM, Scott Baker wrote:
I want to store all my cache dir on a ram disk. I have this in my config:
cache_dir ufs /dev/shm/squid 1024 16 256
Is there any reason NOT to do this?
Yes, memory cache is generally faster than any cache_dir cache.
All the stuff in my cache is
