X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsd_event_new.xml;h=35e58ea755e480cb8a9b1dabad4850a3f0c04794;hp=1fe18202b6de58d31515a51c6dd4812b1b64ad36;hb=51cb9d734a182c4892a6b31f58d75489a2ca432b;hpb=faae655de3cdbed4be1d472b01ce0c4d81e905ed diff --git a/man/sd_event_new.xml b/man/sd_event_new.xml index 1fe18202b..35e58ea75 100644 --- a/man/sd_event_new.xml +++ b/man/sd_event_new.xml @@ -83,24 +83,24 @@ along with systemd; If not, see . sd_event_new() allocates a new event loop object. The event loop object is returned in the - event parameter. After use drop + event parameter. After use, drop the returned reference with sd_event_unref(). When the last reference is - dropped the event loop is freed. + dropped, the event loop is freed. sd_event_default() acquires a reference to the default event loop object of the calling thread, possibly allocating a new object if no default event loop object has been - allocated yet for the thread. After use drop the returned - referened with sd_event_unref(). When the - last reference is dropped the event loop is freed. If this + allocated yet for the thread. After use, drop the returned + reference with sd_event_unref(). When the + last reference is dropped, the event loop is freed. If this function is called while the object returned from a previous call from the same thread is still referenced, the same object is returned again, but the reference is increased by one. It is recommended to use this call instead of sd_event_new() in order to share event loop objects between various components that are dispatched in the same - thread. All threads either have no or one default event loops + thread. All threads either have exactly zero or one default event loop associated, but never more. sd_event_ref() increases the reference @@ -108,13 +108,13 @@ along with systemd; If not, see . sd_event_unref() decreases the reference counter of the specified event loop object by one. If - the counter hits zero the event loop object is freed. Not that it - is freed regardless if it is the default event loop object of a + the counter hits zero, the event loop object is freed. Note that it + is freed regardless of whether it is the default event loop object for a thread or not. This means that allocating an event loop with - sd_event_default(), then releasing it and + sd_event_default(), then releasing it, and then acquiring a new one with sd_event_default() will result in two - distinct objects. Note that in order to free an event loop object + distinct objects. Note that, in order to free an event loop object, all remaining event sources of the event loop also need to be freed as they each keep a reference to it.