HTML rendering created 2025-09-06 byMichael Kerrisk, author ofThe Linux Programming Interface. For details of in-depthLinux/UNIX system programming training courses that I teach, lookhere. Hosting byjambit GmbH. |  |
NAME |SYNOPSIS |DESCRIPTION |RETURN VALUE |NOTES |HISTORY |SEE ALSO |COLOPHON | |
SD_BUS...T_REPLY(3) sd_bus_message_set_expect_replySD_BUS...T_REPLY(3)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 metadata
#include <systemd/sd-bus.h>int sd_bus_message_set_expect_reply(sd_bus_message *message,intb);int sd_bus_message_get_expect_reply(sd_bus_message *message);int sd_bus_message_set_auto_start(sd_bus_message *message, intb);int sd_bus_message_get_auto_start(sd_bus_message *message);intsd_bus_message_set_allow_interactive_authorization(sd_bus_message *message,intb);intsd_bus_message_get_allow_interactive_authorization(sd_bus_message *message);
sd_bus_message_set_expect_reply()sets or clears theNO_REPLY_EXPECTEDflag on the messagem. 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 theNO_REPLY_EXPECTED flag is set on the messagem. It will return positive if it is not set, and zero if it is.sd_bus_message_set_auto_start()sets or clears theNO_AUTO_START flag on the messagem. 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 theNO_AUTO_STARTflag is set on the messagem. It will return positive if it is not set, and zero if it is.sd_bus_message_set_allow_interactive_authorization()sets or clears theALLOW_INTERACTIVE_AUTHORIZATIONflag on the messagem. Setting this flag informs the receiver that the caller is prepared to wait for interactive authorization via polkit or a similar framework. Note that setting this flag does not guarantee that the receiver will actually perform interactive authorization. Also, make sure to set a suitable message timeout when using this flag since interactive authorization could potentially take a long time as it depends on user input. Ifb is non-zero, the flag is set.sd_bus_message_get_allow_interactive_authorization()checks if theALLOW_INTERACTIVE_AUTHORIZATIONflag is set on the messagem. It will return a positive integer if the flag is set. Otherwise, it returns zero.
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:-EINVAL Themessage parameter isNULL.-EPERM The messagemessage is sealed when trying to set a flag. The messagemessage has wrong type.
Functions described here are available as a shared library, which can be compiled against and linked to with thelibsystemd pkg-config(1) file. The code described here usesgetenv(3), which is declared to be not multi-thread-safe. This means that the code calling the functions described here must not callsetenv(3) from a parallel thread. It is recommended to only do calls tosetenv()from an early phase of the program when no other threads have been started.
sd_bus_message_set_expect_reply(),sd_bus_message_get_expect_reply(),sd_bus_message_set_auto_start(), andsd_bus_message_get_auto_start()were added in version 240.sd_bus_message_set_allow_interactive_authorization()andsd_bus_message_get_allow_interactive_authorization()were added in version 246.
systemd(1),sd-bus(3),sd_bus_set_description(3)
This page is part of thesystemd (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 2025-08-11. (At that time, the date of the most recent commit that was found in the repository was 2025-08-11.) 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 isnot part of the original manual page), send a mail to man-pages@man7.orgsystemd 258~rc2SD_BUS...T_REPLY(3)Pages that refer to this page:sd-bus(3), sd-bus-errors(3), sd_bus_message_new(3), systemd.directives(7), systemd.index(7)
HTML rendering created 2025-09-06 byMichael Kerrisk, author ofThe Linux Programming Interface. For details of in-depthLinux/UNIX system programming training courses that I teach, lookhere. Hosting byjambit GmbH. | |