Scroll to navigation



sd_bus_message_set_expect_reply, sd_bus_message_get_expect_reply, sd_bus_message_set_auto_start, sd_bus_message_get_auto_start - Set and query bus message metadata


#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);


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, calling

sd_bus_message_set_expect_reply(..., 0)

sets the flag and suppresses the reply.

sd_bus_message_get_expect_reply() checks if the NO_REPLY_EXPECTED flag is set on the message m. It will return positive if it is not set, and zero if it is.

sd_bus_message_set_auto_start() sets or clears the NO_AUTO_START flag on the message m. When the flag is set the bus must not launch an owner for the destination name in response to this message. Calling

sd_bus_message_set_auto_start(..., 0)

sets the flag.

sd_bus_message_get_auto_start() checks if the NO_AUTO_START flag is set on the message m. It will return positive if it is not set, and zero if it is.


On success, these functions return 0 or a positive integer. On failure, they return a negative errno-style error code.


Returned errors may indicate the following problems:


The message parameter is NULL.


The message message is sealed when trying to set a flag.

The message message has wrong type.


These APIs are implemented as a shared library, which can be compiled and linked to with the libsystemd pkg-config(1) file.


systemd(1), sd-bus(3), sd_bus_set_description(3)
systemd 241