There is no point of trying to kill django development server when toaster starts as '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 <[email protected]> --- bitbake/bin/toaster | 8 -------- 1 file changed, 8 deletions(-) diff --git a/bitbake/bin/toaster b/bitbake/bin/toaster index e35bfce..5e01101 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"' -- 2.6.6 -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
