Tim Kientzle [EMAIL PROTECTED] writes:
According to the Getting Started guide on the website, I should be
able to just run varnish with the default VCL, but that doesn't
actually work.
Yes, it does. Varnish requires that you specify *either* a VCL script
*or* a backend on the command line.
In message [EMAIL PROTECTED], Tim Kientzle wri
tes:
# Start Varnish by typing: varnishd -f /etc/varnish/default.vcl
Which clearly doesn't actually work.
This is wrong and should be fixed. The default VCL does not contain
any backend specifications, as we have no idea where to find the
users
Hi,
On Tue, Jul 01, 2008 at 10:02:52AM +1200, Darryl Dixon - Winterhouse Consulting
wrote:
Afterwards you can
vcl.discard old-unique-name
if you want to get rid of it.
It is pretty easy to automate this all with expect(1) as well, if an
'automated' reload solution is required :)
In message [EMAIL PROTECTED], Skye Poier Nott writes
:
Is it possible to reload /usr/local/etc/varnish/default.vcl without
restarting?
From the docs it looks like one way to do this would be through the
telnet interface:
vcl.load some-unique-name /usr/local/etc/varnish/default.vcl
vcl.use
According to trunk/varnish-cache/bin/varnishd/mgt_vcc.c (line 80 to 160)
this is the default.vcl running if you have just defined a default
backend and nothing else:
Is the fix only to adjust the default.vcl and the man page to reflect
this? (I could make a document-patch :-)
( #*# are my
Audun Ytterdal wrote:
According to trunk/varnish-cache/bin/varnishd/mgt_vcc.c (line 80 to 160)
this is the default.vcl running if you have just defined a default
backend and nothing else:
Is the fix only to adjust the default.vcl and the man page to reflect
this? (I could make a document
