The thought occurred to me as I was doing this. Do you have anything in
mind? The capabilities prototype (which I'm not sure has been reviewed
yet closely, either) could be said to overlap in its present form (eg,
you can ask it for "rxk5.enctypes", and figure there would be other
"rxk5.stuff", so you can search on a wildcard (eg, "rxk5.*"), and it
will send back lists of values. Remember this started as your
suggestion of a pioctl to report the enctypes a cache manager supports.
But Marcus suggested we make it more general. Right now it just reports
information, doesn't provide any framework for registering generic info
from userland (otoh, from inside the cache manager, you register your
named property with the capabilities interface).
Matt
Jeffrey Hutzelman wrote:
On the other hand, there's also something to be said for adding a more
general interface for toggling optional features, instead of inventing
a new pioctl every time.
-- Jeff
--
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI 48104
http://linuxbox.com
tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
