alexus at gmail.com
Tue Aug 23 15:52:31 CEST 2011
I'm not sure what am I suppose to do with that and how would that help me...
[root at 6prx01 ~]# varnishadm help
CLI connected to 127.0.0.1 6082
vcl.load <configname> <filename>
vcl.inline <configname> <quoted_VCLstring>
param.show [-l] [<param>]
param.set <param> <value>
ban <field> <operator> <arg> [&& <field> <oper> <arg>]...
[root at 6prx01 ~]#
On Mon, Aug 22, 2011 at 9:15 PM, Simon Males <sime at sime.net.au> wrote:
> On Tue, Aug 23, 2011 at 1:28 AM, alexus <alexus at gmail.com> wrote:
>> I'm trying to implement "saint mode" into my default.vcl, I copy and
>> paste that little snippet that came with that documentation but now my
>> varnish wont even start.
>> Misbehaving servers — Varnish version 3.0.0 documentation
>> either I'm putting that into a wrong place or something else I dont
>> know, all I know as soon as I comment it out, varnish starts Ok.
>> any ideas how to troubleshoot it?
> You may have some compiler output in /tmp/*.varnish.
> Otherwise you can compile it on demand with a running varnishd:
> $ varnishadm -S /etc/varnish/secrect -T localhost:6082 vcl.load
> name_the_vcl /etc/varnish/default.vcl
> (I'm using 2.1, so varnishadm in 3.0 may be different).
> Failure to compile will produce 'classic' compiler type output.
> Moons ago I had a problem when compiler would fail when I copied and
> pasted something some the web, it felt like it was a funny line ending
> Simon Males
More information about the varnish-misc