Path: utzoo!utstat!news-server.csri.toronto.edu!mailrus!uwm.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!sdd.hp.com!ucsd!ucselx!nash
From: nash@ucselx.sdsu.edu (Ron Nash)
Newsgroups: news.software.b
Subject: Re: Duplicate Message-IDs in history
Message-ID: <1990Jun4.213617.10905@ucselx.sdsu.edu>
Date: 4 Jun 90 21:36:17 GMT
References: <1990Jun1.162428.21301@ucselx.sdsu.edu> <1990Jun2.230633.6125@utzoo.uucp>
Reply-To: nash@ucselx.sdsu.edu (Ron Nash)
Organization: San Diego State University Computing Services
Lines: 26

In article <1990Jun2.230633.6125@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>In article <1990Jun1.162428.21301@ucselx.sdsu.edu> nash@ucselx.sdsu.edu (Ron Nash) writes:
>>I have a clearer example of the Cnews problem I am having.  The problem
>>seems to be that history is not recoginizing duplicate Message-ID's
>>from my UUCP feeds.  

>You need to check what's happening when things arrive by uucp.  From the
>file excerpts you include, I very strongly suspect that you have a B News
>system still active on your machine, and *both* are processing the incoming
>traffic.  You have both B-type and C-type history entries, for example.
>For a guess, the reason why duplicates are getting through is that B News
>is not using dbz.

The problem turned out to be caused by 1) /bin/rnews did not have world
execute causing UUCP to run 2) an ancient copy of /usr/bin/rnews left
over from the Bnews to Cnews conversion last year.  Cnews uses dbz and
Bnews was using dbm allowing the duplicate articles and general chaos
I was having.

Thanks to all who replied and sent email.

-- 
Ron Nash
San Diego State University
Internet:  nash@ucselx.sdsu.edu
UUCP:      ucsd!sdsu!ucselx!nash