Wayne Bastow wrote:
> It is agood idea to look at the squid.conf.default when you upgrade to
> see whether there are any changes in the configuration for the new
> version.
Another good idea is to clean your active squid.conf from all the
documentation cruft once you have got it running. The documentation in
squid.conf is useful on the first setup, but then is it more in the way
than helpful. It is better to refer to squid.conf.default for the
documentation.
cat squid.conf | grep "^[a-z]" >squid.conf.new
edit squid.conf.new adding any comments describing your setup
then replace squid.conf with squid.conf.new.
The benefits are
* squid.conf gets a lot smaller, allowing you to get an good overview of
what you have configured.
* it contains no documentation that will be outdated when you upgrade to
a newer Squid release
* since the configuration file is much smaller it is also much easier to
go thru it and verify what needs to be updated when you upgrade Squid.
/Henrik
Received on Thu Feb 03 2000 - 14:50:00 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:50:56 MST