Re: [adrian@creative.net.au: Re: squid.conf and include files]

include files in squid.conf would be pretty nice, but I do not feel that
squid.conf has become pretty large. The distributed squid.conf is pretty
large yes, but the configuration you usually need for a Squid is not
very large.

The general error most people do when installing Squids is that they do
not strip down their configuration file after making the initial
configuration. There is no reason to have all that documentation and
other cruft in the active configuration file. Having it there only makes
the configuration A LOT harder to read, and risks confusion when making
upgrades/downgrades.

So in addition to supporting include files, I would like to see the
documentation separated into a separate file (maybe a man page?). Both
generated from cf.data.pre to make sure one remembers to update/write
the documentation when changing the configuration options..

/Henrik

Adrian Chadd wrote:
>
> oops ..
>
> ----- Forwarded message from Adrian Chadd <adrian@creative.net.au> -----
>
> Date: Fri, 8 Sep 2000 00:23:53 +0800
> From: Adrian Chadd <adrian@creative.net.au>
> To: Andres Kroonmaa <andre@online.ee>
> Subject: Re: squid.conf and include files
> User-Agent: Mutt/1.2i
>
> On Thu, Sep 07, 2000, Andres Kroonmaa wrote:
> >
> > squid.conf is getting pretty large. for people who operate several caches
> > it is quite timeconsuming to modify each squid.conf file when some change
> > is made that should be shared by all boxes. I've felt several times that
> > it would be nice to be able to include other config files from the main
> > squid.conf. For eg. refresh rules, acl's, or other settings common to all
> > boxes like timeouts, hierarchy peerings, etc. This way I could put only
> > host-specific stuff in main config file and the rest could be copied
> > around without fear of typos.
>
> I *REALLY* like this idea - I"ve been doing the same with some custom
> perl scripts for some time, but this would make things much easier.
>
> Can someone poke at this and verify it works? I'd like this to go into
> HEAD.
>
> Hey, I have an idea - whenever someone comes up with a patch like this,
> how about the document the system that they're touching? In this way,
> the people who do fairly large patches (eg this one) would be brain-
> dumping even skeletal documentation, which I'd be willing to docbook-ify
> and commit to the programmers guide.
>
> Adrian, dreaming about docs ..
>
> --
> Adrian Chadd "If a butterfly flaps its wings in China,
> <adrian@creative.net.au> will a women get naked in Amsterdam?"
> -- Ashley Penney on Chaos Theory
>
> ----- End forwarded message -----
>
> --
> Adrian Chadd "If a butterfly flaps its wings in China,
> <adrian@creative.net.au> will a women get naked in Amsterdam?"
> -- Ashley Penney on Chaos Theory
Received on Thu Sep 07 2000 - 14:10:39 MDT