mod_posix: Move POSIX signal handling into util.startup to avoid race
When libunbound is initialized, it spawns a thread to work in.
In case a module initializes libunbound, e.g. by triggering a s2s
connection, Prosody would not handle signals, instead immediately quit
on e.g. the reload (SIGHUP) signal. Likely because the libunbound thread
would not have inherited the signal mask from the main Prosody thread.
Thanks Menel, riau and franck-x for reporting and help narrowing down
module:set_global();
local filters = require "prosody.util.filters";
local function log_send(t, session)
if t and t ~= "" and t ~= " " then
session.log("debug", "SEND: %s", t);
end
return t;
end
local function log_recv(t, session)
if t and t ~= "" and t ~= " " then
session.log("debug", "RECV: %s", t);
end
return t;
end
local function init_raw_logging(session)
filters.add_filter(session, "stanzas/in", log_recv, -10000);
filters.add_filter(session, "stanzas/out", log_send, 10000);
end
filters.add_filter_hook(init_raw_logging);
function module.unload()
filters.remove_filter_hook(init_raw_logging);
end