NAME
sd_bus_message_set_expect_reply, sd_bus_message_get_expect_reply, sd_bus_message_set_auto_start, sd_bus_message_get_auto_start, sd_bus_message_set_allow_interactive_authorization, sd_bus_message_get_allow_interactive_authorization - Set and query bus message metadataSYNOPSIS
#include <systemd/sd-bus.h>
int
sd_bus_message_set_expect_reply(sd_bus_message *message,
int b);
int
sd_bus_message_get_expect_reply(sd_bus_message *message);
int
sd_bus_message_set_auto_start(sd_bus_message *message,
int b);
int
sd_bus_message_get_auto_start(sd_bus_message *message);
int
sd_bus_message_set_allow_interactive_authorization(sd_bus_message *message,
int b);
int
sd_bus_message_get_allow_interactive_authorization(sd_bus_message *message);
DESCRIPTION
sd_bus_message_set_expect_reply() sets or clears the NO_REPLY_EXPECTED flag on the message m. This flag matters only for method call messages and is used to specify that no method return or error reply is expected. It is ignored for other types. Thus, for a method call message, callingsd_bus_message_set_expect_reply(..., 0)
sd_bus_message_set_auto_start(..., 0)
RETURN VALUE
On success, these functions return a non-negative integer. On failure, they return a negative errno-style error code.Errors
Returned errors may indicate the following problems: -EINVALThe message parameter is
NULL.
-EPERM
The message message is sealed when
trying to set a flag.
The message message has wrong type.
NOTES
These APIs are implemented as a shared library, which can be compiled and linked to with the libsystemd pkg-config(1) file.SEE ALSO
systemd(1), sd-bus(3), sd_bus_set_description(3)systemd 252 |