Test did important condor status command in back ticks making it prone
to failure from "communication error" during the tool run. Switched it
to "runCondorTool" which is more tolerent. #3594
onversion of condor_who data usage for detecing personal condor's
up/down state also required a new option -quick for use before master
is running. Also though we still effectivy allow 40 seconds for the
master to stop. We have a two stage allowance for a personal condor
coming up. We pass two times, currently 120 and 30 to the state
change function. The second number is when we need a live master
by. If we meet that constraint then we have the first number of
seconds to get fully up. #4149