diff options
author | Azat Khuzhin <azat@libevent.org> | 2019-08-29 22:57:44 +0300 |
---|---|---|
committer | Azat Khuzhin <azat@libevent.org> | 2019-09-02 22:14:22 +0300 |
commit | ddacaef59ab6808a0801007d0a681f2415af4871 (patch) | |
tree | 8543cc38d3eb9f0d82dcba28935b096fdb3f7165 /event.c | |
parent | b5e1d91154778f076042e9ea73723a21c0ad690b (diff) | |
download | libevent-ddacaef59ab6808a0801007d0a681f2415af4871.tar.gz |
Revert "Warn if forked from the event loop during event_reinit()"
Thinking about this more and realizing that this was a mistake, so
should be reverted.
In a nut shell I guess most of the apps calls event_reinit() from the
loop (see [1] for example), and this should be totally fine (the bit
with the signals [2] handled in event_reinit() gracefully)
[1]: https://archives.seul.org/libevent/users/Aug-2019/msg00009.html
[2]: https://github.com/libevent/libevent/pull/833#issuecomment-501834453
This reverts commit 497ef904d544ac51de43934549dbeccce8e6e8f8.
Reported-by: mikulas@twibright.com
Backport-to: 2.1
Diffstat (limited to 'event.c')
-rw-r--r-- | event.c | 6 |
1 files changed, 0 insertions, 6 deletions
@@ -1003,12 +1003,6 @@ event_reinit(struct event_base *base) EVBASE_ACQUIRE_LOCK(base, th_base_lock); - if (base->running_loop) { - event_warnx("%s: forked from the event_loop.", __func__); - res = -1; - goto done; - } - evsel = base->evsel; /* check if this event mechanism requires reinit on the backend */ |