any idea why I am getting this storage.conf error and it throttles news.
Wilson, Sue LCC
Sue.Wilson at lcc01.usace.army.mil
Thu Jun 3 02:13:54 UTC 2004
I thought you can't change the classes in storage conf, but if you can=20
Are you saying I should make the newgroups: *.usace class 0
And the newsgroups: * 1
And add the catch all=20
Or=20
Should will just adding the catch all take care of it
??
I will do the catch all anyway, that much I understand.
thankyou
-----Original Message-----
From: inn-workers-bounce at isc.org [mailto:inn-workers-bounce at isc.org] On
Behalf Of Christoph Biedl
Sent: Wednesday, June 02, 2004 5:39 PM
To: inn-workers at isc.org
Subject: Re: any idea why I am getting this storage.conf error and it
throttles news.
Wilson, Sue LCC wrote...
> Jun 2 20:45:53 nntp innd: [ID 297438 news.crit] SERVER throttle no
matching
> entry in storage.conf storing article - throttling
> Jun 2 20:45:53 nntp innd: [ID 492761 news.error] SERVER cant store
article:
> no matching entry in storage.conf
Yes:
> method tradspool {
> newsgroups: *
> class: 0
> size: 0,100000
> }
This file file all articles with a wire size of less than 100000 Bytes
into that storage class. Including those in usace.* which is what you
proably do not want. First match wins and I guess the second declaration
should be in the first place.
> method tradspool {
> newsgroups: usace.*
> class: 1=20
> size: 0,2000000
> }
Consequently this will take care of articles in usace.* with a size
between 100k and 2M.
> (END)
It's a very good idea to add an catch-all at the end here, even if
simply discards articles, like:
method trash {
newsgroups: *
class: 99
}
At the moment, articles for !usace.* larger than 100k have no place to
go - and you've probably got feeded such a beast. The same would happen
with a 2M article for usace.* although maxartsize in inn.conf would
block such articles entirely.
Christoph
More information about the inn-workers
mailing list