sm-notify: Use correct retransmit timeout when sending a fresh RPC
authorChuck Lever <chuck.lever@oracle.com>
Mon, 19 Sep 2011 18:18:47 +0000 (14:18 -0400)
committerLuk Claes <luk@debian.org>
Sun, 2 Oct 2011 14:16:47 +0000 (16:16 +0200)
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>
utils/statd/sm-notify.c

index 46447e8..aa202d3 100644 (file)
@@ -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);
 }