X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/4fdc39dde80fc80d511b7101d15ecc0be77a73a3..0f9c48b1d23fbe958544094e97ba8ad2a7d8b8f4:/main.c

diff --git a/main.c b/main.c
index 254d9d57..37c46183 100644
--- a/main.c
+++ b/main.c
@@ -492,9 +492,10 @@ static void do_server_recv(int f_in, int f_out, int argc,char *argv[])
 }
 
 
-void child_main(int argc, char *argv[])
+int child_main(int argc, char *argv[])
 {
 	start_server(STDIN_FILENO, STDOUT_FILENO, argc, argv);
+	return 0;
 }
 
 
@@ -666,8 +667,6 @@ static int start_client(int argc, char *argv[])
 	extern int am_sender;
 	extern char *shell_cmd;
 	extern int rsync_port;
-	extern int whole_file;
-	extern int write_batch;
 	extern int read_batch;
 	int rc;
 
@@ -828,6 +827,14 @@ const char *get_panic_action(void)
 }
 
 
+/**
+ * Handle a fatal signal by launching a debugger, controlled by $RSYNC_PANIC_ACTION.
+ *
+ * This signal handler is only installed if we were configured with
+ * --enable-maintainer-mode.  Perhaps it should always be on and we
+ * should just look at the environment variable, but I'm a bit leery
+ * of a signal sending us into a busy loop.
+ **/
 static RETSIGTYPE rsync_panic_handler(int UNUSED(whatsig))
 {
 	char cmd_buf[300];