diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-09-07 15:48:16 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-09-09 14:27:55 +0100 |
commit | 384533bdb47af2c3a0f3faea8879e8f3cb6f39f9 (patch) | |
tree | ec9edbe679a9b1d6988e9a42e599b3209b5e7414 /bitbake/lib/bb/utils.py | |
parent | dae69e6dcfa177844bb41a156b1bab091db3f1e7 (diff) | |
download | poky-384533bdb47af2c3a0f3faea8879e8f3cb6f39f9.tar.gz |
bitbake: server/process: Handle SIGTERM more gracefully
Currently if you send a SIGTERM to the bitbake UI process, the system basically
hangs if tasks are executing. This is because the server process doesn't
actually try any kind of shutdown before exiting.
This patch trys executing a stateForceShutdown command first, which is
enough to stop any active tasks before the system exits.
I also noticed that terminate can execute multiple times, once at SIGTERM
from the handler and once from the real exit. Double execution leads to
stack traces and potential hangs (writes to dead pipes), so ensure
the code only can run once.
With these fixes, bitbake much more correctly deals with SIGTERM to the
UI process.
(Bitbake rev: 1032ddddbe3241da02ebb3608a1c40f9123b9e80)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/utils.py')
0 files changed, 0 insertions, 0 deletions