Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!uunet!coplex!dean
From: dean@coplex.uucp (Dean Brooks)
Newsgroups: news.software.b
Subject: C-News Expiration/Unbatching - Collision?
Message-ID: <1991Feb2.064711.10702@coplex.uucp>
Date: 2 Feb 91 06:47:11 GMT
Organization: Copper Electronics, Inc.
Lines: 32


   After running C-News for a week or so, I noticed something that
seemed like a possible problem.

   We had a C-News expire taking place at the sametime that incoming
batches were being dispersed into the /usr/spool/news area.  Both
functions seemed to take place fine at the same time...

   My question is this;  are the two functions compatible with each
other?  It would seem that ONE function must have complete control
of the history file.  Otherwise, it would seem that articles would
be missing/extra in the history file.

   Along the same line, I have noticed that there are articles "staying"
around in /usr/spool/news past the expiration delay time.

   I have the "/bound/" entry in explist set to "0-1-31", the "/expire/"
entry set to 14 days, and the only other line expires ALL articles at
the value of "5" (min/max bounds are taken from the "/bound/" line.

   Is there any collision I should check for that may cause history
to contain the wrong information (that could screw up expiring).  I
really dont want to have articles staying around forever, as that was
one reason I switched to C-News...

   Any experienced C-News hacks have any suggestions?   Thanks...

--
dean@coplex.UUCP   Dean A. Brooks
                   Copper Electronics, Inc.
                   Louisville, Ky
UUCP: !uunet!coplex!dean