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.

     1

# Basic login and initial presence

     2

     3

[Client] Romeo

     4

	jid: discoverer@localhost

     5

	password: password

     6

     7

---------

     8

     9

Romeo connects

    10

    11

Romeo sends:

    12

	<iq type="get" id="info1">

    13

		<query xmlns="http://jabber.org/protocol/disco#info"/>

    14

	</iq>

    15

    16

Romeo receives:

    17

	<iq type="result" id="info1">

    18

		<query xmlns="http://jabber.org/protocol/disco#info" scansion:strict="false">

    19

			<identity xmlns="http://jabber.org/protocol/disco#info" category="account" type="registered"/>

    20

			<feature var="http://jabber.org/protocol/disco#info"/>

    21

			<feature var="http://jabber.org/protocol/disco#items"/>

    22

		</query>

    23

	</iq>

    24

    25

Romeo disconnects

    26