From 19f4f86bfed21c5326ed2acebe1163f3a83e832b Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Mon, 6 May 2024 04:25:50 +0200 Subject: Adding upstream version 241. Signed-off-by: Daniel Baumann --- man/sd_bus_wait.xml | 113 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 113 insertions(+) create mode 100644 man/sd_bus_wait.xml (limited to 'man/sd_bus_wait.xml') diff --git a/man/sd_bus_wait.xml b/man/sd_bus_wait.xml new file mode 100644 index 0000000..e866eeb --- /dev/null +++ b/man/sd_bus_wait.xml @@ -0,0 +1,113 @@ + + + + + + + + + sd_bus_wait + systemd + + + + sd_bus_wait + 3 + + + + sd_bus_wait + + Wait for I/O on a bus connection + + + + + #include <systemd/sd-bus.h> + + + int sd_bus_wait + sd_bus *bus + uint64_t timeout_usec + + + + + + Description + + sd_bus_wait() synchronously waits for I/O on the specified bus connection object. This + function is supposed to be called whenever + sd_bus_process3 returns zero, + indicating that no work is pending on the connection. Internally, this call invokes ppoll3, to wait for I/O on + the bus connection. If the timeout_sec parameter is specified, the call will block at most + for the specified amount of time in µs. Pass UINT64_MAX to permit it to sleep + indefinitely. + + After each invocation of sd_bus_wait() the sd_bus_process() call + should be invoked in order to process any now pending I/O work. + + Note that sd_bus_wait() is suitable only for simple programs as it does not permit + waiting for other I/O events. For more complex programs either connect the bus connection object to an external + event loop using sd_bus_get_fd3 + or to an sd-event3 event loop + using + sd_bus_attach_event3. + + + + Return Value + + If any I/O was seen, a positive value is returned, zero otherwise. If an error occurs, a negative + errno-style error code is returned. + + + + Errors + + Returned errors may indicate the following problems: + + + + -EINVAL + + An invalid bus object was passed. + + + + -ECHILD + + The bus connection was allocated in a parent process and is being reused in a child process + after fork(). + + + + -ENOTCONN + + The bus connection has been terminated already. + + + + + + + + See Also + + + systemd1, + sd-bus3, + sd_bus_process3, + sd_bus_get_fd3, + sd-event3, + sd_bus_attach_event3 + + + + -- cgit v1.2.3