Date: Sat, 11 Dec 1999 14:00:03 -0800 From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> To: Archie Cobbs <archie@whistle.com> Cc: abial@webgiro.com, freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree Message-ID: <91986.944949603@zippy.cdrom.com> In-Reply-To: Your message of "Sat, 11 Dec 1999 13:49:16 PST." <199912112149.NAA71033@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?91986.944949603>