Activation environment(s)?

[Mantas Mikulėnas]

The traditional dbus-daemon keeps a separate environment for services it
spawns directly (i.e. those that don't specify SystemdService= in their
D-Bus .service files), though that it doesn't apply to services it runs via
systemd so you need to keep both in sync.

On the other hand, dbus-broker runs everything via systemd (using transient
service units if necessary), and as far as I know it no longer keeps track
of a separate activation environment and all changes are just directly
forwarded to systemd's environment instead.

It depends on which implementation your distribution uses.


On Mon, Jan 8, 2024, 17:58 Vladimir Kudrya <vladimir-csp at yandex.ru> wrote:

> Hello.
>
> In context of a modern systemd-managed user session, is there a separate
> dbus activation environment, or is it merged with systemd? If one
> intends to manage environment variables, is systemctl (or
> org.freedesktop.systemd1.Manager Environment) enough?
>
> A variable added by dbus-update-activation-environment (even without
> --systemd option) shows up in systemd activation environment. I couldn't
> find a pure dbus service to check if reverse is true.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20240108/0c8ccf49/attachment.htm>