summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--corosync.rnc2
-rw-r--r--corosync.rng.expected2
-rw-r--r--corosync.rng.trang2
3 files changed, 3 insertions, 3 deletions
diff --git a/corosync.rnc b/corosync.rnc
index 8236c83..96baaff 100644
--- a/corosync.rnc
+++ b/corosync.rnc
@@ -453,7 +453,7 @@ totem =
When sending multicast traffic, if the network frequently
reconfigures, chances are that some device in the network doesn't
support large frames.
-
+
Choose hardware carefully if intending to use large frame support.""" ]
attribute netmtu {xsd:unsignedInt}?,
diff --git a/corosync.rng.expected b/corosync.rng.expected
index 464af86..9aac379 100644
--- a/corosync.rng.expected
+++ b/corosync.rng.expected
@@ -684,7 +684,7 @@ The default setting works well for nearly all modern switches.</a:documentation>
When sending multicast traffic, if the network frequently
reconfigures, chances are that some device in the network doesn't
support large frames.
-
+
Choose hardware carefully if intending to use large frame support.">
<a:documentation>This specifies the network maximum transmit
unit. Setting this value beyond '1500', the regular frame MTU, requires
diff --git a/corosync.rng.trang b/corosync.rng.trang
index cc2c6a8..676a66f 100644
--- a/corosync.rng.trang
+++ b/corosync.rng.trang
@@ -664,7 +664,7 @@ The default setting works well for nearly all modern switches.</a:documentation>
When sending multicast traffic, if the network frequently
reconfigures, chances are that some device in the network doesn't
support large frames.
-
+
Choose hardware carefully if intending to use large frame support.">
<a:documentation>This specifies the network maximum transmit
unit. Setting this value beyond '1500', the regular frame MTU, requires