From owner-freebsd-hackers Mon Jun 14 2:31:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 9FDE414D70 for ; Mon, 14 Jun 1999 02:31:40 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id LAA60869; Mon, 14 Jun 1999 11:31:33 +0200 (CEST) (envelope-from des) To: Matthew Dillon Cc: Joel Ray Holveck , freebsd-hackers@FreeBSD.ORG Subject: Re: vn swapfiles deleted while in use References: <86vhcr3bav.fsf@detlev.UUCP> <199906140701.AAA06746@apollo.backplane.com> From: Dag-Erling Smorgrav Date: 14 Jun 1999 11:31:32 +0200 In-Reply-To: Matthew Dillon's message of "Mon, 14 Jun 1999 00:01:26 -0700 (PDT)" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > On the otherhand, if you *truncate* the file or unconfigure the > vn node, you will blow the system up when the system tries > to swap something in or out on that file. Is there any possibility of adding a reference count to the vn device so it can't be unconfigured if it's still referenced? Is there any possibility of implementing a compulsory (as opposed to advisory) file locking system, so vn swapfiles can't be truncated or written to by any other process while it's in use? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message