Better yet, implement a wsus server, let it bypass caching and gpo your users to update from that. That way you can get away from having ms updates dictate caching options that result in problems with streaming.
________________________________
From: Brett Glass [mailto:squid-users_at_brettglass.com]
Sent: Sun 3/1/2009 8:02 AM
To: Amos Jeffries; Brett Glass
Cc: squid-users_at_squid-cache.org
Subject: Re: [squid-users] Streaming is killing Squid cache
At 09:47 PM 2/28/2009, Amos Jeffries wrote:
>Leaving min at -1, and max at something large (10-50MB?)
>
>Should abort the streams when they reach the max value, You'll have to set the max to something reasonably higher than the WU cab size.
>Service Packs may cause issues since they are >100MB each, but are infrequent enough to use a spider and cause caching if need be.
We've actually seen Microsoft updates as big as 800 MB.
Of course, this is a good argument for turning this setting into something that's controlled by an ACL, so one could say, "Cache everything from Microsoft, but not from these streaming providers."
--Brett
Received on Sun Mar 01 2009 - 21:51:31 MST
This archive was generated by hypermail 2.2.0 : Wed Mar 04 2009 - 12:00:02 MST