From 4c64d52afbce2655380df5aa59248fa12edeb852 Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Thu, 25 Dec 2014 10:52:50 +0900
Subject: [PATCH] Update repmgrd usage examples and help output

---
 README.rst                   | 4 +++-
 autofailover_quick_setup.rst | 2 +-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/README.rst b/README.rst
index b075a284..12e74764 100644
--- a/README.rst
+++ b/README.rst
@@ -545,7 +545,7 @@ You could now register the standby by typing on "node2"::
 
 However, you can instead start repmgrd::
 
-  repmgrd -f /var/lib/pgsql/repmgr/repmgr.conf --verbose > /var/lib/pgsql/repmgr/repmgr.log 2>&1
+  repmgrd -f /var/lib/pgsql/repmgr/repmgr.conf --daemonize --verbose > /var/lib/pgsql/repmgr/repmgr.log 2>&1
 
 Which will automatically register your standby system.  And eventually
 you need repmgrd running anyway, to save lag monitoring information.
@@ -1015,6 +1015,8 @@ The output from this program looks like this::
     --verbose                 output verbose activity information
     --monitoring-history      track advance or lag of the replication in every standby in repl_monitor
     -f, --config-file=PATH    path to the configuration file
+    -d, --daemonize           detach process from foregroun
+    -p, --pid-file=PATH       write a PID file
 
   repmgrd monitors a cluster of servers.
 
diff --git a/autofailover_quick_setup.rst b/autofailover_quick_setup.rst
index e9aeb6fe..1826b521 100644
--- a/autofailover_quick_setup.rst
+++ b/autofailover_quick_setup.rst
@@ -202,7 +202,7 @@ Start the repmgrd daemons
 Log in node2 and witness.
 
 	su - postgres
-	repmgrd -f /etc/repmgr/repmgr.conf > /var/log/postgresql/repmgr.log 2>&1
+	repmgrd -f /etc/repmgr/repmgr.conf --daemonize -> /var/log/postgresql/repmgr.log 2>&1
 
 **Note:** The Master does not need a repmgrd daemon.