Re: NNTPC: Expire - weird behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hans.Lambermont@nl.origin-it.com (Hans Lambermont) wrote:

> You intended the following :
> 
> minFilesFreePercent 70
> minBlocksFreePercent 95  (i'd propose < 95% here, we use even 70%
>                           because we have seen users that very quickly
> 			  filled our 8 GB cache. With 70% we mostly
> 			  start expiring soon enough.)
> 
> The comments should read:
> 
> minFilesFreePercent xx : start expire when more than xx% of inodes are
>                          in use, and do not stop expiring until below xx%
> 
> minBlocksFreePercent xx : start expire when more than xx% of blocks are
>                          in use, and do not stop expiring until below xx%

Sorry, but in this case the config variables' names are simply braindead.
These should read "maxFilesInUsePercent" and "maxBlocksInUsePercent".

Elmi.

-- 
"Ingenieurin, Elektrikerin, Architektin und junger Mann mit Knackarsch zum
 Kaffee-Kochen gesucht"              (von einem Plakat, zitiert von Princess)

........................................... whois -h whois.ripe.net ELMI-RIPE


[Index of Archives]     [Yosemite]     [Yosemite Campsites]     [Bugtraq]     [Linux]     [Trn]

Powered by Linux