From 67cfafb23c3722bb63394525b517f0f9d2eb4ab2 Mon Sep 17 00:00:00 2001
From: Johan Wikman <johan.wikman@mariadb.com>
Date: Wed, 24 Aug 2016 14:26:00 +0300
Subject: [PATCH] Enhance MaxAdmin info in 2.0 Upgrading document

---
 .../Upgrading/Upgrading-To-MaxScale-2.0.md    | 23 +++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/Documentation/Upgrading/Upgrading-To-MaxScale-2.0.md b/Documentation/Upgrading/Upgrading-To-MaxScale-2.0.md
index 136985011..a1ca08064 100644
--- a/Documentation/Upgrading/Upgrading-To-MaxScale-2.0.md
+++ b/Documentation/Upgrading/Upgrading-To-MaxScale-2.0.md
@@ -21,6 +21,29 @@ When 2.0 has been installed, MaxAdmin can only be used by `root` and
 other users must be added anew. Please consult
 [MaxAdmin documentation](../Reference/MaxAdmin.md) for more details.
 
+This change requires the _maxscaled_ protocol listener entry in the
+MaxScale configuration file to be updated; address and port information
+must be replaced with socket information. For instance, an entry like
+```
+[MaxAdmin Listener]
+type=listener
+protocol=maxscaled
+address=localhost
+port=6603
+```
+should be updated to
+```
+[MaxAdmin Listener]
+type=listener
+protocol=maxscaled
+socket=default
+```
+where `default` corresponds to `/tmp/maxadmin.sock`.
+
+Note that if this update is *not* made, maxscaled will log a warning
+and use the default socket path. This behaviour may change in later
+releases of MaxScale.
+
 ## MySQL Monitor
 
 The MySQL Monitor now assigns the stale state to the master server by default.