After looking into this more, it seems to be just a small permission problem.
Doing a chmod 777 on the directory containing the compiled VCL does the trick. My guess is that when varnishd is runs, it switches from root to nobody, and nobody doesn't have the right permissions for that directory. Not sure what changed between 3.0.5 and 4.0. Maybe the VCL compilation is not carried by root anymore but by nobody? For security reasons? -H
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
