Xref: utzoo news.admin:6957 news.misc:3607
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!brutus.cs.uiuc.edu!coolidge
From: coolidge@brutus.cs.uiuc.edu (John Coolidge)
Newsgroups: news.admin,news.misc,alt.conspiracy
Subject: Re: Who's Messing With The Usenet ?
Summary: But does it drop message-ids and keep articles?
Keywords: article, duplication, monkey business
Message-ID: <1989Sep18.041601.15352@brutus.cs.uiuc.edu>
Date: 18 Sep 89 04:16:01 GMT
References: <2056@avsd.UUCP> <1989Sep16.061700.4572@brutus.cs.uiuc.edu> <1989Sep17.181534.16677@polyslo.CalPoly.EDU>
Sender: news@brutus.cs.uiuc.edu
Reply-To: coolidge@cs.uiuc.edu
Organization: U of Illinois, CS Dept., Systems Research Group
Lines: 23

hoyt@polyslo.CalPoly.EDU (Sir Hoyt) writes:
>In article <1989Sep16.061700.4572@brutus.cs.uiuc.edu> I write:
>>the history file can't be appended to (disk full, maybe?). In that case,
>>I could imagine news dropping the Message-ID on the floor, then accepting
>>the same id later. Doesn't seem likely to me (well, *I'D* check for it
>>when writing a news :-) ), but maybe...
>	It's happend here at polyslo before.  Expire on B news makes a copy of
>	the history file before processing.  Our history file is
>	about 4Meg, which makes 8Meg, and when you have ~10Meg free....

But does it drop the message id from history while keeping/spooling the
article? That was the behavior that I thought was unlikely... just running
out of history file space seems perfectly reasonable, but reacting to
a failure to append to the history file by keeping the article sounds
somewhat strange...

--John

--------------------------------------------------------------------------
John L. Coolidge     Internet:coolidge@cs.uiuc.edu   UUCP:uiucdcs!coolidge
Of course I don't speak for the U of I (or anyone else except myself)
Copyright 1989 John L. Coolidge. Copying allowed if (and only if) attributed.
You may redistribute this article if and only if your recipients may as well.