Running runbuilds machinery in background allows Toaster to start builds initiated by toaster UI.
Added runbuilds pid file to the list in webserverKillAll to kill runbuilds the same way as runserver process. Signed-off-by: Ed Bartosh <[email protected]> --- bin/toaster | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/bin/toaster b/bin/toaster index d7653c2..62f6526 100755 --- a/bin/toaster +++ b/bin/toaster @@ -31,7 +31,7 @@ webserverKillAll() { local pidfile - for pidfile in ${BUILDDIR}/.toastermain.pid; do + for pidfile in ${BUILDDIR}/.toastermain.pid ${BUILDDIR}/.runbuilds.pid; do if [ -f ${pidfile} ]; then pid=`cat ${pidfile}` while kill -0 $pid 2>/dev/null; do @@ -280,6 +280,7 @@ case $CMD in bitbake --observe-only -u toasterui --remote-server=$BBSERVER -t xmlrpc >>${BUILDDIR}/toaster_ui.log 2>&1 \ & echo $! >${BUILDDIR}/.toasterui.pid fi + python $BBBASEDIR/lib/toaster/manage.py runbuilds & echo $! >${BUILDDIR}/.runbuilds.pid fi if [ $start_success -eq 1 ]; then # set fail safe stop system on terminal exit -- 2.1.4 -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
