Re: Config file...

Hi

> >I've started to really notice how huge the config file has become..
>
> This is because squid.conf(.default) is about the only documentation
> there is on how to configure it.

Sure... at the same time the config file is definitely unclear on certain
things.

I believe that the config file would benefit from a different overall
structure. At the moment things are organised in a "class" basis:

Ports/IP addresses
peers
        peer choice
        peer timeouts
        hierarchy stoplists
        
ACLS for peers

In-memory size

Disk
        low/high watermarks

ipcache sizes

Disk (again)
        sizes/directories

Logs:
        access log
        cache/cache store logs
        log settings (mime, format, etc)
        debug settings
        
external
        ftp user email address
        ftp list width
        dns processes to start and other similar settings
        ping program
        redirect program
        authentication (acls again?)

Tuning:
        wais
        request size
        refresh patterns
        reference ages
        quick_abort stuff
        negative ttls
        timeouts
        
Access Control
        http/icp
        miss_access etc

        proxy_auth_realm

cache admin email
userids
visible host names
registration
acceleration

<whoa - that's lots... and there is still LOTS left>

As some of you know, I am working on a "users guide" for O'Reilly. I am
thus very keen to get the config file into a format that is easy to use.
Preferably it will follow the sections in my book, but that would be rude ;)

I suggest that we re-arrange the config file into a layout that a new user
can work through from "top to bottom". I have a list of "must examine" tags
that should go first... this will reduce the problems that people with
firewalls and so forth have.

I am going to submit a patch for comment.

Oskar
Received on Tue Jul 29 2003 - 13:15:55 MDT