On Nov 9, 2007 2:33 PM, Kris Buelens <[EMAIL PROTECTED]> wrote: > I added a trace myself and I think I understand: when you have some SFS > direcory accessed, and something changes in it (a file added/removed a Grant > affecting you), the SFS server tells you once "something has changed", > involving an EXT4000. The SFS client code will later pool the server to > find out what was changed. Once the server sent you such such a message, > other changes to that directory don't trigger another.
Yep. That's the thing that invalidates the in-core FST copies that CMS holds for local file pools. It conflicts a little with general VM design principles, but since the SFS server knows when the client got a copy again it is probably a fair trade-off. Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/
