summaryrefslogtreecommitdiffstats
path: root/bin
diff options
context:
space:
mode:
authorEd Bartosh <ed.bartosh@linux.intel.com>2016-09-05 15:29:30 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-09-06 10:35:24 +0100
commit0dab45e9815e8939219900264e86f569c714b7c6 (patch)
tree70f64afcd5a1d5db1869d01b3ef4138c6842ee52 /bin
parent46db3279cb81b3ca6ce047204aee620f5ee51220 (diff)
downloadbitbake-contrib-0dab45e9815e8939219900264e86f569c714b7c6.tar.gz
bitbake-contrib-0dab45e9815e8939219900264e86f569c714b7c6.tar.bz2
bitbake-contrib-0dab45e9815e8939219900264e86f569c714b7c6.zip
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. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bin')
-rwxr-xr-xbin/toaster8
1 files changed, 0 insertions, 8 deletions
diff --git a/bin/toaster b/bin/toaster
index e35bfce58c..5e01101f96 100755
--- a/bin/toaster
+++ b/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"'