On Di, 26.09.17 21:07, Matthew Giassa (matt...@giassa.net) 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, matt...@giassa.net (matt...@giassa.net) 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
I've been considering the dbus API, as I arrived at a similar conclusion while
researching this last night. The downside is that, since some services are
provided to me in binary form only, I can't deploy it across all daemons.
In short, I'd be happy with just being able to send SIGTERM and SIG
On Mon, Sep 25, 2017 at 2:47 PM, Mantas Mikulėnas wrote:
> On Mon, Sep 25, 2017 at 8:59 AM, Xin Long wrote:
>>
>> Hi,
>>
>> linux network is using
>> systemctl start teamd@team0.service
>> to start a teamd service, which will call teamd.
>>
>> I got a teamd issue to debug, I wanted generate cor
* 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
On Mi, 27.09.17 01:36, Kai Krakow (hurikha...@gmail.com) wrote:
> Am Mon, 25 Sep 2017 10:26:48 +0200
> schrieb Miroslav Suchý :
>
> > Dne 25.9.2017 v 08:47 Mantas Mikulėnas napsal(a):
> > > But when I start the deamon by "teamd" directly, I could get core
> > > file. When I start it by systemctl
