🚀 go-pugleaf

In article <89s3rf$fvr$1@linux.warren.demon.co.uk>, Nick Leverton 
<leveret@warren.demon.co.uk> wrote:
>In article <FqwHH7.A4s@dangl.demon.co.uk>,
>Dan Glover  <dan@dangl.demon.co.uk> wrote:

>>I think an examination of INN-1.7.2 is the next stage, unless any
>>comment from Freeserve is forthcoming.

My first pass at this hasn't borne fruit - I was hoping for something
which said: "while articles are being expired the response to a GROUP
command might be inconsistent".  If it *is* possible then I'd expect it
to be a transient condition, hopefully only affecting an individual
group for a very short time.  I don't know my way around INN well enough
to spot this in the source without spending a long time.

Re-reading the logs I see one of the cases of "low article number
syndrome" occurred during the evening so I'm more inclined towards the
theory that there's another news machine which occasionally pops up and
is out of sync with the others.  Obviously some comment by POL staff
about the architecture would help in establishing whether this is
actually a possibility.

>It may be helpful to mention that I'm running INN 1.7.4 with Slurp +
>y2k patches, taking my feed from Freeserve, and I experienced no problems
>or missing messages in any of the groups I take.  NEWNEWS is fast on
>Freeserve too.

Indeed. I note that there doesn't seem to be any suggestion to remove
NEWNEWS from the draft NNTP son-of-rfc977.  If it ever becomes a
standard we can presumably berate all the news admins who have chosen
not to support it...

I see that you've been doing business with that nice Mr Gradwell: I'd
better sort something soon as well.

Dan

-- 
Dan Glover (dan@dangl.demon.co.uk)
Today's Excuse:
  Dew on the telephone lines.