>
> Now, I'm seeing "254:64000" for my address, and my client navigation
> is stopped
>
> it's like I reached a limit who stop the connection, I mean it's not
> more slow I'm just waiting (long time) with no return, so I should
> press the "stop" button for navigate again
> After that there is n
>
> Some such as #21, have somehow used more traffic than was in the
> buffer to begin with and have a negative value available. They will
> not
> be able to read anything until the 64K refill has raised their
> values
> back to positive again.
>(I _think_ this is related to uploads wh
- Mail original -
> De: "Amos Jeffries"
> À: squid-users@squid-cache.org
> Envoyé: Mercredi 14 Décembre 2011 01:02:21
> Objet: Re: [squid-users] Delay_pool problem
>
> On Tue, 13 Dec 2011 14:12:48 +0100 (CET), FredB wrote:
> > Hello,
> >
>
Thanks a lot I will try that
- Mail original -
> De: "Amos Jeffries"
> À: squid-users@squid-cache.org
> Envoyé: Mercredi 14 Décembre 2011 01:02:21
> Objet: Re: [squid-users] Delay_pool problem
>
> On Tue, 13 Dec 2011 14:12:48 +0100 (CET), FredB wrote:
> &
On Tue, 13 Dec 2011 14:12:48 +0100 (CET), FredB wrote:
Hello,
I wish to limit the bandwidth like this
1) Limit 64000 by user for objects more big than 30 ko
2) Limit global bandwidth to 1625000 - 13MB -
I tried this configuration
acl myusers src 10.0.0.0/8
acl proto-pool port 80 81 21
delay_
Hello,
I wish to limit the bandwidth like this
1) Limit 64000 by user for objects more big than 30 ko
2) Limit global bandwidth to 1625000 - 13MB -
I tried this configuration
acl myusers src 10.0.0.0/8
acl proto-pool port 80 81 21
delay_pools 2
delay_class 1 2
delay_parameters 1 -1/-1 64000/3
