diff options
| author | Jiajun Xu <jiajun.xu@intel.com> | 2010-09-01 23:38:53 +0800 |
|---|---|---|
| committer | Richard Purdie <rpurdie@linux.intel.com> | 2010-09-02 11:00:08 +0100 |
| commit | 80993c4e1b9aa68651a026dd7416ba3d5e96c50c (patch) | |
| tree | 13af9707a9ae68fcd358e2cf36ad7b9f2d985f65 /scripts/qemuimage-tests/sanity/boot | |
| parent | 4b611b66743a5ec220aef34d796af63029bb5fd9 (diff) | |
| download | openembedded-core-80993c4e1b9aa68651a026dd7416ba3d5e96c50c.tar.gz openembedded-core-80993c4e1b9aa68651a026dd7416ba3d5e96c50c.tar.bz2 openembedded-core-80993c4e1b9aa68651a026dd7416ba3d5e96c50c.tar.xz openembedded-core-80993c4e1b9aa68651a026dd7416ba3d5e96c50c.zip | |
qemuimage-testlib: kill qemu process according to its pid, instead of process name
poky-qemu-internal will set up a tap lockfile when creating tap device. The lockfile
will be released when a TERM signal is received. In previous code, function
Test_Kill_Qemu uses pkill to kill all process named "qemu". This may cause lockfile
release function not work in poky-qemu-internal. Then poky-qemu-internal will be
hang when user start QEMU the second time. To prevent the issue, the new function
Test_Kill_Qemu kills all child pid with a given parent process ID.
Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
Diffstat (limited to 'scripts/qemuimage-tests/sanity/boot')
0 files changed, 0 insertions, 0 deletions