On 15/01/2010 00:18, Luigi Gangitano wrote: > Steven, did you by chance have the opportunity to upgrade to lenny > and check if this bug is fixed? I cannot reproduce it with current > (lenny and sid) machines and have no production server with etch > currently running squid 3.0.
I still haven't upgraded the affected machine from etch to lenny, but at some point after DSA 1843-2 I upgraded squid3 using the latest package from lenny (3.0.STABLE8-3+lenny2), without upgrading anything else. I can happily say that I haven't noticed this bug in a very long time, whereas it would have happened almost daily with the version from etch (3.0.PRE5-5+etch1). I also have a couple of new machines which use squid3 on lenny and they haven't been affected by this bug. So I'm quite sure that this bug is fixed in the current squid3 for lenny. Many thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
