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.
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