Re: [squid-users] squid.conf: continuation lines?

On Sun, 13 May 2001, Henrik Nordstrom wrote:

> Alex Rousskov wrote:
>
> > I suspect that Henrik did not have auto-detection in mind but rather
> > was talking about [optionally] re-loading #included files when Squid
> > is asked to be reconfigured.
>
> Actually I am thinking about automatic detection of changes in
> configuration data such as the definition of an included ACL list.
>
> At this stage I consider automatic reload generic configuration
> directives a bad thing. For such things a explicit action is required.
>
> Should probably be optional, but it is quite important in environments
> where ACL lists is changing a lot. reconfigure is a very heavy and quite
> dangerous operation.

Fine. I still assert that checking for ACL updates by default is not
a good idea. In general, when I edit a configuration file (or
#included ACL list), I do not want the changes to be propagated until
I am ready. And since most packages, including todays Squid do not
auto-detect changes, the default behavior should not change.

Since adding more actions to cache manager is not allowed, to support
isolated per-directive (e.g., large ACL) reconfiguration, a
simple "console" interface may be appropriate:
        telnet localhost 3129
        (squid) enable
        ******
        (squid) reconfigure acl bigfoobar

If that is too much, we can have a global --enable_config_autosync
<check_interval> ./configure option or an equivalent per-acl option.
        
Alex.
Received on Sun May 13 2001 - 11:23:10 MDT