Mailing List Archive: How to best debug your VCL?

How to best debug your VCL?

Nov 10, 2006, 4:39 AM

Post #1 of 3 (586 views)

Hi!

I'm currently trying out different rule settings in VCL to make sure
just the right things are cached, and if the rulesets gets a bit
complex I'd like to know how to best debug it, that is how to best
know which if statements was true or not.

Is there for example a log statment? I couldn't find anything in the
vcl man page, and "log" didn't work in any case, but maybe it's called
something else? :-)

--
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management http://www.nuxeo.org/

How to best debug your VCL? [ In reply to ]

phk at phk

Nov 10, 2006, 6:53 AM

Post #2 of 3 (574 views)

Permalink

In message <319e029f0611100339t21ee094wc8a32759040cac40 at mail.gmail.com>, "Lenna
rt Regebro" writes:
>Hi!
>
>I'm currently trying out different rule settings in VCL to make sure
>just the right things are cached, and if the rulesets gets a bit
>complex I'd like to know how to best debug it, that is how to best
>know which if statements was true or not.

There is a parameter that enables VCL logging. In your shmlog
you will get a log entry for each executed "token" of the VCL
code with line+char.

--
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.

How to best debug your VCL? [ In reply to ]

regebro at gmail

Nov 10, 2006, 9:11 AM

Post #3 of 3 (563 views)

Permalink

On 11/10/06, Poul-Henning Kamp <phk at phk.freebsd.dk> wrote:
> There is a parameter that enables VCL logging. In your shmlog
> you will get a log entry for each executed "token" of the VCL
> code with line+char.

Aha, the vcl trace setting, got it, thanks!

--
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management http://www.nuxeo.org/