When building a large number of Varnish servers last week, I noticed that one of the servers wasn't picking up my custom varnish_listen_port. As it turns out, running systemctl status varnish revealed that the systemd unit file being used was /lib/systemd/system/varnish.service.
This role currently stores a varnish unit file at /etc/systemd/system/varnish.service, but it looks like it would be more correct to store it at the /lib path. I'm going to do a test on a branch and see if it works the same—if so, I'll move the file there in this role's configuration, and then make sure the /etc file is symlinked to the /lib one.
When building a large number of Varnish servers last week, I noticed that one of the servers wasn't picking up my custom
varnish_listen_port
. As it turns out, runningsystemctl status varnish
revealed that the systemd unit file being used was/lib/systemd/system/varnish.service
.This role currently stores a varnish unit file at
/etc/systemd/system/varnish.service
, but it looks like it would be more correct to store it at the/lib
path. I'm going to do a test on a branch and see if it works the same—if so, I'll move the file there in this role's configuration, and then make sure the/etc
file is symlinked to the/lib
one.