From owner-freebsd-current Sat Dec 11 13:59:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BA98C14BE4 for ; Sat, 11 Dec 1999 13:59:47 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA91990; Sat, 11 Dec 1999 14:00:04 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Archie Cobbs Cc: abial@webgiro.com, freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree In-reply-to: Your message of "Sat, 11 Dec 1999 13:49:16 PST." <199912112149.NAA71033@bubba.whistle.com> Date: Sat, 11 Dec 1999 14:00:03 -0800 Message-ID: <91986.944949603@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In other words, it's not a problem specific to KLD's .. but > it's still a problem :-) Which raises an important issue - other than walking the sysctl tree regularly looking for changes, how does such an application become aware that the sysctl space has changed? The same holds true for a dynamic /dev, of course, though one assumes one can at least hack a solution with devfs where you stat the directory and compare its current mod time with a saved one, only walking the directory if you see a change. I don't see any kind of mechanism for doing this with sysctl, even as a gross hack. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message