delay_pools is the closest we have. With delay pools you can throttle
the user to almost nothing when reaching his limit.
We also have the capability to limit how large files each individual
user may download (reply_body_max_size in Squid-2.5).
It is my personal belief that more long-term accounting is best done
by log processing which feeds backs access control information to
Squid, but I am open to other suggestions as well.
Regards
Henrik
On Monday 13 May 2002 09:59, Bruce Janson wrote:
> Can you describe a little bit more what you are after, and in
> what ways the mechanisms that exists are not granular enough for
> you use? ...
>
> Henrik,
> Certainly. We would like to be able to assign byte-count
> limits to individual users and then terminate incoming transfers as
> soon as that user's limit is passed. From my reading of the
> documentation and configuration file I decided that such a feature
> was not currently supported (But perhaps I misread...).
>
> Regards,
> bruce.
Received on Mon May 13 2002 - 02:22:45 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:15:26 MST