You should never add your own signal handler, GNUNET_PROGRAM_run() does
that already, by adding your own you remove the GNUnet signal handler
and thus break the shutdown logic.
-Christian
On 10/26/22 10:15, accounts-gnu...@holbrook.no wrote:
When running the service with gnunet-arm -i svc, the function added with
GNUNET_SCHEDULER_add_shutdown is not being run when issuing gnunet-arm -k
svc
If I add a sigterm handler and do GNUNET_SCHEDULER_shutdown there, it
hangs and I have to sigint (and it doesnt halt).
If I run the service directly (without gnunet-arm) the shutdown task
gets triggered.
Is this expected behavior?
Is there a recommended way to add teardown code when using gnunet-arm?
I'm on 1567c9472b917a097cace08a7b08fc724e14f381
thanks,
l
