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

On Sun, 13 May 2001, Robert Collins wrote:

> However I have _no_ idea how to implement file watching in unix (doesn't
> it require a signal?) at all, let alone portably :] We could walk the
> config tree for file nodes every minute or two and re-read that node
> though.

IMO, it is a bad idea to auto-detect changes in configuration files.
All reconfigurations should only be done when Squid is explicitly told
so. I would be happy to explain my assertion if needed.

There are always exceptions to the rule, when watching files will work
correctly and is handy. However, those exceptions can (and, IMO,
should) be handled by having an external process that watches the
files for updates and sends Squid a re-configure signal as needed.

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.

        # re-read on reconfigure by default:
        acl foobar <include src="filename"> ...

        # exception (e.g., too expensive to reconfigure)
        # Squid should probably warn of these during reconfigure
        acl foobar <include src="filename" reconfigure="no"> ...

Actually, the "import" and "reconfigure" options (whatever their
syntax will end up being) probably make sense for virtually all
configuration options in squid.conf, and even as separate thing, not
just ACLs. It is, essentially, a pre-processor directive, after all:

        http_port 8080
        <include src="somecustomoptions.cfg" reconfigure="yes">
        access_log /dev/null
        ...

$0.02,

Alex.
Received on Sat May 12 2001 - 17:18:04 MDT