From 06a80040fff44d86ec9293bc6629fcb330ec3a4b Mon Sep 17 00:00:00 2001 From: John Colvin Date: Fri, 23 Aug 2024 14:13:15 +0000 Subject: [PATCH] Handle signal interrupts explicitly in sparkd Otherwise the python interpretter, which is instantiated when we load python md plugins, prevents the application from exiting. --- src/app_sparkd/sparkd/main.cpp | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/app_sparkd/sparkd/main.cpp b/src/app_sparkd/sparkd/main.cpp index bd2ace949..7922214b1 100644 --- a/src/app_sparkd/sparkd/main.cpp +++ b/src/app_sparkd/sparkd/main.cpp @@ -11,10 +11,18 @@ #include "sparkd/cmds/crypto/CryptoCmd.h" #include +#include using namespace bts; +void signal_handler(int signum) { + std::cerr << "Interrupt signal (" << signum << "). Exiting" << std::endl; + exit(signum); +} + int main(int argc, char **argv) { + std::signal(SIGINT, signal_handler); + std::signal(SIGTERM, signal_handler); utils::SparkLibInit init; // The catch testing framework has its own command line parser so