Handle SIGTERM signal

[romainreignier]

rosmon already handles SIGINT signal here:

rosmon/src/main.cpp

Line 389 in edf2742

signal(SIGINT, handleSIGINT);

But roslaunch also handles SIGTERM and SIGUP signals as seen here:

https://github.com/ros/ros_comm/blob/89ca9a7bf288b09d033a1ab6966ef8cfe39e1002/tools/roslaunch/src/roslaunch/pmon.py#L162

One use case I have is when a rosmon instance is launched within a QProcess. QProcess only provides SIGTERM, via QProcess::termate() and SIGKILL via QProcess::kill().

As SIGTERM and SIGINT are quite close in semantics according to this page, I think that it would be nice if rosmon also handles SIGTERM.

What do you think about that?

[xqms]

I agree, SIGTERM and SIGHUP should be handled gracefully as well. Could you check if #60 fits your requirements?

[romainreignier]

Yes, it is exactly the patch I have tried locally. Thank you. Le ven. 26 oct. 2018 à 23:42, Max Schwarz <notifications@github.com> a écrit :

…

I agree, SIGTERM and SIGHUP should be handled gracefully as well. Could you check if #60 <#60> fits your requirements? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#59 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIb5YA0NPcjwgfmrSxLjHrdujVL-mQ2eks5uo4G5gaJpZM4X5w1P> .

[xqms]

Merged #60. Thanks for checking!