Re: cache_dir config, move the new "maxsize" argument (-1)

I fully agree. So the question is if should we move that -1 to a
cache_dir option instead of being one of the mandatory arguments to
cache_dir?

If so, we should do it before 2.4.STABLE1 is rolled, so we need to
decide NOW.

/Henrik

> ----- Original Message -----
> From: "Andres Kroonmaa" <andre@online.ee>
> To: "Adrian Chadd" <adrian@creative.net.au>
> Cc: <squid-dev@squid-cache.org>
> Sent: Friday, February 02, 2001 7:03 AM
> Subject: Re: cache_dir config
>

> typical user will never need to tune that "-1" from default. Why force
> them to change config file for upgrade, and back if downgrade?
> Also, if we need maxfilesize, then probably in very near future we'd want
> minfilesize as well. Also, we might want to specify replacement policy
> per FS, diskload limits, ACL's, etc. we'd need to add such option
> anyway, then why brake existing one now?
>
> > Perhaps stuff like this requires a nested parser? :-)
>
> not sure what you mean, but don't we have a parser for options
> already (cache_peer [options] )?
>
Received on Fri Feb 09 2001 - 12:42:38 MST