From 6b4aedc0c9bff86f868886fd86f3ae8f715ae765 Mon Sep 17 00:00:00 2001 From: Alexandru DAMIAN Date: Fri, 7 Mar 2014 15:10:50 +0000 Subject: bitbake: toaster: erase checks for stop command We remove the checks for the stop command, since we assume the user really means it wants to shutdown the system when he issues the command. [YOCTO #5376] (Bitbake rev: 5d6594de8876be8ce4df56b846fee0fc687a6261) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie --- bitbake/bin/toaster | 17 ++--------------- 1 file changed, 2 insertions(+), 15 deletions(-) (limited to 'bitbake/bin') diff --git a/bitbake/bin/toaster b/bitbake/bin/toaster index 38e71acc2b..9c0a15ff67 100755 --- a/bitbake/bin/toaster +++ b/bitbake/bin/toaster @@ -143,25 +143,12 @@ if [ -e $BUILDDIR/bitbake.lock ]; then fi if [ ${CMD} == "start" ] && ( [ $lock -eq 0 ] || [ -e $BUILDDIR/.toastermain.pid ] ); then - echo "Error: bitbake lock state error. System is already on." 2>&1 - return 3 -elif [ ${CMD} == "stop" ] && ( [ $lock -eq 1 ] || ! [ -e $BUILDDIR/.toastermain.pid ] ) ; then - echo "Error: bitbake lock state error. Trying to stop a stopped system ? -If you think the system is hanged up, you can try to manually stop system with the commands - -# BBSERVER=localhost:8200 bitbake -m - -and - -# webserverKillAll -" 2>&1 + echo "Error: bitbake lock state error. File locks show that the system is on." 2>&1 + echo "If you see problems, stop and then start the system again." 2>&1 return 3 fi - - - # Execute the commands case $CMD in -- cgit v1.2.3-54-g00ecf