From owner-freebsd-hackers Fri Dec 11 12:30:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23874 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 12:30:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23866 for ; Fri, 11 Dec 1998 12:30:17 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id PAA13018 for ; Fri, 11 Dec 1998 15:30:02 -0500 (EST) Date: Fri, 11 Dec 1998 15:30:02 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: freebsd-hackers@FreeBSD.ORG Subject: status of NFS? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We're getting ready to replace two important production machines running 2.1.7.1 with two running our stable snap (980825). We currently run nfs between them to allow shell users to read mail locally (yes, I know about IMAP, but the solution we have works well now...). Basically the mail server export /var/mail to the shell machine and the shell machine exports /home so user's procmailrc's can be read, etc. NFS is over a private 100Mb network on a second nic. I'd just like to get a feel from everyone as to what the best options for NFS in this situation are. Right now, even with "soft" and "intr" flags, I get un-killable processes should one of the mounts go away. Generally, reboots are required to get everything back in sync after a failure. I'm now using a line like so: 10.0.0.1:/var/mail /var/mail nfs rw,bg,intr,soft,nfsv3,tcp,nosuid,nodev,noexec Looking at the archives, people seem to have better luck with v2 over udp. Thoughts? Thanks, Charles --- Charles Sprickman spork@super-g.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message