applied: [PATCH pmg-api 1/3] pmgpolicy: fix failing run_command in children

[Stoiko Ivanov <s.ivanov@proxmox.com>]

Thanks for the analysis and digging into this so quickly!

I gave it a spin on a reproducer of the issue (first only with your 1/3
and then additionally with your 2/3 applied) and it fixes the issue.

decided to apply both patches after looking through the commit-history of
pmgpolicy, and checking Net::Servers changes from a git-repository on
github [0] - it seems that the handling of SIGPIPE and SIGCHLD was added
at some point 2005 286cd15 ("fix signal handling"), while our
copy of run_child might have been copied off before that.
In any case it does not look like it was a deliberate decision to
keep the SIGCHLD handler from the parent.

I dropped the 3/3 that got sent by mistake.

[0]  https://github.com/rhandom/perl-net-server.git

On Wed, 10 Jun 2026 13:35:44 +0200, Dominik Csapak wrote:
> Net::Server::PreForkSimple installs a handler for that in the parent
> which reaps all children automatically with `waitpid(-1, ...)` and this
> gets copied over on fork. Normally, the default `run_child` method sets
> this back to the default, but in pmgpolicy that is overwritten and not
> all signal handlers are set correctly.
> 
> This handler with its waitpid will be called before the one in
> `run_command` which results in an error there.
> 
> [...]

Applied, thanks!

[1/3] pmgpolicy: fix failing run_command in children
      commit: 66d7976b9c73aacd94d0f66d5a28302a985cc5e5
[2/3] pmgpolicy: mimic Net::Server::PreForkSimple's signal handlers in child
      commit: c3b01e45d841e66779698fb03866fe5d397b56f3