Hi,
There are two other solutions if you absolutely cannot remove articles
(which is of course what a news server is designed to do). You must also
ensure you are doing an expire each night, even if you're not expiring any
articles.
The method we recommend was added in 56a (Should be in 56a3), and involves
setting a maximum size for the history. The setting in dnews.conf is -
hist_max 2000000000
This will cause dnews to trim the history when this limit is reached.
- Roydon L.
----- Original Message -----
From: <[EMAIL PROTECTED]>
Newsgroups: netwin.dnews
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 02, 2002 7:33 PM
Subject: History over 2gig limit?!
> Hi!
>
> Today my DNEWS 5.5g1 told me:
>
> History over 2gig limit reduce pile size of non binary piles 2050MB >
2050MB
>
> ... and he's right. :-)
>
> I do not carry many binaries and have a large spool. What now?
> I found an old answer (July 2001) to the same question:
>
> >There is presently a 2GB limit on the file size, which only becomes a
> >problem if large numbers of articles are not being expired. A solution is
> >being worked on to solve this problem.
>
> Is that solution now available?
>
> >As a temporary solution until we have a real fix available we recommend
you
> >reduce the pile sizes for non-binary groups, as non binary piles store a
> >greater number of articles.
>
> Hm that cannot be done, because we need all the old articles...
>
> >It is possible a 'rebulid_index' may also help to resolve the problem if
the
> >history
> >contains dangling entries due to some previous fault (upgrading to 5.5c5
is
> >also
> >a good idea)
>
> I just started a 'rebulid_index', maybe this helps...
>
> ++ralph
>
