From 03a8f2eaba235debf524e7ee4fe3dbb753d57f6d Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Fri, 27 Feb 2015 10:01:38 +0900
Subject: [PATCH] Clarify repmgr.conf usage

---
 QUICKSTART.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/QUICKSTART.md b/QUICKSTART.md
index b71d0fd9..dd0ec817 100644
--- a/QUICKSTART.md
+++ b/QUICKSTART.md
@@ -20,7 +20,7 @@ Conceptual Overview
  - `repmgrd`: an optional daemon process which runs on standby nodes to monitor
    replication and node status
 
-Each PostgreSQL node requires a `repmgr` configuration file; additionally
+Each PostgreSQL node requires a `repmgr.conf` configuration file; additionally
 it must be "registered" using the `repmgr` command-line client. `repmgr` stores
 information about managed nodes in a custom schema on the node's current master
 database.
@@ -92,7 +92,7 @@ usage.
 
 ### repmgr configuration
 
-Each PostgreSQL node requires a `repmgr` configuration file containing
+Each PostgreSQL node requires a `repmgr.conf` configuration file containing
 identification and database connection information:
 
     cluster=test
@@ -111,7 +111,10 @@ identification and database connection information:
 * `pg_bindir`: (optional) location of PostgreSQL binaries, if not in the default $PATH
 
 Note that the configuration file should *not* be stored inside the PostgreSQL
-data directory.
+data directory. The configuration file can be specified with the
+`-f, --config-file=PATH` option and can have any arbitrary name. If no
+configuration file is specified, `repmgr` will search for `repmgr.conf`
+in the current working directory.
 
 Each node configuration needs to be registered with `repmgr`, either using the
 `repmgr` command line tool, or the `repmgrd` daemon; for details see below. Details