On Tue, 16 Nov 2004, Matthew Dillon wrote:
> Could you run an 'md5' checksum on the file when it is found to be
> bad verses when it is found to be good ? And then put the good and
> the bad file up somewhere where I can fetch them so I can do a
> byte-by-byte comparison.
I first had the problem with cups-1.1.22-source.tar.bz2 when updating
the cups port. I had corrupted files from several ftp sites and I
remember that the file sizes were different each time.
I just used 'fetch' to get the same file and it is corrupted once again,
but the filesize is correct this time. I'd be happy to send you the
file but I have no ftp server available to me. May I upload it? (8MB)
>
> Also, in -CURRENT, try turning off sack and see if the problem still
> occurs.
>
> sysctl net.inet.tcp.sack=0
I just tried this and, with a sample size of 1 try, it works fine. I
changed the value of sack while my newsreader was open to this group
and it got very confused -- I had to close the newsreader and reopen
it before I could post this. Dunno if it's related to sack or not.