From 321eb844e466ba80d2d889bdb7b774566148aaf3 Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Mon, 4 Feb 2019 16:08:45 +0900
Subject: [PATCH] doc: update Debian/Ubuntu repmgrd configuration

Remove reference to setting "repmgrd_pid_file", as this should not
be set in this context.

Per GitHub #517.
---
 doc/repmgrd-configuration.sgml | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/doc/repmgrd-configuration.sgml b/doc/repmgrd-configuration.sgml
index 56548770..b911e92b 100644
--- a/doc/repmgrd-configuration.sgml
+++ b/doc/repmgrd-configuration.sgml
@@ -492,9 +492,6 @@ REPMGRD_OPTS="--daemonize=false"
       <para>
         From <application>repmgrd</application> 4.1, ensure <varname>REPMGRD_OPTS</varname> includes
         <option>--daemonize=false</option>, as daemonization is handled by the service command.
-        We recommend setting <varname>repmgrd_pid_file</varname> in <filename>repmgr.conf</filename> to the
-        same value set in <varname>REPMGRD_PIDFILE</varname> to prevent another <application>repmgrd</application>
-        instance from being started manually.
       </para>
       <para>
         If using <application>systemd</application>, you may need to execute <command>systemctl daemon-reload</command>.