[kwlug-disc] The joys of systemd ...

[Ronald Barnes]

Khalid Baheyeldin wrote on 2017-03-07 05:36 PM:

> /usr/sbin/varnishd -a :81 -T localhost:6082 -f /etc/varnish/main.vcl
> -S /etc/varnish/secret -s malloc,512m
>
> Note that I have to edit the unit file to change things like the port
> number, configuration file name or amount and type of storage.
> Previously, this was done in /etc/default/varnish, but this no longer
> the case. Ugly as hell.

Hi,

Firstly, the best way to change unit files is to copy your unit file to 
the relevant location in /etc/systemd.

This is so system updates don't overwrite your changes.

I tested the default varnish files and everything ran with ps -ef 
showing expected output.



And that's probably as far as my ability to help you goes.


> OK, so I do it that way, then do systemctl daemon-reload, then start
> the unit via systemctl start varnish.
>
> Checking systemctrl status varnish says the daemon started
> successfully. Checking journalctl -xe, and /var/log/syslog all say
> that the daemon is started, but ps -ef shows no such daemon!
>
> No clue as to why Varnish does not start.

Yeah, that *is* weird.  Any luck with it yet?

Please let us (or at least me) know how you resolve this.


Regards,

rb

--