| SD_EVENT_SOURCE_GET_EVENT(3) | sd_event_source_get_event | SD_EVENT_SOURCE_GET_EVENT(3) |
.SH "NAME" sd_event_source_get_event - Retrieve the event loop of
an event source
.SH "SYNOPSIS"
#include <systemd/sd-event.h>
.HP 864u sd_event*
sd_event_source_get_event(sd_event_source *source);
.SH "DESCRIPTION"
.PP sd_event_source_get_event() may be used to retrieve the event loop
object the event source object specified as source is associated
with. The event loop object is specified when creating an event source
object with calls such as sd_event_add_io(3) or
sd_event_add_time(3).
.SH "RETURN VALUE"
.PP On success, sd_event_source_get_event() returns the associated
event loop object. On failure, it returns NULL.
.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_event_source_get_event() was added in version 229.
.SH "SEE ALSO"
.PP sd-event(3), sd_event_add_io(3),
sd_event_add_time(3), sd_event_add_signal(3),
sd_event_add_child(3), sd_event_add_inotify(3),
sd_event_add_defer(3), sd_event_source_set_userdata(3)
| systemd 262.2 |