From owner-freebsd-hackers Thu Nov 9 12: 8:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from linus.dvart.com (linus.dvart.com [64.79.2.3]) by hub.freebsd.org (Postfix) with ESMTP id 0B55337B479 for ; Thu, 9 Nov 2000 12:08:15 -0800 (PST) Received: from dvart.com ([192.168.100.141]) by linus.dvart.com (8.9.3/8.9.3) with ESMTP id MAA23812; Thu, 9 Nov 2000 12:08:11 -0800 Message-ID: <3A0B042B.BAABCBDE@dvart.com> Date: Thu, 09 Nov 2000 12:08:11 -0800 From: bruno schwander X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: close call in a device ? References: <200011091827.LAA22910@usr08.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you infinitely for all this information. It will take me a while to absorb and poke around in the right places but this is definitely extremely useful, thank you. I will most probably come back to you with more questions, in a near future time... bruno Terry Lambert wrote: > > > To add to this, the close calls can be forces; there is a flag > > > in the device structure wich can force notification. I'm not > > > sure what it does over a fork(), though: I think you really want > > > open notification. > > > > You mean that when I register my device/kernel module, I can > > explicitely request that all close calls will notify my module? > > That is exactly what I need. > > Add D_TRACKCLOSE to d_flags for your device. When the d_close() > of your device is call, the first arg is the dev. > snip ... much much more .... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message