On Sun, 13 Aug 2023 19:10:32 +0200
Tobias Nygren wrote:
> A similar situation arises with daemons that reload their configuration
> via the classic SIGHUP + fork(2) mechanism. If that is done from within
> the event loop I guess we lose?
Same goes of course for any trivial server process that
On Sat, 12 Aug 2023 19:21:06 -0400
Christos Zoulas wrote:
> I really want to understand what's going on here (why do we think that
> our epoll implementation is broken in a way that will affect applications).
jperkin@ might be able to explain what the issues with Illumos are,
but I guess the
> Date: Sun, 13 Aug 2023 13:03:09 +0200
> From: Rhialto
>
> On Sat 12 Aug 2023 at 11:58:36 +, Taylor R Campbell wrote:
> > Cons:
> > - POSIX doesn't ask system(3) to work when SIGCHLD is set to SIG_IGN
> > or when it has SA_NOCLDWAIT set, so this code is nonportable anyway;
>
> I read
On Sat 12 Aug 2023 at 11:58:36 +, Taylor R Campbell wrote:
> Cons:
> - POSIX doesn't ask system(3) to work when SIGCHLD is set to SIG_IGN
> or when it has SA_NOCLDWAIT set, so this code is nonportable anyway;
I read through
https://pubs.opengroup.org/onlinepubs/007908799/xsh/system.html and
> Date: Sat, 12 Aug 2023 19:21:06 -0400
> From: Christos Zoulas
>
> 2. Nobody has given an example of an application that breaks, or answered
> the question if we understand how the Illumos feature is breaking things,
> or even if the Illumos implementation is similar to ours. Theodore
> Date: Sat, 12 Aug 2023 22:48:05 -0400 (EDT)
> From: Mouse
>
> > If the calling process has SA_NOCLDWAIT set or has SIGCHLD set to
> > SIG_IGN, [...]
>
> Check my understanding: this applies to wait(2), but not alternatives
> like waitpid(2) or wait4(2), right?
If you read all the way
