From: Ion Badulescu Subject: Re: nfs client using autofs v4 Date: Wed, 8 Jan 2003 20:17:13 -0500 Sender: nfs-admin@lists.sourceforge.net Message-ID: <200301090117.h091HD426729@moisil.badula.org> References: Cc: linuxmanagers@linuxmanagers.org, NFS@lists.sourceforge.net Return-path: To: devnull@adc.idt.com In-Reply-To: Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: On Wed, 8 Jan 2003 18:24:27 -0500 (EST), devnull@adc.idt.com wrote: > > We would like to default all NFS mounts to use TCP and if not available > use UDP. This way all mounts coming from Network Appliance will be TCP and > the ones from the Linux Box will be UDP. > > Does anyone know of a way of doing this. > > Adding localoptions='nfsvers=3,tcp,udp' to the local autofs startup script > does not work. > > Maybe this is a compile-time option to autofs(i dont see one) No, because autofs doesn't know anything about NFS. It simply calls the external mount program with the arguments you gave it. What you need is a mount program which can autodetect what the server supports in terms of NFS service. I don't know of any such mount, though. Your alternative is amd (www.am-utils.org), whose 6.1 version (now in late beta) supports autofs mounts and which can do this autodetection and more. Hope this helps, Ion [am-utils co-maintainer and primary developer of autofs support in amd] -- 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 is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs