Managing NFS and KRPC Kernel Configurations in HP-UX 11i v3 (762807-001, March 2014)

Note: If the tunable is set to a value greater than 64
requests, an informational warning is issued, at runtime.
Any value greater than 64 is beyond the tested limits.
Restrictions on Changing
The rpc_svc_default_max_same_xprt tunable is dynamic. System reboot is not required to activate
changes made to this tunable. However, the maximum number of requests that can be processed
before switching transport endpoints is set when the transport endpoint is configured into the KRPC
subsystem. Changes made to this tunable affect only the new endpoints and not the existing ones.
Modifying the Value
Modify the value of this tunable so services can take advantage of certain client behaviors, such as
write clustering. Increasing the value of this tunable enables the server to take better advantage of
client behaviors.
2.4.4 rpc_svc_idle_timeout
Description
The rpc_svc_idle_timeout tunable controls the time interval, in milliseconds, that a TCP connection
between the server and client may remain idle before it is forcibly closed by the NFS server system.
Tested Values
Default: 360000 (6 minutes)
Min: 1000 (1 second)
Max: 600000 (10 minutes)
Note: If the tunable is set to a value less than 1000
milliseconds or greater than 600000 milliseconds, an
informational warning is issued at runtime. These values are
beyond the tested limits.
Restrictions on Changing
The rpc_svc_idle_timeout tunable is dynamic. System reboot is not required to activate changes made
to this tunable. Changes made to this tunable are applicable for TCP connections that are created
after the value of this tunable is modified.
Modifying the Value
If you prefer to have idle TCP connections cleaned up in less than 6 minutes, decrease this value. If
you prefer that idle TCP connections remain available for longer than 6 minutes, increase this value.
However, this tunable only controls the server behavior.
To change the client-side behavior with respect to idle TCP connections, modify the
rpc_clnt_idle_timeout parameter. For more information, see rpc_clnt_idle_timeout