From: Chuck Lever <chuck.lever@oracle.com>
Date: Mon, 19 Sep 2011 18:18:47 +0000 (-0400)
Subject: sm-notify: Use correct retransmit timeout when sending a fresh RPC
X-Git-Tag: debian/1%1.2.5-1~11^2~12
X-Git-Url: https://git.decadent.org.uk/gitweb/?p=nfs-utils.git;a=commitdiff_plain;h=24a3291682a316cae8998319d25e81fa4cc609ff

sm-notify: Use correct retransmit timeout when sending a fresh RPC

An RPC retransmit timeout should start out the same for each new RPC
request.  Don't increase the retransmit timeout after receiving the
reply to the rpcbind query.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Steve Dickson <steved@redhat.com>
---

diff --git a/utils/statd/sm-notify.c b/utils/statd/sm-notify.c
index 46447e8..aa202d3 100644
--- a/utils/statd/sm-notify.c
+++ b/utils/statd/sm-notify.c
@@ -701,8 +701,7 @@ smn_schedule(struct nsm_host *host)
 {
 	host->xid = 0;
 	host->send_next = time(NULL);
-	if (host->timeout >= NSM_MAX_TIMEOUT / 4)
-		host->timeout = NSM_MAX_TIMEOUT / 4;
+	host->timeout = NSM_TIMEOUT;
 	insert_host(host);
 }