mirror of
https://github.com/facebook/sapling.git
synced 2024-10-09 08:18:15 +03:00
8391057f7d
Summary: An NFS client caches the attributes of files to avoid having to request these very frequently. What this means is that a file changed by another client (or by the server itself) may take some time to be reflected on the client, that time depends on the attribute caching configuration of the mount point. For EdenFS, files can changed in 2 ways: - Either it is changed by the user via the mount point, - Or the user runs an `hg update` For the first one, the client will simply update its attributes appropriately, but for the second one, the cached attributes will only be updated when the user does opens the file, any calls to stat prior will return the old attributes. Since EdenFS runs on the same host, we can force the attributes caches to be discarded by simply issuing an open call on the file that changed. Reviewed By: chadaustin Differential Revision: D28456482 fbshipit-source-id: 91022d35a33e436c47d94403d0c139992f880cf9 |
||
|---|---|---|
| .. | ||
| benchharness | ||
| benchmarks | ||
| cli | ||
| cli_rs | ||
| config | ||
| docs | ||
| fuse | ||
| inodes | ||
| journal | ||
| model | ||
| monitor | ||
| nfs | ||
| notifications | ||
| prjfs | ||
| py | ||
| rocksdb | ||
| scripts | ||
| service | ||
| sqlite | ||
| store | ||
| takeover | ||
| telemetry | ||
| testharness | ||
| third-party | ||
| utils | ||
| CMakeLists.txt | ||