|
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 | SEE ALSO | COLOPHON |
|
|
|
SD_BUS_R...D_RETURN(3) sd_bus_reply_method_return SD_BUS_R...D_RETURN(3)
sd_bus_reply_method_return, sd_bus_reply_method_returnv - Reply to
a D-Bus method call
#include <systemd/sd-bus.h>
int sd_bus_reply_method_return(sd_bus_message *call,
const char *types, ...);
int sd_bus_reply_method_returnv(sd_bus_message *call,
const char *types, va_list ap);
sd_bus_reply_method_return() sends a reply to the call message.
The type string types and the arguments that follow it must adhere
to the format described in sd_bus_message_append(3). If no reply
is expected to call, this function succeeds without sending a
reply.
On success, this function returns a non-negative integer. On
failure, it returns a negative errno-style error code.
Errors
Returned errors may indicate the following problems:
-EINVAL
The input parameter call is NULL.
Message call is not a method call message.
Message call is not attached to a bus.
Message m is not a method reply message.
Added in version 246.
-EPERM
Message call has been sealed.
Added in version 246.
-ENOTCONN
The bus to which message call is attached is not connected.
Added in version 246.
-ENOMEM
Memory allocation failed.
Added in version 246.
In addition, any error returned by sd_bus_send(3) may be returned.
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.
systemd(1), sd-bus(3), sd_bus_message_new_method_return(3)
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_R...D_RETURN(3)
Pages that refer to this page: sd-bus(3), sd_bus_add_object(3), sd_bus_send(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. |
|