summaryrefslogtreecommitdiff
path: root/main.c
diff options
context:
space:
mode:
authorMartin Pool <mbp@samba.org>2002-04-08 07:46:34 +0000
committerMartin Pool <mbp@samba.org>2002-04-08 07:46:34 +0000
commit9fb3f7a9aba781b901c0b06fdf700a3701870d0b (patch)
tree11445e4a2d761d1d3d71eaf294146e525d14bb6d /main.c
parent734a94a20c7ee4bd787eb434d21d8be1f24f7774 (diff)
downloadrsync-9fb3f7a9aba781b901c0b06fdf700a3701870d0b.tar.gz
rsync-9fb3f7a9aba781b901c0b06fdf700a3701870d0b.tar.bz2
rsync-9fb3f7a9aba781b901c0b06fdf700a3701870d0b.zip
Doc rsync_panic_handler()
Diffstat (limited to 'main.c')
-rw-r--r--main.c8
1 files changed, 8 insertions, 0 deletions
diff --git a/main.c b/main.c
index 8aad59cd..37c46183 100644
--- a/main.c
+++ b/main.c
@@ -827,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];