Currently we gather this data via client side code doing ordinary tree walking. Hideous execution time as you might expect, not to mention server and network impact. We know it can be done on the server instead by parsing the volume headers and snagging the raw inodes. We have pointers to some code that leads in that direction, but it leaves much to the imagination and a lot of work to be done. We'd much rather be Lazy. Has anyone done anything like this already or knows someone else who has?
--
Peter Scott
[EMAIL PROTECTED]
_______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
