summaryrefslogtreecommitdiffstats
path: root/meta-yocto-bsp/recipes-core
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2015-09-08 23:35:04 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-09-09 14:27:46 +0100
commit335260cbfcedc7c348f2e190400efbae67ad92ff (patch)
treed48f9aec1a2b48fc4e3b5b23db95d26d92767b1b /meta-yocto-bsp/recipes-core
parent79bf3f7155e00b96bd205c5bd844cc91ab2e9553 (diff)
downloadpoky-335260cbfcedc7c348f2e190400efbae67ad92ff.tar.gz
qemurunner: Ensure runqemu doesn't survive SIGKILL
Currently, we see runqemu and qemu-system-* processes left behind when bitbake is killed by buildbot. This is due to the use of setpgrp() in the runqemu subprocess call. We need the setpgrp call so that all runqemu processes can easily be killed (by killing their process group). This presents a problem if this controlling process itself is killed however since those processes don't notice the death of the parent and merrily continue on. Rather than hack runqemu to deal with this, we add something to qemurunner, at least for now to resolve the issue. Basically we fork off another process which holds an open pipe to the parent and also is setpgrp. If/when the pipe sees EOF from the parent dieing, it kills the process group. This is like pctrl's PDEATHSIG but for a process group rather than a single process. (From OE-Core rev: 99428eafb5352bd39bc4329bdba07c6d6f17b03f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-yocto-bsp/recipes-core')
0 files changed, 0 insertions, 0 deletions