Patchwork [bitbake-devel,4/8] toaster: erase checks for stop command

login
register
mail settings
Submitter Alexandru DAMIAN
Date March 11, 2014, 3:49 p.m.
Message ID <5d6594de8876be8ce4df56b846fee0fc687a6261.1394552757.git.alexandru.damian@intel.com>
Download mbox | patch
Permalink /patch/68401/
State New
Headers show

Comments

Alexandru DAMIAN - March 11, 2014, 3:49 p.m.
From: Alexandru DAMIAN <alexandru.damian@intel.com>

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]

Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
---
 bin/toaster | 17 ++---------------
 1 file changed, 2 insertions(+), 15 deletions(-)

Patch

diff --git a/bin/toaster b/bin/toaster
index 38e71ac..9c0a15f 100755
--- a/bin/toaster
+++ b/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