From owner-freebsd-hackers Fri Jul 30 17:44:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 953D414BED for ; Fri, 30 Jul 1999 17:44:11 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id UAA07680; Fri, 30 Jul 1999 20:43:13 -0400 (EDT) Date: Fri, 30 Jul 1999 20:43:12 -0400 (EDT) From: Alfred Perlstein Reply-To: Alfred Perlstein To: Doug Cc: freebsd-hackers@FreeBSD.ORG, Dag-Erling Smorgrav Subject: Re: readdirplus is very cool, any other nfs client suggestions? In-Reply-To: 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 On Fri, 30 Jul 1999, Doug wrote: > Spent quite a bit of time today playing around with the newly > repaired readdirplus option for nfs clients in -current. My thanks to Matt > Dillon and Bill Paul. For those that don't remember, I'm trying to use > amd/nfs client stuff on some freebsd web servers that read their data from > our sun (and now sun + netapp) web farm. I have a script that used to lock > up amd and/or nfs and/or the whole machine pretty regularly. I've run it > about 100 times today in various conditions with no ill effects. About > this I am quite pleased. :) ... > amd.Interfaces: > > /defaults type:=nfs;opts:=rw,vers=3,readdirplus,intr,proto=udp > > * rhost:=IP${key};rfs:=/Space/${key} Not to rain on your parade, but Dag-Erling informed me that there was problems using NFSv3 over the loopback interface that can cause lockups. DES: can you elaborate? you think it may cause problems with amd since it's like an NFS buffer isn't it and would work over the loopback... -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message