Newsgroups: news.software.b
Path: utzoo!henry
From: henry@zoo.toronto.edu (Henry Spencer)
Subject: Re: Problem with C news addmissing (actually histdups)
Message-ID: <1991Mar11.164715.24742@zoo.toronto.edu>
Date: Mon, 11 Mar 1991 16:47:15 GMT
References: <1991Mar5.184229.10851@urbana.mcd.mot.com> <1991Mar6.061734.19538@zoo.toronto.edu> <1991Mar8.213005.1660@colnet.uucp>
Organization: U of Toronto Zoology

In article <1991Mar8.213005.1660@colnet.uucp> res@colnet.uucp (Rob Stampfli) writes:
>I ran addmissing once, when I noticed a problem with an orphan note.  It
>worked fine.  I don't generally run it, though, on any regular basis.  My
>question:  is it something I should stick it in the crontab to sweep out
>any potential problems once a week or so, or should I only run it when there
>is cause?

The intent was that it be run only for cause.  Barring system failures or
resource exhaustion, C News does not lose articles.  When I ran addmissing
for testing, at a time when our system had run many months without a history
rebuild, it turned up a total of four articles, all orphaned due to a messy
crash during news processing.  We're admittedly in a favorable position
because utzoo is very reliable.  If you've got significant reliability
problems, you might want to run addmissing, say, once every couple of months.
If you need it more often than that, you've got problems that need fixing.
-- 
"But this *is* the simplified version   | Henry Spencer @ U of Toronto Zoology
for the general public."     -S. Harris |  henry@zoo.toronto.edu  utzoo!henry