util.startup: Check root after detecting platform and reading config (thanks SigmaTel71) Ensures that startup.detect_platform() runs so know whether to use the POSIX method of checking the current user or something else. Also after reading the config so we know whether the root override setting is set.

mod_posix: Move everything to util.startup This allows greater control over the order of events. Notably, the internal ordering between daemonization, initialization of libunbound and setup of signal handling is sensitive. libunbound starts a separate thread for processing DNS requests. If this thread is started before signal handling has been set up, it will not inherit the signal handlers and instead behave as it would have before signal handlers were set up, i.e. cause the whole process to immediately exit. libunbound is usually initialized on the first DNS request, usually triggered by an outgoing s2s connection attempt. If daemonization happens before signals have been set up, signals may not be processed at all.

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

net.server_epoll: Log creation of signalfd handles at noise level To aid in tracking down signalfd-related problems

util.bit53: Add bnot() method

util.signal: Fail signalfd() if unable to change signal mask By aborting early, the failure should be brought to the attention somehow.

net.server_epoll: Log failure to hook signals To make any such failures noticeable

Merge 0.12->trunk

net.http.files: Validate argument to setup function Fixes error in #1765 by throwing an error earlier

mod_s2s: Comment on why we avoid hostnames in stanza bounce messages

mod_cron: Fix log format to account for float that was integer before

mod_cron: Sync Teal source with 92301fa7a673 Yeah, it's weird to have two versions. Needing more build dependencies is also something we want to avoid, so here we are.

util.signal: Wrap signalfd in an userdatum for gc handling etc

net.server_epoll: Support hooking signals via signalfd Handling signal events the same way as all other events makes sense and seems safer than the signal handling just jumping around in C and messing with Lua states.

util.signal: Add support for signalfd(2) on Linux signalfd allows handling signal events using the same method as sockets, via file descriptors. Thus all signal dispatch can go through the same main event loop as everything else, removing need for thread-scary signal handling where execution would just jump to the signal handler regardless of the state of Lua, and needing to keep track of Lua states/threads.

features: Add mod_server_info

mod_server_contact_info: Update to publish fields via new mod_server_info

mod_server_info: New module to manage the serverinfo disco extension form This allows multiple modules to populate the form dynamically. Currently the form is "owned" by mod_server_contact_info, which prevents other modules from contributing to it. A further commit will port mod_server_contact_info to use this module.

util.strbitop: Add common_prefix_bits() to Teal interface description

util.hashes: Add missing entries to Teal interface description Also sorted to match C source

util.crypto: Update Teal interface description to match C sources Was missing some entries. Rearranged to match order of entries in the C source Reg table.