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
syntax: glob
.hgignore
.luacheckcache
data
local
www_files
html/*
prosody.lua
prosody.cfg.lua
prosody.version
config.unix
*.patch
*.diff
*.orig
*.rej
*.save
*~
*.o
*.so
*.install
*.pid
*.log
*.err
*.debug
*.dll
*.exp
*.lib
*.obj
luacov.report.out
luacov.report.out.index
luacov.stats.out