On Tue, 16 Nov 2004, Matthew Dillon wrote:
> Leave SACK turned off (set it to 0 in /etc/sysctl.conf) and run a bunch
> more tests and report back.
>
> If you consistently get zero corruption with SACK turned off then we
> know it is SACK....
Okay, I downloaded the same cups sourcefile three times from different
mirrors and got a perfect result every time.
I set SACK=1 again and downloaded a corrupt file from the same ftp server
which gave me a perfect file just minutes earlier.
So far: five out of six files corrupt with SACK=1 and zero of four with
SACK=0.
After years of reading scientific journals I can say without any hesitation
that SACK is responsible for the file corruption (p=0.0001).
(I can say with equal certainty that most scientific articles likewise
make up a p-value out of thin air, but that has little to do with the
present file-corruption problem ;o)