[PATCH] Improve description of corosync.conf's token_retransmit_before_loss_const

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Signed-off-by: Steven Dake <sdake@xxxxxxxxxx>
---
 man/corosync.conf.5 | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/man/corosync.conf.5 b/man/corosync.conf.5
index b6fd0a0..2b72248 100644
--- a/man/corosync.conf.5
+++ b/man/corosync.conf.5
@@ -318,9 +318,11 @@ The default is 180 milliseconds.
 
 .TP
 token_retransmits_before_loss_const
-This value identifies how many token retransmits should be attempted before
-forming a new configuration.  If this value is set, retransmit and hold will
-be automatically calculated from retransmits_before_loss and token.
+This value identifies how many token retransmits should be attempted.  If no
+token is received by the next processor in the ring before the token timeout
+expires on that node, a new configuration will be formed.  If this value is set,
+retransmit and hold will be automatically calculated from
+retransmits_before_loss and token
 
 The default is 4 retransmissions.
 
-- 
1.8.1.4

_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss




[Index of Archives]     [Linux Clusters]     [Corosync Project]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [X.Org]

  Powered by Linux