Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site Glacier.ARPA
Path: utzoo!watmath!clyde!cbosgd!ulysses!allegra!oliveb!Glacier!reid
From: reid@Glacier.ARPA (Brian Reid)
Newsgroups: net.news.b
Subject: more verification of Chuqui's article-eater bug, & a question
Message-ID: <11414@Glacier.ARPA>
Date: Fri, 6-Sep-85 00:17:36 EDT
Article-I.D.: Glacier.11414
Posted: Fri Sep  6 00:17:36 1985
Date-Received: Sat, 7-Sep-85 05:48:33 EDT
Reply-To: reid@Glacier.UUCP (Brian Reid)
Organization: Stanford University, Computer Systems Lab
Lines: 24
Summary: I saw it happen with my own blurry eyes

We had some problems this weekend when our daily, weekly, and monthly
netnews maintenance runs were all trying to run at the same time; one of the
side effects was that we then ran for 4 days with rnews turned off and the
incoming news accumulating in /usr/spool/news/rnews.$$.

This evening I manually ran all of the accumulated news, which means that I
got a rare chance to watch half a week's worth of netnews go by with stderr
connected to my terminal.

There were about 1000 messages piled up, and 31 of them were thrown away
before my very eyes, with a message saying "out of sync, skipping xxx",
where "xxx" was each line of a discarded message. This means that 1.5
percent of the messages were lost, and in every case, the lost messages were
preceded in the batch by a zero-length control message.

I remember Chuqui's original posting, then several challenging him saying it
wasn't happening, then Chuqui re-asserting that it was happening. One thing
that I don't remember is whether or not anybody ever posted a specific fix to 
unbatch. In other words, do I have to go into unbatch and fix this or has
somebody posted the fix only to have the fix gobbled upstream of me by the
very bug it was supposed to correct.
-- 
	Brian Reid	decwrl!glacier!reid
	Stanford	reid@SU-Glacier.ARPA