Search squid archive

Re: Design a delay_pools policy...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



fre 2007-03-23 klockan 09:41 +0200 skrev Raymond A. Meijer:

> I read it 73847 times, but I found it very hard to understand :-|

So what was the hardest part to understand? (just trying to figure out
how to better document this)

http://wiki.squid-cache.org/SquidFaq/MiscFeatures#head-fd9b4b7ba1854a3c21796173af9d0b9aee33e376
http://www.deckle.co.za/squid-users-guide/Access_Control_and_Access_Control_Operators#Delay_Classes

> delay_pools 1
> delay_class 1 2
> delay_access 1 allow !fastusers !local
> delay_access 1 deny all
> delay_parameters 1 -1/-1 100000/100000

Looks fine if you want a hard 100KByte/s (ca 1Mbit/s) limit per user.
Usually how most people use delay pools is by using a somewhat bigger
bucket (maybe 10 times the rate) and a slightly smaller rate to allow
some burstiness which is typical in normal browsing while still limiting
downloads.

delay_parameters 1 -1/-1 400000/90000

this will allow users to access Internet in bursts of up to 400Kbyte
unlimited as long as they stay within their allowed 90Kbyte/s limit in
average.

You could also reorder the acl lists slightly to make them easier to
maintain if you need to add more exclusion criterias later on

delay_access 1 deny fastusers
delay_access 1 deny local
delay_access 1 allow all

but both ways works fine.

Regards
Henrik

Attachment: signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux