diff options
| author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-11-28 17:31:39 +0000 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-12-16 14:31:32 +0000 |
| commit | b9943e4bfe96e3e1242643014cba915924222fa4 (patch) | |
| tree | 09f5b74cf5137228ed47d018ab609018e053e6a4 /meta/lib/oeqa/selftest/cases/signing.py | |
| parent | 7ad6069850af97a63397007069d146b0ff5cc14d (diff) | |
| download | poky-b9943e4bfe96e3e1242643014cba915924222fa4.tar.gz | |
scripts/runqemu: Improve lockfile handling for python with close_fd=True
On python versions with close_fds=True (python 3.2 onwards), the tap
device lockfile isn't passed to the child process.
Since this guards against use of an active interface, we really want this
here, so pass it in pass_fds. This means if the parent exits early, the child
still holds the lock, avoiding messages like:
runqemu - ERROR - Failed to run qemu: qemu-system-x86_64: could not configure /dev/net/tun (tap0): Device or resource busy
(From OE-Core rev: 17a0a067d597c445c5892ff9914e91a2187f7e09)
(From OE-Core rev: 1d03e0d54863124c5a65b59ecdc76dbac13d312a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/lib/oeqa/selftest/cases/signing.py')
0 files changed, 0 insertions, 0 deletions