At 08:39 AM 2/11/01 -0500, you wrote:
>I'm beginning to think there is a problem with the way multi-parts
>work although as I'm new to DNews it may be me. I'm seeing very few
>completed messages arriving in the main part area even though when I
>look at my upstream server all the parts are there and have been for a
>number of hours. My server also seems to spend most of it's time
>downloading the parts and storing them in the multi-part area but my
>partlost.log rarely shows anything in it. I even increased the size of
>the multi-part buffer to 6.5 gig and it makes no difference.
That sounds odd,
Send me the output of
tellnews status
and
part*.log
And newsfeeds.conf. and dnews.conf
ChrisP.
>David.
>
>On Fri, 09 Feb 2001 16:30:45 +1300, Support Auckland
><[EMAIL PROTECTED]> wrote:
>
> >At 10:52 PM 2/7/2001 -0500, you wrote:
> >>I've been trying to work out how multi-parts work with dnews, and
> >>can't :-)
> >>
> >>I have a 3gig multi-part area set up on my disk. My current report
> >>tells me:
> >>
> >>Parts 2915:351 1212mb, In 14232 6125mb, Complete 5514 2309mb, 39% 38%,
> >>Rej 0%
> >>Drop 3252mb, Err 0 Rotated 306 minutes ago, Upto 1 0.45 30
> >>
> >>Which as far as I know, means I have 1.8gb left, but it's dropping
> >>over 3gig. The 39% is actually unusually low, it's normally around
> >>76% but my provider has been doing some maintanence.
> >>
> >>Can someone explain the life of a 'part' as it comes in from the suck
> >>feed?
> >>
> >>Here is what I expect to happen. A part is sucked in, it goes into the
> >>multi-part area. Something checks to see if it belongs to an existing
> >>part. If it is and makes a complete part, all the parts are moved onto
> >>the normal piles. When the logs get full, it deletes the oldest part
> >>and subsequent parts that belong to it.
> >>
> >>However, as my multi-part area never get's more than about 1.2gig in
> >>it, it's obviously not filling it up. So, what and why is it deleting
> >>parts before it's full?
> >
> >Dnews doesn't use the part buffer "super space efficiently'" it does use
> >it "super time efficiently" , specifically it avoids fragmentation and all
> >reads/writes
> >are contiguous, this is quite important as the part buffer has to have
> so much
> >data going thru it. The down side is at any one time half of the space you
> >have
> >reserverd may not be used.
> >
> >So to answer your question, items are stored in the order they arrive, when
> >one is complete the comlpete items are sent into dnews, thus leaving gaps
> >in that part of the part buffer, the gaps remain until dnews cycles
> right thru
> >your entire part buffer
> >
> >Your part buffer is '306' minutes long, which is fine, you won't be loosing
> >any significant
> >amout of parts due to this.
> >
> >>Also, if I revert back to not using the multi-part function, is there
> >>a facility for getting the parts out of the multi-part area and into
> >>the main piles?
> >
> >Nope sorry, you get an hour worth of broken parts if you turn it off.
> >
> > ChrisP.
> >
> >
> >
> >>Sorry about the ramble.
> >>David.
> >>------------ And now a word from our sponser ------------------
> >>For a quality usenet news server, try DNEWS, easy to install,
> >>fast, efficient and reliable. For home servers or carrier class
> >>installations with millions of users it will allow you to grow!
> >>---- See http://netwinsite.com/sponser/sponser_dnews.htm ----
> >
