From owner-freebsd-hackers Mon Jun 14 11: 3:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1FD2E1522E for ; Mon, 14 Jun 1999 11:03:30 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA11413; Mon, 14 Jun 1999 11:03:27 -0700 (PDT) (envelope-from dillon) Date: Mon, 14 Jun 1999 11:03:27 -0700 (PDT) From: Matthew Dillon Message-Id: <199906141803.LAA11413@apollo.backplane.com> To: Dag-Erling Smorgrav 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> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> 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 Sure. We could probably do the same thing we do for active binaries. It's pretty low on my list, though. -Matt Matthew Dillon :-- :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 : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message