1SD_BUS_REPLY_METHOD_RETURN(s3d)_bus_reply_method_retuSrDn_BUS_REPLY_METHOD_RETURN(3)
2
3
4
6 sd_bus_reply_method_return, sd_bus_reply_method_returnv - Reply to a
7 D-Bus method call
8
10 #include <systemd/sd-bus.h>
11
12 int sd_bus_reply_method_return(sd_bus_message *call, const char *types,
13 ...);
14
15 int sd_bus_reply_method_returnv(sd_bus_message *call,
16 const char *types, va_list ap);
17
19 sd_bus_reply_method_return() sends a reply to the call message. The
20 type string types and the arguments that follow it must adhere to the
21 format described in sd_bus_message_append(3). If no reply is expected
22 to call, this function succeeds without sending a reply.
23
25 On success, this function returns a non-negative integer. On failure,
26 it returns a negative errno-style error code.
27
28 Errors
29 Returned errors may indicate the following problems:
30
31 -EINVAL
32 The input parameter call is NULL.
33
34 Message call is not a method call message.
35
36 Message call is not attached to a bus.
37
38 Message m is not a method reply message.
39
40 -EPERM
41 Message call has been sealed.
42
43 -ENOTCONN
44 The bus to which message call is attached is not connected.
45
46 -ENOMEM
47 Memory allocation failed.
48
49 In addition, any error returned by sd_bus_send(1) may be returned.
50
52 Functions described here are available as a shared library, which can
53 be compiled against and linked to with the libsystemd pkg-config(1)
54 file.
55
56 The code described here uses getenv(3), which is declared to be not
57 multi-thread-safe. This means that the code calling the functions
58 described here must not call setenv(3) from a parallel thread. It is
59 recommended to only do calls to setenv() from an early phase of the
60 program when no other threads have been started.
61
63 systemd(1), sd-bus(3), sd_bus_message_new_method_return(3)
64
65
66
67systemd 254 SD_BUS_REPLY_METHOD_RETURN(3)