* kdbus: for some reason "busctl monitor" only shows metadata for signal msgs, never method call or method reply msgs
* add "systemctl start -v foobar.service" that shows logs of a service
* kdbus: for some reason "busctl monitor" only shows metadata for signal msgs, never method call or method reply msgs
* add "systemctl start -v foobar.service" that shows logs of a service
- when kdbus does not take our message without memfds, try again with memfds
- systemd-bus-proxyd needs to enforce good old XML policy
- allow updating attach flags during runtime
- when kdbus does not take our message without memfds, try again with memfds
- systemd-bus-proxyd needs to enforce good old XML policy
- allow updating attach flags during runtime
- introduce sd_bus_emit_object_added()/sd_bus_emit_object_removed() that automatically includes the build-in interfaces in the list
- port to sd-resolve for connecting to TCP dbus servers
- see if we can drop more message validation on the sending side
- introduce sd_bus_emit_object_added()/sd_bus_emit_object_removed() that automatically includes the build-in interfaces in the list
- port to sd-resolve for connecting to TCP dbus servers
- see if we can drop more message validation on the sending side