Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!tut.cis.ohio-state.edu!n8emr!colnet!res
From: res@colnet.uucp (Rob Stampfli)
Newsgroups: news.software.b
Subject: Re: Problem with C news addmissing (actually histdups)
Message-ID: <1991Mar8.213005.1660@colnet.uucp>
Date: 8 Mar 91 21:30:05 GMT
References: <1991Mar5.184229.10851@urbana.mcd.mot.com> <1991Mar6.061734.19538@zoo.toronto.edu>
Organization: Little to None
Lines: 12

>>The following context diff is a fix for the problem in expire/histdups:
>
>This one is annoying but more or less harmless, since you get it only
>if addmissing didn't have any work to do. :-)

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?
-- 
Rob Stampfli, 614-864-9377, res@kd8wk.uucp (osu-cis!kd8wk!res), kd8wk@n8jyv.oh