Running squid-2.7.STABLE1-20080528 on Debian linux 2.6.19.7 kernel
using wccp2 and iptables for transparency.
Put into production approx. 2 weeks ago, approx. 10k customers are
browsing transparently without any complaints of latency, and we're
seeing a measurable incoming bandwidth savings on
On tor, 2008-07-10 at 09:40 -0500, Rhino wrote:
> Running squid-2.7.STABLE1-20080528 on Debian linux 2.6.19.7 kernel
> using wccp2 and iptables for transparency.
> Put into production approx. 2 weeks ago, approx. 10k customers are
> browsing transparently without any complaints of latency, and w
On tor, 2008-07-10 at 11:06 -0500, Rhino wrote:
> 2008/07/10 03:07:31| storeLocateVary: Not our vary marker object,
> AD15713B6C28E4CE9BBEA7488
> 76C70B7 =
> 'http://x.myspacecdn.com/modules/common/static/js/apps/json001.js',
> 'accept-encod
> ing="gzip,%20deflate"'/'gzip, deflate'
> 2008/07/10 03
On tor, 2008-07-10 at 13:58 -0500, Rhino wrote:
> >
> the cache.log is huge - ton of entries in there starting from when it
> began after the previous rotation (daily).
> Is there anything in particular to look for?
The most interesting is FATAL, assertion failed, segmentation fault, and
the a
