Re: mount.nfs: protocol fallback when server doesn't support TCP

[Neil Brown <neilb@suse.de>]

On Tue, 31 Aug 2010 16:29:59 -0400
Chuck Lever <chuck.lever@oracle.com> wrote:

> 
> On Aug 30, 2010, at 9:00 PM, Neil Brown wrote:
> 
> > Two observations I've made while exploring which are only tangential to the
> > current issue:
> > 
> > 1/ if I give an invalid proto name
> >          mount -o proto=fred .....
> >    the mount command fails (as it should) but gives no error message.
> 
> I was not able to reproduce this.  I get an appropriate error message from mount.nfs when built either with TI-RPC or without.  I'm using the latest upstream nfs-utils + my mountd patches.
> 

Ahh yes, fixed by

commit 9ac7a15017b876d4d8d3a4502ebaf954f36f7f54
Author: Steve Dickson <steved@redhat.com>
Date:   Thu Jun 3 08:53:22 2010 -0400

    mount.nfs: silently fails when the network protocol is not found
    
    mount.nfs should display some type of error diagnostics when
    the network protocol can not be determined.
    
    Signed-off-by: Steve Dickson <steved@redhat.com>


Thanks,
NeilBrown