tree b3ef413b8c3b29baab3671dfca5b766e7d976b6d
parent 158ea5bc6604122071a7d18f085eecb062057d56
author Pau Espin Pedrol <pespin@sysmocom.de> 1553880990 +0100
committer Pau Espin Pedrol <pespin@sysmocom.de> 1553881888 +0100

osmo-trx: Avoid handling signals after shutdown triggered

Recently a blocked osmo-trx process was found after ending SIGTERM to
it.
Apparently one thread was handling SIGTERM and calling fprintf()
(grabbing libc lock) while another thread was handling another signal
and also grabbing similar lock. Both thread looked deadlocked there.
Probably this change doesn't fix the block on its own, but at least
simplifies scenarios inside signal ctx which can go wrong.

Change-Id: If91621913b8b03d8a0f4c863be0b0d479f97e8a1