On 11-Dec-99 Jordan K. Hubbard wrote:
>> 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.
Perhaps a modtime on the sysctl tree as a gross hack? Inside of sysctl() and
the SYSCTL() macros you would update the time every time a write was made, node
added, node removed, etc. However, it is a gross hack.
> - Jordan
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
