when doing sr3 stop xxx
it will send SIGTERM, and then wait, and see if the process exits on it's own,
then repeat the process multiple times, and then send SIGKILL if it's really stubborn.
If you run:
sr3 stop xxx
sr3 stop yyy
it runs those timing loops twice. if instead you run:
sr3 stop xxx yyy
it will run the loops once. So save time when starting and stopping components in sr3 (applies primarily to the dynamic_flow case.) by starting/stopping as many components as possible in one invocation.
when doing sr3 stop xxx it will send SIGTERM, and then wait, and see if the process exits on it's own, then repeat the process multiple times, and then send SIGKILL if it's really stubborn.
If you run:
sr3 stop xxx sr3 stop yyy
it runs those timing loops twice. if instead you run:
sr3 stop xxx yyy
it will run the loops once. So save time when starting and stopping components in sr3 (applies primarily to the dynamic_flow case.) by starting/stopping as many components as possible in one invocation.