Hello, We use directives "reply_body_max_size", "request_body_max_size" and "delay_access" to limit upload, download and passband in our infra. This configuration existes since a while, but we have noticed that with squid v4.16, our delay pool didn't react as we wanted anymore. We were excpeting improvment upgrading squid to v5.6. But it got worth : - restriction still didn't work - and squid had a segmentation fault each time some acl where used Thanks to Alex Rousskov (bug 5231), after some investigation, it appears that we used "slow" acl (proxy_auth an time acl) where only "fast" acl where authorized...). The bug is still open as squid has not flagged the problem in cache logs, My email, is to show you our configuration and the behaviour we espect, and the behaviour we finally have. 1 - squd v4.12 : we expect to limit downlod/upload and passband during working time for all login except those starting with cg_* " ###### Gestion de bande passante ##########
" => with this configuration, the delay pool seemed not to work anymore, so we upgraded squid to v5.6. Which caused the squid segmentation fault... 2 - squid v5.6 : to solve the segmentation fault, we had to take off my_ldap_auth/cgen (proxy_auth acl) and bureau (time acl). The limitation work again, but we are no more able to limit restriction during working time, or for spécific login... " ###### Gestion de bande passante ##########
" Can you tell me if what we want to do is still possible? Limiting upload/download/passband for all logged user except those starting by cg_*..?. Thank you for the time reading, and thank you for your answers. Regards, Eric Perrot Pour une administration
exemplaire, préservons l'environnement.
N'imprimons que si nécessaire.
|
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users