nnrpd issue

[Pavel V. Knyazev]

Greetz.

Folks, i'm all ready to go on ...

----- Original Message -----
From: "Katsuhiro Kondou" <Katsuhiro_Kondou at isc.org>
To: <inn-workers at isc.org>
Sent: Friday, December 20, 2002 2:41 PM
Subject: Re: nnrpd issue


> In article <yllm32uxrh.fsf at windlord.stanford.edu>,
> Russ Allbery <rra at stanford.edu> wrote;
>
> } If the problem is with the storage API calls, Katsuhiro's patch should
> } have helped.  So I'm not sure what's going on.
>
> Can I make it clear what is going on?
>
> In article <001701c29493$5e5dbca0$4201800a at surnet.ru>,
> "Pavel V. Knyazev" <pasha at surnet.ru> wrote;
>
> } I thought 'ctlinnd renumber group' would help me ... it didn't somehow.
> } I don't get it at all, where does it get lowmark number after that :-\
> } Seems like renumber doesn't do things it has to. I may be wrong though.
>
> Is lo number updated after 'ctlinnd renumber ...'?
> And how does it look like about this;

Nope.
My steps:

1) at the beginning we have
8:21pm image:db> grep alt.binaries.sounds.mp3\  active
alt.binaries.sounds.mp3 0003823324 0003757377 y

2) i change manually lo, so we have
8:22pm image:db> grep alt.binaries.sounds.mp3\  active
alt.binaries.sounds.mp3 0003823324 0003779999 y

3) i renumber it and grep it over
8:24pm image:db> ctlinnd renumber alt.binaries.sounds.mp3
Ok
8:24pm image:db> grep alt.binaries.sounds.mp3\  active
alt.binaries.sounds.mp3 0003823328 0003757377 y

I thought, if i changed lomark to a higher value, my 'NEXT'
command would take less time to do its job. I was wrong.

> } group alt.binaries.sounds.mp3
> } 211 63130 2395958 2460705 alt.binaries.sounds.mp3
> } next
> } 223 2409831 <aqrm12$ga2$6 at reader12.wxs.nl> Article retrieved; request
text
> } separately.
>
> Article number is the same as lo after renumbering?

No, renumber just takes lo from overview database, hence we have:
group alt.binaries.sounds.mp3
211 64441 3757377 3823387 alt.binaries.sounds.mp3
next
223 3771177 <U%tW9.67803$Yq2.467889 at news.easynews.com> Article retrieved;
request text separately.

Moreover, if i change lo manually *without* doing renumbering after,
i still see the same lo after group command, take a look at this:

8:31pm image:db> grep alt.binaries.sounds.mp3\  active
alt.binaries.sounds.mp3 0003823411 0003779999 y
8:31pm image:db> nnrpd
200 image.surnet.ru InterNetNews NNRP server INN 2.3.4 (20021002 prerelease)
ready (posting ok).
group alt.binaries.sounds.mp3
211 64465 3757377 3823411 alt.binaries.sounds.mp3
quit
205 .
8:32pm image:db> grep alt.binaries.sounds.mp3\  active
alt.binaries.sounds.mp3 0003823411 0003779999 y


See that?

--
Pavel V. Knyazev