From 8719012c789146f7fe3c0480cfde7291119de075 Mon Sep 17 00:00:00 2001 From: Ed Bartosh Date: Mon, 5 Sep 2016 15:29:30 +0100 Subject: bitbake: toaster: don't kill toaster on start There is no point of trying to kill django development server when toaster starts because 'manage.py checksocket' command is already used in the script code to check if development server port is occupied. Even if Toaster is listening on another port, killing previous instance looks quite implicit and doesn't solve anything as there are other processes that might be still running. (Bitbake rev: 0dab45e9815e8939219900264e86f569c714b7c6) Signed-off-by: Ed Bartosh Signed-off-by: Michael Wood Signed-off-by: Richard Purdie --- bitbake/bin/toaster | 8 -------- 1 file changed, 8 deletions(-) (limited to 'bitbake') diff --git a/bitbake/bin/toaster b/bitbake/bin/toaster index e35bfce58c..5e01101f96 100755 --- a/bitbake/bin/toaster +++ b/bitbake/bin/toaster @@ -249,14 +249,6 @@ case $CMD in fi fi - # kill Toaster web server if it's alive - if [ -e $BUILDDIR/.toastermain.pid ] && kill -0 `cat $BUILDDIR/.toastermain.pid`; then - echo "Warning: bitbake appears to be dead, but the Toaster web server is running." 1>&2 - echo " Something fishy is going on." 1>&2 - echo "Cleaning up the web server to start from a clean slate." - webserverKillAll - fi - # Create configuration file conf=${BUILDDIR}/conf/local.conf line='INHERIT+="toaster buildhistory"' -- cgit v1.2.3-54-g00ecf