Path: utzoo!censor!becker!bdb
From: bdb@becker.UUCP (Bruce Becker)
Newsgroups: tor.news
Subject: Re: duplicate articles (was: drought?)
Message-ID: <450@becker.UUCP>
Date: 25 Apr 89 12:24:17 GMT
References: <1989Apr19.173049.1553@utzoo.uucp> <429@becker.UUCP> <1989Apr22.142911.1685@ziebmef.uucp> <4777@vpk3.UUCP>
Reply-To: bdb@becker.UUCP (Bruce Becker)
Organization: G. T. S., Toronto, Ontario
Lines: 43

In article <4777@vpk3.UUCP> bob@attcan.UUCP (Bob Kyryliuk) writes:
| [...]
|Here's a sample duplicate article from mark@sickkids:
|
|	article headers (note identical Message-ID's):
|
|		148:Path: attcan!utgpu!lsuc!sickkids!mark
|		148:Message-ID: <259@sickkids.UUCP>
|
|		151:Path: attcan!utzoo!yunexus!maccs!lsuc!sickkids!mark
|		151:Message-ID: <259@sickkids.UUCP>
|
|	history.d entries (note that they arrived the same day):
|
|		<259@sickkids.UUCP>	04/22/89 02:23	tor.news/148
|		<259@sickkids.UUCP>	04/22/89 13:02	tor.news/151
|
|As we often get numerous duplicate articles because of our multiple feeds
|(ie 1000-10000 per day :-) which are handled correctly, it seems odd that 
|a few of the tor.news.* articles are slipping in past the B-News software.
| 
|Anyone have any clues?

	I have duplicates consistently in my news, and not
	just in "tor" either. The reason why I ended up complaining
	was that a lot of the recirculated articles *ought* to
	have been rejected but weren't for some reason.

	I had put the problem down to a possible flaw in the
	port of dbm to this machine (which theory I have yet
	to test), but "history.d" sounds like the non-dbm type
	of history mechanism, so there may be a flaw in the
	logic of the B News history system (version 4.3.1.4).

	I have put off dealing with this problem until I upgrade
	my News software, which I'm told will be available RSN...

Cheers,
-- 
   __	 Bruce Becker	Toronto, Ont.
w \cc/	 Internet: bdb@becker.UUCP, bruce@gpu.utcs.toronto.edu
 `/v/-e	 BitNet:   BECKER@HUMBER.BITNET
_<  >_	 "A divine sparc turned me from nextrophilia" - NoNuke of the North