AM NOW DEBUGGING SYSTEMD, AND HAVING TO LEARN THE INTERNALS.

ALL OF THE RAGE

not kidding, we fixed it with:

EnvironmentFile=-/etc/default/varnish
ExecStart=/bin/bash -c "/bin/echo ${DAEMON_OPTS} && /usr/sbin/varnishd ${DAEMON_OPTS}"

Because otherwise systemd would randomly eat parts of ${DAEMON_OPTS}. oh yes, we *also* had to make DAEMON_OPTS a single line, because *something* didn't like '\' continuation chars.

systemd is the worst software I've ever had to use, and I've used AIX, HP-UX, Solaris, and 16-bit Windows Payroll software.

@phessler being worse than HP-UX is a truly Herculean task: I have nightmares made of setting up HP workstations in the 1990s…

It truly sounds like systemd is not only reinventing the wheel but building a whole car in the wheel including all previous mistakes.

@cynicalsecurity I think part of what made it worse than HP-UX is the importance of the machines involved.

HP-UX was a build/test machine that handled one or two small customers.

The varnish+systemd machine[1] is for our CDN, which a few very important customers use.

[1] the rest of the cluster will be upgraded, but only *much* later once we get all of the bugs fixed.

@phessler I can sense the dread in your toots… systemd is bad enough as-is, if you come from a BSD and/or true Unix background it becomes unbearable.

I use Kali for work, see the errors scroll past at boot and beg that they are never fatal… I wish there was a BSD-based Kali to be honest.

@cynicalsecurity I've spent more time fighting this one systemd, than it could ever save across our entire fleet of machines.

and yea, I regret pretty much every time I have to use linux or "linux-tools". so many easy-to-fix bugs.

*weeps for the future*