Henrik, The HTTP 1.1 patch is applied and it's 2.6 stable5. The only odd thing is that I am running IWSS on the same server. Here are the squid.conf entries: cache_peer 127.0.0.1 parent 8080 0 no-query default acl our_networks src 10.0.0.0/8 acl numconn maxconn 100 http_access deny our_networks numconn http_access allow our_networks http_access deny all never_direct allow our_networks Also, I'm using file lists to block some IPs: acl DSBlock dst "/usr/local/squid/etc/dshieldblock.conf" http_access deny DSBlock acl BlockIP dst "/usr/local/squid/etc/blockip.conf" http_access deny BlockIP Otherwise, it's pretty vanilla. Thanks, Dave -----Original Message----- From: Henrik Nordstrom [mailto:henrik@xxxxxxxxxxxxxxxxxxx] Sent: Wednesday, March 14, 2007 4:41 PM To: Dave Rhodes Cc: Squid Users Subject: RE: Oom-killer and Squid mån 2007-03-12 klockan 17:33 -0400 skrev Dave Rhodes: > Henrik, > The Squid proc continues to grow. I ran the memory monitor between > 1.5 and 1.7GB. Hopefully that's enough. > > Let me know if you see anything interesting in there or if there is > something specific I can look for. Lots of things growing which should not be growing.. Most interesting is that the FwdState is growing a lot.. this should be a fairly small number as FwdState represents a request currently being processed. The rest is probably related to this.. Which Squid version is this? (you probaly told me already, but please remind me) Standard release, or any patches applied? Any odd configuration? Regards Henrik
