Armer requires escalation to SIGTERM to quit in example.

[stevencolinmartin]

CTRL-C does not cause nicely quit

(robostackenv) stevem@steveQUT:~/armer_ws$ roslaunch armer armer.launch ... logging to /home/stevem/.ros/log/e526e96c-dfb2-11eb-8d88-b88584a53a39/roslaunch-steveQUT-364430.log Checking log directory for disk usage. This may take a while. Press Ctrl-C to interrupt WARNING: disk usage in log directory [/home/stevem/.ros/log] is over 1GB. It's recommended that you use the 'rosclean' command.

started roslaunch server http://steveQUT:39161/

SUMMARY

PARAMETERS

• /armer/config: /home/stevem/arme...
• /rosdistro: noetic
• /rosversion: 1.15.9

NODES / armer (armer/armer)

ROS_MASTER_URI=http://localhost:11311

process[armer-1]: started with pid [364444] /home/stevem/mambaforge/envs/robostackenv/lib/python3.8/site-packages/swift/out ^C[armer-1] killing on exit ^[[A^C^C^C[armer-1] escalating to SIGTERM [armer-1] escalating to SIGKILL Shutdown errors:

• process[armer-1, pid 364444]: required SIGKILL. May still be running. shutting down processing monitor... ... shutting down processing monitor complete done

[suddrey-qut]

rospy captures interrupt signals by default which for long running scripts causes issues. I've disabled this for the examples.