| SD_BUS_PENDING_METHOD_CALLS(3) | sd_bus_pending_method_calls | SD_BUS_PENDING_METHOD_CALLS(3) |
.SH "NAME" sd_bus_pending_method_calls - Return the number of
currently pending, outgoing method calls
.SH "SYNOPSIS"
#include <systemd/sd-bus.h>
.HP 768u int
sd_bus_pending_method_calls(sd_bus *bus);
.SH "DESCRIPTION"
.PP sd_bus_pending_method_calls() returns the number of currently
pending outgoing method calls, i.e. method calls enqueued with
sd_bus_call_async(3) for which no reply has been received yet, and
which have not reached a timeout yet.
.PP The bus argument may be NULL, in which case zero is
returned.
.SH "RETURN VALUE"
.PP This function returns 0 if there are no pending method calls, or a
NULL bus object was specified. On failure, a negative errno-style
error code is returned.
.SS "Errors"
.PP Returned errors may indicate the following problems:
.PP -ECHILD
The bus connection has been created in a different process, library or module
instance.
.RE
.SH "NOTES"
.PP Functions described here are available as a shared library, which can be
compiled against and linked to with the
libsystemd pkg-config(1) file.
.PP All functions listed here are thread-agnostic and only a single thread
may operate on a given object at any given time. Different threads may
access the same object at different times. Multiple independent objects may
be used from different threads in parallel.
.PP The code described here uses getenv(3), which is declared to be
not multi-thread-safe. This means that the code calling the functions
described here must not call setenv(3) from a parallel thread. It is
recommended to only do calls to setenv() from an early phase of the
program when no other threads have been started.
.SH "HISTORY"
.PP sd_bus_pending_method_calls() was added in version 257.
.SH "SEE ALSO"
.PP systemd(1), sd-bus(3), sd_bus_call_async(3)
| systemd 262.2 |