search for: casuistic

>>Wait -- this is supposed to still work, and I have a lot of customers that do exactly that. >>"vfs objects" in [global] that applies to all shares then. I just tested it. It works until you put some other vfs module in some share. Then it ceases to work, you have to declare it for all shares. This works: [global] vfs objects = acl_xattr [share] /some/path This does

...are B, that other one for share C. This was the previous behavior and it was VERY convenient. Plus, it respected the general principle of "global (G) parameters work in [global] and share (S) parameters work both in (S) and in (G)". This is very clear. The current situation opens a can of casuistic worms, where instead of a simple general principle you will have to specify casuistically where each of the particular parameters work and don't work. AND even if the change is an acceptable one, then it needs to be documented clearly, wouldn't you think?