Subject: Re: [boost] [Boost-users] Brainstorming [WAS: Subject: Formal Review of Proposed Boost.Process library starts tomorrow]
From: Oliver Kowalke (k-oli_at_[hidden])
Date: 2011-02-15 02:12:23
> Arguably then the signal handler could record that the signal was
> delivered rather than actually call waitpid. In any case, waitpid won't
> block, so I expect the signal handler would take on the order of a
> millisecond (this would really have to be tested, though, to know).
>
> Also, the user could still provide a dedicated thread by blocking
> SIGCHLD in every thread but one, without any special support in
> boost.process.
If you call waitpid(-1,...) in aloop inside a signal handler, then you get the pids of the children. What do you do next? Keep in mind that the functions you can call must be obstruction-free/async-safe.
How do you tell the other threads your pid you got from waitpid()?
-- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl