Opportunistic locks, or
oplocks, allow clients to cache files locally, improving performance on the order of 30 percent. This option is now enabled by default. For read-only files, the
fake
oplocks provides the same functionality without actually doing any caching. If you have files that cannot be cached,
oplocks can be turned off.
Database files should never be cached, nor should any files that are updated both on the server and the client and whose changes must be immediately visible. For these files, the
veto
oplock
files option allows you to specify a list of individual files or a pattern containing wildcards to avoid caching.
oplocks can be turned off on a share-by-share basis if you have large groups of files you don't want cached on clients. See Chapter 5,
Browsing and Advanced Disk Shares , for more information on opportunistic locks.
