Blame SOURCES/bz1845583-exportfs-1-describe-clientspec-format-in-metadata.patch

d42a06
From f572186ec9bd26c791771a18d38804cfde602578 Mon Sep 17 00:00:00 2001
d42a06
From: zzhou1 <10611019+zzhou1@users.noreply.github.com>
d42a06
Date: Tue, 3 Sep 2019 09:24:23 +0000
d42a06
Subject: [PATCH] exportfs: doc clarification for clientspec format
d42a06
d42a06
Point out the standard of the format is aligned with `man exportfs`, and also point out the correct way to deal with the use case to export the same directory(-ies) to multiple subnets.
d42a06
---
d42a06
 heartbeat/exportfs | 6 ++++++
d42a06
 1 file changed, 6 insertions(+)
d42a06
d42a06
diff --git a/heartbeat/exportfs b/heartbeat/exportfs
d42a06
index 80ed057f2..dc609a0b4 100755
d42a06
--- a/heartbeat/exportfs
d42a06
+++ b/heartbeat/exportfs
d42a06
@@ -47,6 +47,12 @@ Manages NFS exports
d42a06
 <longdesc lang="en">
d42a06
 The client specification allowing remote machines to mount the directory
d42a06
 (or directories) over NFS.
d42a06
+
d42a06
+Note: it follows the format defined in "man exportfs". For example, in
d42a06
+the use case to export the directory(-ies) for multiple subnets, please
d42a06
+do config a dedicated primitive for each subnet CIDR ip address, 
d42a06
+and do not attempt to use multiple CIDR ip addresses in a space
d42a06
+seperated list, like in /etc/exports.
d42a06
 </longdesc>
d42a06
 <shortdesc lang="en">
d42a06
 Client ACL.