Thank you for taking the time to report this issue and help to improve Ubuntu.
> 3. Scenario 1: when myserver is powered down the command > mount.nfs <server:/export> <mountppoint> > should return with an error immediately No, sorry, that's not how TCP/IP works. If the server is down, then your client has no way to *know* that the server is down, except by waiting for the protocol timeout to be reached. This is different than if the NFS *service* is down or firewalled, in which case you will get an immediate reject. > commit 697e28939b7d0a3e0ffe3b6bd516213a55f5a063 > Author: Jeff Layton <[email protected]> Date: Mon Apr 14 09:03:13 2008 -0400 This is unrelated. If your server is down, you're not getting an EACCES error. ** Changed in: nfs-utils (Ubuntu) Status: New => Invalid -- mount.nfs hangs when nfs server is not reachable https://bugs.launchpad.net/bugs/470405 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
