Hi folks, Is it true that NFS mount option "timeo" has nothing to do with the socket's setting of the user-specified timeout TCP_USER_TIMEOUT. Instead, when creating a TCP socket NFS uses either default/hard coded value of 60s for v3 or for v4.x it's lease based. Is there no value is having an adjustable TCP timeout value? Thank you.