diff options
| author | Lennart Poettering <lennart@poettering.net> | 2013-12-27 01:00:51 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2013-12-27 01:00:51 +0100 |
| commit | 9129246ba5ae990025347b3d5ab7d5178d968ee1 (patch) | |
| tree | 4917bed94f5a706312a73659ca2dd63e099d7880 | |
| parent | 2e2ec0eaa6d81ffd793c0071150cd57637410fbd (diff) | |
bus: explain obsoletion of dbus1 .service files
| -rw-r--r-- | src/libsystemd-bus/PORTING-DBUS1 | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/src/libsystemd-bus/PORTING-DBUS1 b/src/libsystemd-bus/PORTING-DBUS1 index 0f0ab6e904..9300137236 100644 --- a/src/libsystemd-bus/PORTING-DBUS1 +++ b/src/libsystemd-bus/PORTING-DBUS1 @@ -527,6 +527,21 @@ following the XDG basedir spec. Of course the $DBUS_SYSTEM_BUS_ADDRESS and $DBUS_SESSION_BUS_ADDRESS variables should still take precedence. +DBUS SERVICE FILES + +Activatable services for kdbus may not use classic dbus1 service +activation files. Instead, programs should drop in native systemd +.service and .busname unit files, so that they are treated uniformly +with other types of units and activation of the system. + +Note that this results in a major difference to classic dbus1: +activatable bus names can be established at any time in the boot. This +is unlike dbus1 where activatable names are unconditionally available +as long as dbus-daemon is running. Being able to control when +activatable names are established is essential to allow usage of kdbus +during early boot and in initrds, without the risk of triggering +services too early. + DISCLAIMER This all is just the status quo. We are putting this together, because |