HenrikB added the comment:
Thank you both for the comments and suggests. Before I'm getting to the
"interesting" part, first to the "easy" one:
>> What is also useful to know, is that I'm observing this on a legacy RHEL 6
>> system *with a custom
HenrikB added the comment:
Thanks for taking your time on this one.
I'll report back if I find out more about this kernel-specific issue.
Here're my replies to the outstanding questions/comments:
>> where the *child* process (`self.pid == 0`) get stuck while calling
>&