Re: [systemd-devel] Activation environment(s)?

2024-01-15 Thread Vladimir Kudrya
At least signals seem to be sent only only once. A process in a login shell can wait for TERM (and two HUPs if on console), wait a bit after this, then safely fork cleanup tasks and exit before KILL comes. On 15/01/2024 13.08, Lennart Poettering wrote: When the goal is to shut down a

Re: [systemd-devel] Activation environment(s)?

2024-01-15 Thread Lennart Poettering
On Fr, 12.01.24 18:16, Vladimir Kudrya (vladimir-...@yandex.ru) wrote: > On 08/01/2024 22.26, Simon McVittie wrote: > > It is not possible to unset a variable in the dbus-daemon's activation > > environment, or with `dbus-update-activation-environment`: that's an > > API limitation in the

Re: [systemd-devel] Activation environment(s)?

2024-01-12 Thread Vladimir Kudrya
On 08/01/2024 22.26, Simon McVittie wrote: It is not possible to unset a variable in the dbus-daemon's activation environment, or with `dbus-update-activation-environment`: that's an API limitation in the org.freedesktop.DBus interface. I've thought about adding an