On 15 Dec 2004 at 10:04, Robert Trouchet wrote: > Thanks for the reply Shawn > > 1. I have added in a deny the slow account access to the main pool line > (above the allow all line) as below > > delay_access 2 deny SlowAccount > > 2. I have checked and I am running the delay pools version. > > 3. How should I look at the cachemgr.cgi file. It is not viewable with > Notepad.
You must place this in your web server's cgi-bin folder and setup access in squid - see the docs on this. It doesn't need to be on the same server, but can be (different port for web server of course). Apparently you can use squidclient to retrieve this info, but I have not tried this yet. > 4. My network is a class A (10.a.b.c). I have created a dedicated account > just for testing. The restrictions need to be on a user by user basis as > users can log onto any computer on the network. Ok, but it may be simpler to troubleshoot if you add an ACL for a specific IP and use that for now. Once it's working then move on to group auth ACLs. I would recommend you consider Class 2 or 3 ACLs, with limits set accordingly so that one user can't sap all the bandwidth for the group. Below is my current setup, which is working well, but still subject to finetuning. This is supporting approx 325 concurrent users on 7 vlans, and seems to work nicely. It is set to use at most 80% of our bandwidth for the entire pool, and so far we've seen at most about 65%. Before this we would see peaks of 98% daily. ========= delay_pools 1 delay_class 1 3 # Class 3 pool for all 10.x subnets, 1MB/s agg, 500KB/s net, 100KB/s individual. delay_parameters 1 1000000/1000000 500000/500000 100000/100000 #delay_access 1 allow vlan2 delay_access 1 allow vlan80 delay_access 1 allow vlan90 delay_access 1 allow vlan100 delay_access 1 allow vlan110 delay_access 1 allow vlan120 delay_access 1 allow vlan210 delay_access 1 allow vlan200 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Shawn Wright, I.T. Manager Shawnigan Lake School http://www.sls.bc.ca [EMAIL PROTECTED]
