mod_bosh: Set base_type on session This fixes a traceback with mod_saslauth. Ideally we move this to util.session at some point, though.

util.startup: Back out 598df17b8ebb Broke signal handling again, such that an early s2s connection results in libunbound catching signals and getting Prosody killed on e.g. SIGHUP This returns to the situation where prosody --daemonize does not respond to signals.

util.startup: Hook signals after daemonization signalfds stop working with epoll after forking hooking signals later should not affect anything

mod_pubsub: Ignore shadowed variable [luacheck]

mod_pubsub: Add shell commands to create and list nodes

core.features: Advertise that events are fired for SIGUSR1/2 Moved here from mod_posix since these events no longer originate there

util.startup: Fix firing of USR1/2 events

net.server: Restore epoll signalfd handling Reverts 4a9a69659727

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

net.server: Disable epoll signalfd handling by default until problems resolved