health check path doesn't change after VCL reload (2.0.6)

[John Norman]

That's great.

Still, the VCL indicated as "active" had a different path for the health
check.

On Wed, Feb 24, 2010 at 3:24 PM, Poul-Henning Kamp <phk at phk.freebsd.dk>wrote:

> In message <b6b8b6b71002241137j71ae210r35487c328e8f69d1 at mail.gmail.com>,
> John N
> orman writes:
>
> >We notice that after VCL is reloaded, our old health check path is still
> >getting checked.
> >
> >The only thing that seems to fix it is a varnish restart.
>
> No, unloading the old VCL code should also do it.
>
> We keep polling the backends of all loaded VCL, so they are all
> ready to roll the moment you do "vcl.use mumble".
>
>
> --
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk at FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20100224/e10fed62/attachment-0001.html>