Hmm, maybe I'll chuck:
X-Listen-Port
X-Listen-Name
On all the generated SystemD units.
Okay, will rewrite to use .socket files. Is there a trick to overcoming the
PATH issue which avoids launching bash?
On Tue, May 2, 2017 at 10:11 PM, Lennart Poettering
wrote:
> On Mon, 01.05.17 13:
Wrote some scripts to generate systemd .service files and start-up those
services.
Currently just for some REST APIs, but soon will include distributed
systems also.
I set the TCP listen port variable that is used by my .service like so:
`Environment=PORT=4200`
To get PATH to work nicely, my `Ex
