Date: Wed, 12 Apr 2006 01:04:38 -0700 From: Colin Percival <cperciva@freebsd.org> To: Andrew Pantyukhin <infofarmer@gmail.com> Cc: Wojciech Puchar <wojtek@tensor.3miasto.net>, freebsd-questions@freebsd.org Subject: Re: portsnap DOESN'T WORK Message-ID: <443CB496.4080101@freebsd.org> In-Reply-To: <cb5206420604120002w7f5229buc9a8c94c9a0c14d6@mail.gmail.com> References: <20060411202952.F59517@chylonia.3miasto.net> <443C1A4D.3050609@freebsd.org> <cb5206420604120002w7f5229buc9a8c94c9a0c14d6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Pantyukhin wrote: > BTW, I didn't want to bother you, but I've had a similar problem > on a very slow link. Portsnap tends to time out (in spite of the > download is in progress, bytes are coming - just very slowly) > and says that <something> is corrupt. I think time outs should > be tuned. What does "portsnap --debug fetch" report? Are you using a proxy? Which part is timing out, downloading the initial snapshot tarball or downloading lots of patches? Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?443CB496.4080101>