Relative include paths cause VCL compilation error
shiver opened this issue · 0 comments
shiver commented
Setup:
- Varnish-4.1.0 revision 3041728
- VSF (master ea07f16)
- Ubuntu 14.04
Recent changes to the VSF VCL files appear to have introduced relative VCL path includes.
I have a basic fresh install of Varnish and the VSF mod, having only added the VSF include at the top of /etc/varnish/default.vcl per the installation instructions.
vcl 4.0;
include "/etc/varnish/security/vsf.vcl";
...
When running Varnish I receive a VCL compilation error:
$ sudo varnishd -f /etc/varnish/default.vcl
Error:
Message from VCC-compiler:
Cannot read file 'build/variables.vcl': No such file or directory
('/etc/varnish/security/vsf.vcl' Line 10 Pos 9)
include "build/variables.vcl";
--------#####################-
Running VCC-compiler failed, exited with 2
VCL compilation failed
To fix I have prefixed each include path in vsf.vcl and config.vcl with the "security" symlink.
EG:
include "security/build/variables.vcl";
include "security/local.vcl";
Is there another way to approach this which does not involve altering the include paths, or is this an actual issue?
Thanks