aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChen Qi <Qi.Chen@windriver.com>2015-01-29 11:31:46 +0800
committerChen Qi <Qi.Chen@windriver.com>2015-01-29 13:29:44 +0800
commitdf11b197377156cf9c8119e94a95fe8691251f89 (patch)
treeb3c2021fd31203963aee5b0cf3608eb531d1dc83
parent2a775ebbb175dd70fc7228607c306d4ccb9e4ba4 (diff)
downloadopenembedded-core-contrib-ChenQi/runqemu-internal-error-message.tar.gz
openembedded-core-contrib-ChenQi/runqemu-internal-error-message.tar.bz2
openembedded-core-contrib-ChenQi/runqemu-internal-error-message.zip
runqemu-internal: get rid of annoying but harmless error messageChenQi/runqemu-internal-error-message
If tap0 interface has been created by other users on the system, we would get error messages when using runqemu. Error messages are like below. Acquiring lockfile for tap0... touch: cannot touch ‘/tmp/qemu-tap-locks/tap0.lock’: Permission denied /buildarea2/chenqi/poky/scripts/runqemu-internal: line 139: /tmp/qemu-tap-locks/tap0.lock: Permission denied flock: 8: Bad file descriptor The system can still boot up because runqemu would try to create a new tap interface. So the error message above is harmless, yet somewhat annoying. This patch fixes the above problem. With this patch, the output would be as follows. Acquiring lockfile for tap0... Acquiring lockfile for /tmp/qemu-tap-locks/tap0.lock failed Setting up tap interface under sudo Acquiring lockfile for tap1... Running qemu-system-arm... Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
-rwxr-xr-xscripts/runqemu-internal6
1 files changed, 5 insertions, 1 deletions
diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal
index 5711bd3802..a0a1e96eb4 100755
--- a/scripts/runqemu-internal
+++ b/scripts/runqemu-internal
@@ -138,7 +138,11 @@ else
return 1
fi
- touch $lockfile.lock
+ touch $lockfile.lock 2>/dev/null
+ if [ $? -ne 0 ]; then
+ echo "Acquiring lockfile for $lockfile.lock failed"
+ return 1
+ fi
exec 8>$lockfile.lock
flock -n -x 8
if [ $? -ne 0 ]; then