about summary refs log tree commit homepage
path: root/xt
diff options
context:
space:
mode:
authorEric Wong <e@80x24.org>2023-09-15 10:11:57 +0000
committerEric Wong <e@80x24.org>2023-09-15 17:02:41 +0000
commite281363ba93763a7bc4be41ad814cd972d1775f9 (patch)
treee8d4b4d21929721747d6ed8718f57741fe294ebe /xt
parent759885e60e59b5cdcb13c0174e6f6b4a147787f9 (diff)
downloadpublic-inbox-e281363ba93763a7bc4be41ad814cd972d1775f9.tar.gz
The fundamental difference which I originally missed when
implementing kqueue EVFILT_SIGNAL support is that it does not
consume signals like signalfd(2) does.  In other words, with
EVFILT_SIGNAL, it's possible for a single signal to be delivered
twice if we unblock signals upon leaving the event loop as we do
in lei.

Note: Our DS->event_loop and Sigfd APIs can/should probably be
changed to better accomodate EVFILT_SIGNAL differences from
signalfd without sacrificing usability of either.

This fixes the problem of leftover lei-ovv.dst*, lei_cfg-* and
skv.* files in $TMPDIR at the end of test suite runs on *BSD
when IO::KQueue is installed.
Diffstat (limited to 'xt')
0 files changed, 0 insertions, 0 deletions