Avoid propagating shutdown signal to all subprocesses

This was a sort-of-regression with 7233f68

While this behavior might seem desirable in some cases, multi-user
installs like public servers would rather not kill children while
upgrading.

Turns out that pipes are inherited by forks, and writing in one side
means there might be more than one listener that calls
bitlbee_shutdown(). If the parent gets it, the children will get it
too. If a child gets it, the parent and the other children get it too.

This adds a sighandler_shutdown_setup() function that closes any
previously existing pipes and disconnects the events from them, to
create a new one. This is called again after forking each child process.

While I'm sure this fixes the issue, I still don't understand why it
*didn't* kill the forked processes in some cases. Worrying.

1 files changed, 3 insertions, 0 deletions

diff --git a/bitlbee.c b/bitlbee.c
index 98f2d9c9..fa8c6795 100644
--- a/bitlbee.c
+++ b/bitlbee.c
@@ -310,6 +310,9 @@ static gboolean bitlbee_io_new_client(gpointer data, gint fd, b_input_condition
 			close(global.listen_socket);
 			b_event_remove(global.listen_watch_source_id);
 
+			/* Make a new pipe for the shutdown signal handler */
+			sighandler_shutdown_setup();
+
 			/* Make the connection. */
 			irc = irc_new(new_socket);