Re: Peer twiddling

We have had this discussion a couple of times.

The most logical approach is extending the cachemgr interface with more
active options like this. Have done so previously when I needed to
selectively reload parts of the configuration (more specifically included
acl definitions). This however was not accepted by Duane at the time.

I think the last time we discussed this the conlcusion was that there
should be a better local control mechanism replacing the -k xxx signals
used today, for example by using a named pipe or unix domain socket. This
could then easily be extended with active actions like the ones discussed.

--
Henrik

Adrian Chadd wrote:

> Hi guys,
>
> I've had some requests by ISPs to enable a method of twiddling the
> peer configuration without restarting squid. This is so an external
> program can change various bits of the peer's configuration.
>
> The current quick modification simply enables/disables a given
> peer via an internal URL (/squid-internal-peer/peername:peerport/enable
> or .../disable), but later on down the track a few other things
> might be twiddled (eg peer weights, default parent status.)
>
> I've thrown it into the 'peertwiddle' branch on sourceforge.
> The patch is pretty simple in itself, but I'm curious to know if
> anyone can suggest a better way of implementing it.
>
> I'd like for this to eventually find its way into squid-HEAD
> and squid-2.4.
>
> (The diff URL is http://squid.sourceforge.net/cgi-bin/diff/peertwiddle)
>
> Thanks!
>
> Adrian
Received on Thu Sep 13 2001 - 03:03:11 MDT