Date: Wed, 26 Mar 2008 19:55:55 -0000 From: "Barry Byrne" <barry.byrne@wbtsystems.com> To: "'RW'" <fbsd06@mlists.homeunix.com>, <freebsd-questions@freebsd.org> Subject: RE: portsnap fetch errors Message-ID: <005301c88f7b$67512660$0201a8c0@wbt.wbtsystems.com> In-Reply-To: <20080326183502.2180be97@gumby.homeunix.com.> References: <BDCFD9B395C4234F98409E10C78B8418B89214@ASHEVS011.mcilink.com><00fe01c88f59$729cf750$c5010c0a@wbt.wbtsystems.com> <20080326183502.2180be97@gumby.homeunix.com.>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of RW > Sent: 26 March 2008 18:35 > To: freebsd-questions@freebsd.org > Subject: Re: portsnap fetch errors > > On Wed, 26 Mar 2008 15:52:51 -0000 > "Barry Byrne" <barry.byrne@wbtsystems.com> wrote: > > > > By any chance is your portsnap using a proxy server, possibly squid? > > > > If so this may get around the problem prior to running your > portsnap. > > > > # sysctl net.inet.ip.portrange.randomized=0 > > Why would that make a difference? I think some versions of squid may be a bit broken with respect to correctly handling HTTP/1.1 and in the case of portsnap downloading many files, squid starts closing some of the open connections, which portsnap then attempts to reuse. There was a thread on one of the FreeBSD lists in late 2006. Google a bit and you'll probably find it. Don't know for certain this is your problem, but it did fix it when I came across the problem. - barry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005301c88f7b$67512660$0201a8c0>