From owner-freebsd-bugs Mon Apr 26 10:10:15 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 82B13152B2 for ; Mon, 26 Apr 1999 10:10:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id KAA09094; Mon, 26 Apr 1999 10:10:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 26 Apr 1999 10:10:02 -0700 (PDT) Message-Id: <199904261710.KAA09094@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Mikhail Teterin Subject: Re: bin/11335: find hangs in `nfsrcv' on local filesystem despite -xdev Reply-To: Mikhail Teterin Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/11335; it has been noted by GNATS. From: Mikhail Teterin To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Cc: Subject: Re: bin/11335: find hangs in `nfsrcv' on local filesystem despite -xdev Date: Mon, 26 Apr 1999 12:59:30 -0400 (EDT) Garrett Wollman once wrote: > < said: > > >> Description: > > > A simple `find / -xdev -type f' hangs without a single line of > > output. `ps -axlww | grep pid' shows: > > 105 7553 10201 0 -1 0 800 504 nfsrcv I p4 0:00.01 / (find) > > That's Just The Way It Is. `find' has to stat the mount point in > order to find out that it is in fact a mount point. And there is no other, safe, way to do it? At least, may be forking off a child, a'la AMD? Something has to be done about /etc/security then -- I come on Monday to see the Saturday and Sunday daily runs hanging... Yours, -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message