Re: 3.1 steps forward
On Tue, Mar 25, 2008, Amos Jeffries wrote: have you fixed the AddrInfo leak? :) Fixed. Are you still creating/destroying individual addrinfo structs when doing socket operations? Adrian -- - Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial Squid Support - - $25/pm entry-level VPSes w/ capped bandwidth charges available in WA -
Re: 3.1 steps forward
Adrian Chadd wrote: On Tue, Mar 25, 2008, Amos Jeffries wrote: have you fixed the AddrInfo leak? :) Fixed. Are you still creating/destroying individual addrinfo structs when doing socket operations? I have only changed the place where it was leaking, to fix the leak. The other spots still need to be audited and improved. Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: 3.1 steps forward
Adrian Chadd wrote: On Fri, Feb 15, 2008, Amos Jeffries wrote: Sorry if I was obtuse. I meant that you are the expert on this one. Are you able to re-locate that mysterious branch and estimate when you will have time to sync and push it to HEAD? squid3_logdaemon have you fixed the AddrInfo leak? :) Fixed. Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: 3.1 steps forward
Adrian Chadd wrote: On Fri, Feb 15, 2008, Amos Jeffries wrote: Sorry if I was obtuse. I meant that you are the expert on this one. Are you able to re-locate that mysterious branch and estimate when you will have time to sync and push it to HEAD? squid3_logdaemon have you fixed the AddrInfo leak? :) A better bypass is now in testing. Hopefully I will have some time tomorrow to run it through the hoops properly. Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: 3.1 steps forward
On Thu, Feb 14, 2008, Amos Jeffries wrote: I'm just checking 3.1 progress maps now that the current big patches are in. Adrian: http://wiki.squid-cache.org/Features/LogDaemon Can we add a timeline on this now please? If it requires a push THN will provide a little funding to get it for our use in 3.1. Its done. Its in a branch in sourceforge somewhere. Adrian -- - Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial Squid Support - - $25/pm entry-level VPSes w/ capped bandwidth charges available in WA -
Re: 3.1 steps forward
Adrian Chadd wrote: On Thu, Feb 14, 2008, Amos Jeffries wrote: I'm just checking 3.1 progress maps now that the current big patches are in. Adrian: http://wiki.squid-cache.org/Features/LogDaemon Can we add a timeline on this now please? If it requires a push THN will provide a little funding to get it for our use in 3.1. Its done. Its in a branch in sourceforge somewhere. Sorry if I was obtuse. I meant that you are the expert on this one. Are you able to re-locate that mysterious branch and estimate when you will have time to sync and push it to HEAD? Thanks Amos -- Please use Squid 2.6STABLE17+ or 3.0STABLE1+ There are serious security advisories out on all earlier releases.
Re: 3.1 steps forward
On Fri, Feb 15, 2008, Amos Jeffries wrote: Sorry if I was obtuse. I meant that you are the expert on this one. Are you able to re-locate that mysterious branch and estimate when you will have time to sync and push it to HEAD? squid3_logdaemon have you fixed the AddrInfo leak? :) Adrian
3.1 steps forward
I'm just checking 3.1 progress maps now that the current big patches are in. Adrian: http://wiki.squid-cache.org/Features/LogDaemon Can we add a timeline on this now please? If it requires a push THN will provide a little funding to get it for our use in 3.1. Amos
