|
HTML rendering created 2026-09-09 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|
|
NAME | SYNOPSIS | DESCRIPTION | RETURN VALUE | NOTES | HISTORY | SEE ALSO | NOTES | COLOPHON |
|
|
|
SD_BUS_A...T_MANAGER(3) sd_bus_add_object_manager SD_BUS_A...T_MANAGER(3)
sd_bus_add_object_manager - Add a D-Bus object manager for a D-Bus
object sub-tree
#include <systemd/sd-bus.h>
int sd_bus_add_object_manager(sd_bus *bus, sd_bus_slot **slot,
const char *path);
sd_bus_add_object_manager() installs a handler for the given path
that implements the GetManagedObjects() method of the
org.freedesktop.DBus.ObjectManager interface. See
org.freedesktop.DBus.ObjectManager[1] for more information.
To implement the InterfacesAdded and InterfacesRemoved signals of
the org.freedesktop.DBus.ObjectManager interface, call
sd_bus_emit_interfaces_added(3) and
sd_bus_emit_interfaces_removed(3) whenever interfaces are added or
removed from the sub-tree, respectively.
When sd_bus_add_object_manager() succeeds, a slot is created
internally. If the output parameter slot is NULL, a "floating"
slot object is created, see sd_bus_slot_set_floating(3).
Otherwise, a pointer to the slot object is returned. In that case,
the reference to the slot object should be dropped when the object
manager is not needed anymore, see sd_bus_slot_unref(3).
On success, sd_bus_add_object_manager() returns a non-negative
integer. On failure, it returns a negative errno-style error code.
Errors
Returned errors may indicate the following problems:
-EINVAL
One of the required parameters is NULL or path is not a valid
object path.
-ENOPKG
The bus cannot be resolved.
-ECHILD
The bus was created in a different process, library or module
instance.
-ENOMEM
Memory allocation failed.
Functions described here are available as a shared library, which
can be compiled against and linked to with the
libsystemd pkg-config(1) file.
All functions listed here are thread-agnostic and only a single
thread may operate on a given object at any given time. Different
threads may access the same object at different times. Multiple
independent objects may be used from different threads in
parallel.
The code described here uses getenv(3), which is declared to be
not multi-thread-safe. This means that the code calling the
functions described here must not call setenv(3) from a parallel
thread. It is recommended to only do calls to setenv() from an
early phase of the program when no other threads have been
started.
sd_bus_add_object_manager() was added in version 221.
sd-bus(3), busctl(1), sd_bus_add_object_vtable(3),
sd_bus_emit_interfaces_added(3), sd_bus_slot_unref(3)
1. org.freedesktop.DBus.ObjectManager
https://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager
This page is part of the systemd (systemd system and service
manager) project. Information about the project can be found at
⟨http://www.freedesktop.org/wiki/Software/systemd⟩. If you have a
bug report for this manual page, see
⟨http://www.freedesktop.org/wiki/Software/systemd/#bugreports⟩.
This page was obtained from the project's upstream Git repository
⟨https://github.com/systemd/systemd.git⟩ on 2026-08-04. (At that
time, the date of the most recent commit that was found in the
repository was 2026-08-03.) If you discover any rendering
problems in this HTML version of the page, or you believe there is
a better or more up-to-date source for the page, or you have
corrections or improvements to the information in this COLOPHON
(which is not part of the original manual page), send a mail to
man-pages@man7.org
systemd 262~devel SD_BUS_A...T_MANAGER(3)
Pages that refer to this page: sd-bus(3), sd_bus_emit_signal(3), systemd.directives(7), systemd.index(7)
|
HTML rendering created 2026-09-09 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|