Mark Fasheh wrote: > AT_STRICT allows userspace to indicate that it wants the most up to date > version of a files status, regardless of performance impact. A distributed > file system which has a non-coherent inode cache would know then to send a > direct query to it's server. Good idea! Sort out some NFS pain. If a filesystem doesn't honour AT_STRICT, can we have the function return an error instead of stale values? I think AT_SYNC, AT_UPTODATE, AT_CURRENT or AT_NOW are clearer names than AT_STRICT, but it doesn't matter. Actually, all the names with AT_ are a bit silly, just because it happens to use the same flag space at the *at() syscalls. They don't have anything to do with "atness". What about calling these flags STAT_*? -- JAmie -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
