If your server is misconfigured such that the RPC calls will fail, how should the client know that it's not a transient error?
Per the nfs(5) manpage, if you want NFS calls to be interruptable, you can use the non-default 'intr' option. If you want NFS calls to eventually time out rather than being retried indefinitely, you can use the non-default 'soft' option. I don't think the behavior you're describing here is a bug, just the expected default behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1340451 Title: nfs client hangs when nlockmgr service at rpcbind refuses connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1340451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
