From eebf07549fe747bac253caa2113c37c7e8acceda Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Wed, 3 Oct 2018 11:59:27 +0900 Subject: [PATCH] doc: update repmgrd configuration for Debian/Ubuntu --- doc/repmgrd-configuration.sgml | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/doc/repmgrd-configuration.sgml b/doc/repmgrd-configuration.sgml index 252a2115..79373d66 100644 --- a/doc/repmgrd-configuration.sgml +++ b/doc/repmgrd-configuration.sgml @@ -454,7 +454,7 @@ REPMGRD_ENABLED=no #REPMGRD_CONF="/path/to/repmgr.conf" # additional options -#REPMGRD_OPTS="" +REPMGRD_OPTS="--daemonize=false" # user to run repmgrd as #REPMGRD_USER=postgres @@ -469,6 +469,19 @@ REPMGRD_ENABLED=no Set REPMGRD_ENABLED to yes, and REPMGRD_CONF to the repmgr.conf file you are using. + + + See for details of the Debian/Ubuntu packages and + typical file locations (including repmgr.conf). + + + + From repmgrd 4.1, ensure REPMGRD_OPTS includes + , as daemonization is handled by the service command. + We recommend setting repmgrd_pid_file in repmgr.conf to the + same value set in REPMGRD_PIDFILE to prevent another repmgrd + instance from being started manually. + If using systemd, you may need to execute systemctl daemon-reload. Also, if you attempted to start repmgrd using systemctl start repmgrd,