sd_event_source_get_pending — Determine pending state of event sources
sd_event_source_get_pending() may be
used to determine whether the event source object specified as
source has seen events but has not been
dispatched yet (and thus is marked "pending").
Event source objects initially are not marked pending, when they are created with calls such as sd_event_add_io(3), sd_event_add_time(3), with the exception of those created with sd_event_add_defer(3) which are immediately marked pending, and sd_event_add_exit(3) for which the "pending" concept is not defined. For details see the respective manual pages.
In each event loop iteration one event source of those marked pending is dispatched, in the order defined by the event source priority, as set with sd_event_source_set_priority(3).
sd_event_source_get_pending() returns an integer greater than zero
when the event source is marked pending, and zero when the event source is not marked pending. On
failure, it returns a negative errno-style error code.
Returned errors may indicate the following problems:
source is not a valid pointer to an
source refers to an event source object created with
Not enough memory.
The event loop is already terminated.
The event loop has been created in a different process, library or module instance.
Functions described here are available as a shared
library, which can be compiled against and linked to with the
The code described here uses
which is declared to be not multi-thread-safe. This means that the code calling the functions described
here must not call
from a parallel thread. It is recommended to only do calls to
from an early phase of the program when no other threads have been started.
sd_event_source_get_pending() was added in version 229.