Path: utzoo!lsuc!tmsoft!dptcdc!ncrcan!ziebmef!cks
From: cks@ziebmef.uucp (Chris Siebenmann)
Newsgroups: tor.news
Subject: Re: Munged article in tor.news.stats
Message-ID: <1989Apr22.142556.1619@ziebmef.uucp>
Date: 22 Apr 89 18:25:55 GMT
References: <1989Apr18.063300.2852@tmszfI.uucp> <1660@dciem.dciem.dnd.ca> <427@becker.UUCP>
Reply-To: cks@ziebmef.UUCP (Chris Siebenmann)
Organization: Ziebmef Public Access Unix, Toronto, Ontario
Lines: 19

In article <427@becker.UUCP> bdb@becker.UUCP (Bruce Becker) writes:
...
| 	It could be that one of the systems on the path
| 	transiently ran out of disk blocks during a compress
| 	operation, which would make the uncompressed
| 	file look pretty strange.

 Wouldn't that just chop off the file (or truncate bits out of the
middle) instead of garbling letters? From previous experience, it
looks like the uucp transfer corrupted the batch that article was in,
starting at it (my experience has been that one article is zapped, and
then there aren't recognizable '#! rnews' headers for the rest, so
they get dropped).

-- 
	"But he said leave me alone I'm a family man
	 and my bark is much worse than my bite"
Chris Siebenmann		uunet!{utgpu!moore,attcan!telly}!ziebmef!cks
cks@ziebmef.UUCP	     or	.....!utgpu!{,ontmoh!,ncrcan!brambo!}cks