When you do a vcl.load, the file is read, compiled into a
machine executable format and loaded into varnishd.
Any changes you make to the source file after that will not
affect the compile version which is already loaded.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
Hello, list.
I have read that config change would be effective like below at management
interface.
(according to
http://projects.linpro.no/pipermail/varnish-misc/2007-July/000598.html)
vcl.load newconf /my/new/config
vcl.use newconf
But, if main config file is /etc/default.vcl and varnishd
TiAMO <[EMAIL PROTECTED]> writes:
> I need to add more backend servers and req.http.Host definitions quite
> often, is there a way to change the config without restarting varnish
> and loose the entire cache?
vcl.load newconf /my/new/config
vcl.use newconf
> also is it possible to make varnish li
In message <[EMAIL PROTECTED]>, TiAMO writes:
>I need to add more backend servers and req.http.Host definitions quite often,
>is there a way to change the config without restarting varnish and loose the
>entire cache?
Yes, you can load a new VCL code from the CLI interface with no disruption
to
I need to add more backend servers and req.http.Host definitions quite often,
is there a way to change the config without restarting varnish and loose the
entire cache?
Or is it just simpler to have a backend on loopback and write a separate app
to handle the backend distribution without having
