* Ralf Hildebrandt <ralf.hildebra...@charite.de>: > * Matus UHLAR - fantomas <uh...@fantomas.sk>: > > > so the problem was not "3.1 uses too many connections" but "2.7 drops > > connections when it should not". > > A bit funny ;) > > I made some more experiments and found out that the problem is between > the Squid in front of dansguardian. > > client -> squid_in_front -> dansguardian -> squid_behind -> Internet > > I was able to replace the squid 2.7.x "behind" dansguardian with a > 3.1.x version without negative impacts (except for frequent crashes).
I increased the maximum number of dansguardian processes and found that squid3 would use 297 dansguardian processes, about 2.5 times the number 2.7.x would keep busy. Dunno if that's a good or bad sign. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
