From owner-freebsd-hackers Thu Aug 2 3:48:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 1270537B401 for ; Thu, 2 Aug 2001 03:48:38 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 2 Aug 2001 11:48:35 +0100 (BST) Date: Thu, 2 Aug 2001 11:48:35 +0100 From: David Malone To: Julian Stacey Cc: hackers@freebsd.org Subject: Re: vnconfig + mount removes permission for a second Message-ID: <20010802114835.A92803@walton.maths.tcd.ie> References: <200108011135.f71BZWP01453@jhs.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200108011135.f71BZWP01453@jhs.muc.de>; from jhs@jhs.muc.de on Wed, Aug 01, 2001 at 11:35:32AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 01, 2001 at 11:35:32AM +0000, Julian Stacey wrote: > So something is momentarily making the image unreadable. > Should FreeBSD [mount/kernel ?] be changed to avoid denying access ? When you do a mount it automatically HUP's mountd which then re-exports NFS filesystems. I suspect what is happening is that the the filesystem mountlist is being cleared for a moment and that is upsetting the cp. You could try moving /var/run/mountd.pid out of the way and running the mount command. That should stop mount HUPing mountd, which would let you test this theory. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message