Well, the big thing here is that you're using delay pools in a manner which it wasn't intended. Its not a quota system, its a method of restricting instantaneous transfer speeds. That said, it would be useful to be able to modify bucket values automatically via some sort of cachemgr-like interface (both increasing and decreasing the buckets.) Since I've got my fingers dirty in the Squid-2 delay pools, hit me up privately for more details if you're interested. Adrian On Wed, Apr 09, 2008, Jason Haar wrote: > Hi there > > We are starting to use delay_pool to limit multimedia downloads (stop > them swallowing our links). We've set just two pools (tracked per IP), a > default (no limits) and a "multimedia" pool set at 300M and then > throttle down to 1Kbyte/sec >:-) > > Seems to work well - but there's no indication of how long an IP would > end up "blacklisted" if it occurred. At the moment we're restarting > Squid every Sunday and just stating users get 300M per week. > > Is there any other way to "reset" delay_pools beyond a restart? How > about a timeout variable? Setting it to 150M per day is sort of what > we're really after - but we don't want daily "outages" just to reset the > stats... > > Thanks, this is with squid-2.6STABLE17 under CentOS > > -- > Cheers > > Jason Haar > Information Security Manager, Trimble Navigation Ltd. > Phone: +64 3 9635 377 Fax: +64 3 9635 417 > PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 -- - Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial Squid Support - - $25/pm entry-level VPSes w/ capped bandwidth charges available in WA -
