HP CIFS Client A.02.02 Administrator's Guide

Configuration File
Configuration Parameters
Chapter 7 125
lock
The number of pages to read ahead if an oplock was
granted.
noLock
The number of pages to read ahead of no oplock was
granted.
useWriteBack This variable defines whether cache write- back
techniques should be used. Write back is insecure (in
terms of error recovery) if used with NFS2, but it may
increase performance notably. The value is a dictionary
with the following keys:
lock
Boolean value which configures whether write back
should be used when an oplock has been granted.
noLock
Boolean value which configures whether write back
should be used when no oplock has been granted.
If you care about reliability, always leave these options
off. This configuration variable is also passed to the
server. There are server/OS combinations (notably
Samba/Linux) which become very slow in write-
through mode. You may want to configure write back
for these.
requestOplock This boolean variable defines whether oplocks should
be requested from the server. It should be set to no for
Windows 95 machines because they grant an oplock
although there is no support for it.
closeForSetattr This boolean variable defines whether files should be
closed before attributes (write protection, modification
dates) are changed. This is very useful for Windows 95
servers because these servers can not set the attributes
of open files. However, with this feature enabled, the
UNIX semantics mapping does not work completely.
The default is no.