On Di, 26.09.17 21:07, Matthew Giassa ([email protected]) wrote:
> Additionally, does systemd support assigning an environment variable to an
> internal variable, ie:
>
> Environment=MYPIDFILE=/var/run/mine.pid
> PIDFILE=$MYPIDFILE
systemd unit files are not supposed to be a templating engine.
On Di, 26.09.17 16:15, [email protected] ([email protected]) wrote:
> I have a project where I'm adding some services to a Raspberry Pi 3,
> and have decided to go with systemd being (mostly) responsible for
> launching all of the services. All of the server processes use a common
> API to do
emd without wrapping systemctl.
Thank you for the feedback.
Sent from my BlackBerry 10 smartphone on the Bell network.
Original Message
From: Lennart Poettering
Sent: Wednesday, September 27, 2017 9:54 AM
To: [email protected]
Cc: [email protected]
Subject: Re: [systemd-d
* Matthew Giassa [2017-09-26 21:07:16 -0700]:
I know there are workarounds for ExecStart for example, using /bin/bash to
evaluate environment variables, but I think that special case only applies to
ExecStart, ExecStartPre, and Executor, as they actually get executed rather
than just assigne
Additionally, does systemd support assigning an environment variable to an
internal variable, ie:
Environment=MYPIDFILE=/var/run/mine.pid
PIDFILE=$MYPIDFILE
I know there are workarounds for ExecStart for example, using /bin/bash to
evaluate environment variables, but I think that special case o
I have a project where I'm adding some services to a Raspberry Pi 3,
and have decided to go with systemd being (mostly) responsible for
launching all of the services. All of the server processes use a common
API to do some initial setup (argument parsing, init, etc), drop root
permissions, and t
