From: Ion Badulescu <lists@news.cs.columbia.edu>
Subject: Re: nfs-utils 1.0.5 break amd?
Date: Tue, 5 Aug 2003 09:23:14 -0400
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <200308051323.h75DNEKM016040@buggy.badula.org>
References: <1060071722.2980.74.camel@ikarus>
Cc: nfs@lists.sourceforge.net
To: Marc Schmitt <mschmitt@inf.ethz.ch>
In-Reply-To: <1060071722.2980.74.camel@ikarus>
Errors-To: nfs-admin@lists.sourceforge.net

On 05 Aug 2003 10:22:02 +0200, Marc Schmitt <mschmitt@inf.ethz.ch> wrote:
> Well, again it's me confusing stuff.
> With MOUNTD_TCP=no I thought I could prevent the clients from mounting
> the server with NFS over tcp... which is something I already have,
> because current RH kernels don't have NFS server support over TCP
> enabled in the kernel.

No, the transport protocol used to talk to mountd has no effect
whatsoever on the transport protocol used to talk to nfsd. Only the
version of the mountd protocol matters (and note that while mountd v3
corresponds to nfs v3, mountd v1 and v2 both correspond to nfs v2).

Since you use amd, you can always force it not to use tcp for nfs
mounts.  You can either do it globally for the client by setting
nfs_proto = udp in its amd.conf, or on a per mount entry basis by adding
proto = udp to that entry's mount options.

Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs