Start TCP and TLS listeners later in boot process

See #1869 for background.

This makes listener startup and peer notification to be some
of the last boot steps. This way client operations on a node that's
not 100% initialised are less likely.

Since some parts of boot process happen concurrently, without coordinating
all of them with listener startup this is not something that can be
guaranteed. Moving listener startup to a later stage reduces the
probability of clients attempting operations on a booting node.

0 files changed, 0 insertions, 0 deletions