On 16/07/2024 19:03, Greg Wooledge wrote:
On Tue, Jul 16, 2024 at 18:42:40 +0700, Max Nikulin wrote:On 16/07/2024 10:39, Greg Wooledge wrote:hobbit:~/.config$ cat systemd/user/xterm.serviceI am a bit afraid that corner cases might exist because there are no .service files for applications started from menus and runnersWell, I don't have "menus and runners". I had to create *something* I could use for testing, and that's what I came up with.
Running from a menu or a runner is similar to
systemd-run --user --scope --slice app.slice -- xterm
Accordingly to systemd-run(1), --scope causes environment inheritance
from starting process despite new process is moved to another branch of
cgroup tree.
However │ │ │ ├─plasma-krunner.service (#8046) │ │ │ │ └─2533 /usr/bin/krunner and │ │ │ ├─plasma-plasmashell.service (#7073) │ │ │ │ └─2027 /usr/bin/plasmashell --no-respawnthat are parents in "ps xwf" process tree for runner and menu cases accordingly are *services* and it explains why service.d overrides apply.
Greg, do you have an example when Environment= in service.d works, but an environment.d file does not?
P.S. There is <https://wiki.debian.org/Debate/umask> from 2013 briefly discussing 022 vs. 002 values.