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

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