Re: [systemd-devel] Antw: [EXT] Re: Accpetance of Environment Variables in Attributes

2020-06-26 Thread Reindl Harald
Am 26.06.20 um 15:03 schrieb Colin Guthrie: > Ulrich Windl wrote on 26/06/2020 10:43: > Roman Odaisky schrieb am 25.06.2020 um 14:35 in >> Nachricht >> <2175_1593088566_5EF49A35_2175_217_1_5367023.DvuYhMxLoT@xps>: [Service] User=nobody >>> >>> May I interject that DynamicUser=yes

Re: [systemd-devel] How to disable seccomp in systemd-nspawn?

2020-06-26 Thread Lennart Poettering
On Fr, 26.06.20 21:43, Mohan R (mohan...@gmail.com) wrote: > Hi > > On Fri, Jun 26, 2020 at 9:23 PM Lennart Poettering > wrote: > > You might need a newer libseccomp so that the syscall is actually > > known by it. openat2 is a very recent syscall addition, and you need > > to update libseccomp

Re: [systemd-devel] How to disable seccomp in systemd-nspawn?

2020-06-26 Thread Mohan R
Hi On Fri, Jun 26, 2020 at 9:23 PM Lennart Poettering wrote: > You might need a newer libseccomp so that the syscall is actually > known by it. openat2 is a very recent syscall addition, and you need > to update libseccomp in lockstep if you want it to grok it. Thanks for the details, I'll look

Re: [systemd-devel] How to disable seccomp in systemd-nspawn?

2020-06-26 Thread Lennart Poettering
On Do, 25.06.20 20:19, Mohan R (mohan...@gmail.com) wrote: > Hi > > On Thu, Jun 25, 2020 at 2:17 PM Lennart Poettering > wrote: > > You can't disable seccomp right now. > > Any future plan to include a flag or some other way? > > > We implement a system call allow list, i.e. everything that

Re: [systemd-devel] Antw: [EXT] Re: Accpetance of Environment Variables in Attributes

2020-06-26 Thread Lennart Poettering
On Fr, 26.06.20 14:03, Colin Guthrie (gm...@colin.guthr.ie) wrote: > Ulrich Windl wrote on 26/06/2020 10:43: > Roman Odaisky schrieb am 25.06.2020 um 14:35 in > > Nachricht > > <2175_1593088566_5EF49A35_2175_217_1_5367023.DvuYhMxLoT@xps>: > >>> [Service] > >>> User=nobody > >> > >> May I

Re: [systemd-devel] Accpetance of Environment Variables in Attributes

2020-06-26 Thread Lennart Poettering
On Do, 25.06.20 22:04, Ede Wolf (lis...@nebelschwaden.de) wrote: > > > what exactly stands in your way to use > > ExtecStart=/usr/local/bin/myscript.sh? > > > Because my question was about making a template unit file more dynamic, not > the process called by the unit. > > Having an

Re: [systemd-devel] Antw: [EXT] Re: Accpetance of Environment Variables in Attributes

2020-06-26 Thread Lennart Poettering
On Fr, 26.06.20 11:40, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote: > > I am not sure what made you think this works, but systemd has no > > concept of env var expansion in unit files. It's not a shell. > > But is there actually a good reason not to allow it? We don't want to be a

Re: [systemd-devel] Accpetance of Environment Variables in Attributes

2020-06-26 Thread Lennart Poettering
On Do, 25.06.20 20:25, Ede Wolf (lis...@nebelschwaden.de) wrote: > Does work, so %i works, $SOMETHING not. Different naming, different way of > invocation, I am aware of that, but in general it still the usage of > variables. And the likes of %H, %m or %v are some form of environment, > aren't

Re: [systemd-devel] Antw: [EXT] Re: Accpetance of Environment Variables in Attributes

2020-06-26 Thread Colin Guthrie
Ulrich Windl wrote on 26/06/2020 10:43: Roman Odaisky schrieb am 25.06.2020 um 14:35 in > Nachricht > <2175_1593088566_5EF49A35_2175_217_1_5367023.DvuYhMxLoT@xps>: >>> [Service] >>> User=nobody >> >> May I interject that DynamicUser=yes is generally superior to User=nobody. > > And I

Re: [systemd-devel] Accpetance of Environment Variables in Attributes

2020-06-26 Thread Kevin P. Fleming
On Fri, Jun 26, 2020 at 3:39 AM Ede Wolf wrote: > > > I do this today using a drop-in, because environment variables can be > > set there as well. It works very well, exactly as you describe. There > > is a template service unit file, and a drop-in directory for each > > instance which contains a

[systemd-devel] Antw: [EXT] Re: Accpetance of Environment Variables in Attributes

2020-06-26 Thread Ulrich Windl
>>> Roman Odaisky schrieb am 25.06.2020 um 14:35 in Nachricht <2175_1593088566_5EF49A35_2175_217_1_5367023.DvuYhMxLoT@xps>: >> [Service] >> User=nobody > > May I interject that DynamicUser=yes is generally superior to User=nobody. And I always thought the user is named nobody, because no

[systemd-devel] Antw: [EXT] Re: Accpetance of Environment Variables in Attributes

2020-06-26 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 25.06.2020 um 13:33 in Nachricht <25312_1593084828_5EF48B9C_25312_52_1_20200625113339.GA160936@gardel-login>: > On Do, 25.06.20 13:24, Ede Wolf (lis...@nebelschwaden.de) wrote: > >> So I have an environmentfile containing two variable definitions: >> >>

Re: [systemd-devel] Accpetance of Environment Variables in Attributes

2020-06-26 Thread Ede Wolf
I do this today using a drop-in, because environment variables can be set there as well. It works very well, exactly as you describe. There is a template service unit file, and a drop-in directory for each instance which contains a file that sets the environment variables and also provides values