Quellcode durchsuchen

Correct the description of bindnetaddr config parameter in manpage

bindnetaddr has been wrongly described in the past, and did not
document that fact that it will also accept exact address matches.

Signed-off-by: Barney Desmond <barney.desmond@anchor.net.au>
Reviewed-by: Jan Friesse <jfriesse@redhat.com>
Barney Desmond vor 14 Jahren
Ursprung
Commit
323f0f4277
1 geänderte Dateien mit 10 neuen und 5 gelöschten Zeilen
  1. 10 5
      man/corosync.conf.5

+ 10 - 5
man/corosync.conf.5

@@ -81,13 +81,18 @@ ring. The ringnumber must start at 0.
 .TP
 .TP
 bindnetaddr
 bindnetaddr
 This specifies the network address the corosync executive should bind
 This specifies the network address the corosync executive should bind
-to.  For example, if the local interface is 192.168.5.92 with netmask
-255.255.255.0, set bindnetaddr to 192.168.5.0.  If the local interface
-is 192.168.5.92 with netmask 255.255.255.192, set bindnetaddr to
-192.168.5.64, and so forth.
+to.
+
+bindnetaddr should be an IP address configured on the system, or a network
+address.
+
+For example, if the local interface is 192.168.5.92 with netmask
+255.255.255.0, you should set bindnetaddr to 192.168.5.92 or 192.168.5.0.
+If the local interface is 192.168.5.92 with netmask 255.255.255.192,
+set bindnetaddr to 192.168.5.92 or 192.168.5.64, and so forth.
 
 
 This may also be an IPV6 address, in which case IPV6 networking will be used.
 This may also be an IPV6 address, in which case IPV6 networking will be used.
-In this case, the full address must be specified and there is no automatic
+In this case, the exact address must be specified and there is no automatic
 selection of the network interface within a specific subnet as with IPv4.
 selection of the network interface within a specific subnet as with IPv4.
 
 
 If IPv6 networking is used, the nodeid field in nodelist must be specified.
 If IPv6 networking is used, the nodeid field in nodelist must be specified.