search for: id8dbqfalhoopzzozrzi

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 13 Feb 2004, Geoff Shang wrote: > Mihai RUSU wrote: > > > Another nice feature to add would be a "bandwidth" limit (so just a new > > <limit> type entry). > > Problem with this is, what do you do once the limit has been reached? Who > do you kick? Or do you just not allow anymore listeners? I

> > > Another nice feature to add would be a "bandwidth" limit (so just a new > > > <limit> type entry). If you are running icecast2 on linux you can handle bandwidth limitations using QoS more specificly iproute2. That way icecast2 doesnt have to take up extra resources to handle bandwidth limitations. resources here cbq bash script

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi I will need to find a solution for server side limit of clients bandwidth depending on their IPs (because we have very fast local connections with local ISPs and slow "external" connections with the rest of the Internet). Initially I think I'll just start 2 icecast servers (one for "local" clients, one for