My last commit accidentally re-introduced the risk of
request_visnode.sh trying to re-connect to a job which is in the
process of being deleted.  I have now separated stopCmd into
stopCmd and stopCmdForRestart, so that I can still have a
speedy exit when finishing my MASSIVE Desktop session, but
without risking triggering this request_visnode.sh problem.