From owner-freebsd-hackers Mon Aug 2 0:27:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id 83B1D14F04 for ; Mon, 2 Aug 1999 00:27:09 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id JAA87675; Mon, 2 Aug 1999 09:25:52 +0200 (CEST) (envelope-from des) To: Alfred Perlstein Cc: Doug , freebsd-hackers@FreeBSD.ORG, Dag-Erling Smorgrav Subject: Re: readdirplus is very cool, any other nfs client suggestions? References: Organization: Yes Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 02 Aug 1999 09:25:52 +0200 In-Reply-To: Alfred Perlstein's message of "Fri, 30 Jul 1999 20:43:12 -0400 (EDT)" Message-ID: Lines: 30 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > 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... I used loopback mounts to test NFS make worlds a while ago (there were places where make world would bomb because chflags doesn't work on NFS) and experienced deadlock problems. Somebody (I don't remember who exactly) told me that this was a known problem with the NFSv3 code; reading over loopback mounts works fine, but writing apparently results in deadlocks. Search the archives; the commit logs should give you an idea of when this was (check the logs for Makefiles that use chflags). root@des ~# current -l -F Makefile chflags src/Makefile.inc1 src/lib/libc/sys/Makefile.inc src/lib/libc_r/Makefile src/release/Makefile src/sys/alpha/conf/Makefile.alpha src/sys/i386/conf/Makefile.i386 src/sys/pc98/conf/Makefile.pc98 src/usr.bin/Makefile src/usr.bin/chflags/Makefile src/usr.bin/chpass/Makefile src/usr.bin/passwd/Makefile DES -- Dag-Erling Smorgrav - des@yes.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message