Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ncr-sd.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!ncr-sd!greg
From: greg@ncr-sd.UUCP (Greg Noel)
Newsgroups: net.unix,net.news,net.wanted.sources
Subject: Re: rn again - seeing articles more than once
Message-ID: <384@ncr-sd.UUCP>
Date: Mon, 6-Jan-86 15:55:34 EST
Article-I.D.: ncr-sd.384
Posted: Mon Jan  6 15:55:34 1986
Date-Received: Tue, 7-Jan-86 04:34:06 EST
References: <1609@Shasta.ARPA> <377@ho95e.UUCP> <2447@ukma.UUCP> <1730@cbosgd.UUCP> <379@ho95e.UUCP> <2816@glacier.ARPA>
Reply-To: greg@ncr-sd.UUCP (Greg Noel)
Organization: NCR Corporation, San Diego
Lines: 21
Xref: watmath net.unix:6766 net.news:4507 net.wanted.sources:1701

In article <2816@glacier.ARPA> reid@glacier.UUCP (Brian Reid) writes:
>
>The Xref failure is somehow linked to unbatching, but not in any
>deterministic way that I have been able to put my finger on. Since the
>consequences of this bug are not dire, we have not devoted a lot of work to
>fixing it.

I believe he is correct, and since the consequences are not dire, I have
not looked into it very much, either, but I believe the senario is that
the Xref information is calculated \before/ the article is inserted and
when the article is actually inserted, inews finds that one of the article
numbers is already in use and rotates to the next one, making the Xref
information incorrect.  The result is that when rn marks the articles as
read, it can potentially mark the \wrong/ article.  The result is that
you see some articles more than once and you \don't/ see articles that
were incorrectly marked as seen.  It is linked to unbatching because
there tend to be several <hmmmmm -- what's the plural of inews?  Inewses?>
running at the same time and potentially trying to deliver articles into
the same newsgroup.
-- 
-- Greg Noel, NCR Rancho Bernardo    Greg@ncr-sd.UUCP or Greg@nosc.ARPA