When shutting the database engines down, the associated "slon"
processes tend to exit too.

My preference is that when the database is stopped/started (or
during a network outage) that the daemon remains running, and
attempts periodic reconnects.

What is the suggested approach for managing the daemon processes
so that replication starts up again when the database becomes
available?

Thanks,

Dave