Date: 14 Jun 1999 11:31:32 +0200 From: Dag-Erling Smorgrav <des@flood.ping.uio.no> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Joel Ray Holveck <joelh@gnu.org>, freebsd-hackers@FreeBSD.ORG Subject: Re: vn swapfiles deleted while in use Message-ID: <xzpk8t7f7rf.fsf@flood.ping.uio.no> In-Reply-To: Matthew Dillon's message of "Mon, 14 Jun 1999 00:01:26 -0700 (PDT)" References: <86vhcr3bav.fsf@detlev.UUCP> <199906140701.AAA06746@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Dillon <dillon@apollo.backplane.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpk8t7f7rf.fsf>