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 46447e8110284b0e960c67d81da6dae45c5deca1..aa202d3a934a430ba62234327eadebaf33d07be5 100644 (file)
--- 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);
 }