Robert Felber
Wed, 16 Jan 2008 10:53:26 -0800
On Wed, Jan 16, 2008 at 06:09:20PM +0100, fili wrote: > > > >Ok, a bug. Fixing appears troublesome (breaks lowest-resource-usage-policy). > >Not certain whether requests which will be answered with 'rc:' should > >generally not be cached (this wouldn't break > >cache-resources). > > > >$CACHESIZE=0; > > > > Thanks Rovert, I've got it up and running now using $CACHESIZE=0; > Do you think that no-caching might result in higher loads on a mail-heavy > server?
Not load, but more smtpd processes waiting for a polw reply.
> I've read the release info of 0.1.14 beta-14, specificly:
> >results with 'rc:' as action are not cached
> Is it useful for my current setup to update?
Useful yes, required, not really.
> And should I then change $CACHESIZE back to the default value?
You can delete it (with the latest version).
> On a different note, wouldn't it be a good idea to introduce a variable like:
> $BLOCK_RETRY_TTL = 30;
>
> 30 being the seconds in which retries will be temporarily blocked.
> If this value is set to 0, then Policyd-weight won't block retries at all.
This is the job of $NTTL and $NTIME in concert
$NTTL (default: 1)
The client is penalized for that many retries.
$NTIME (default: 30)
The $NTTL counter will only be decremented if the client waits
at least $NTIME seconds.
--
Robert Felber (PGP: 896CF30B)
Munich, Germany
____________________________________________________________
Policyd-weight Mailinglist - http://www.policyd-weight.org/