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.
No 'to' attribute:
IQ: Pass to appropriate handler
Presence: Broadcast to contacts
- if initial presence, also send out presence probes
- if probe would be to local user, generate presence stanza for them
Message: Route as if it is addressed to the bare JID of the sender
To a local host:
IQ: Pass to appropriate handler
Presence: -
Message: Deliver to admin?
To local contact:
Bare JID:
IQ: Pass to appropriate handler
Presence: Broadcast to all resources
Message: Route to 'best' resource
Full JID:
IQ: Send to resource
Presence: Send to resource
Message: Send to resource
Full JID but resource not connected:
IQ: Return service-unavailable
Message: Handle same as if to bare JID
Presence: Drop (unless type=subscribe[ed])
To remote contact:
Initiate s2s connection if necessary
Send stanza across