sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-03-12 20:58:37 +03:00
Code

- added docs on the new "fake oplocks" option.

Browse Source
This commit is contained in:
Andrew Tridgell -
parent 61e3116e57
commit 1303132113
2 changed files with 53 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
docs/manpages/smb.conf.5
View File

@ -472,6 +472,8 @@ dont descend
exec
fake oplocks
force group
force user
@ -1569,6 +1571,31 @@ of the user.
.B Example:
only user = True
.SS fake oplocks (S)
Oplocks are the way that SMB clients get permission from a server to
locally cache file operations. If a server grants an oplock
(opportunistic lock) then the client is free to assume that it is the
only one accessing the file and it will agressively cache file
data. With some oplock types the client may even cache file open/close
operations. This can give enormous performance benefits.
Samba does not support opportunistic locks because they are very
difficult to do under Unix. Samba can fake them, however, by granting
a oplock whenever a client asks for one. This is controlled using the
smb.conf option "fake oplocks". If you set "fake oplocks = yes" then
you are telling the client that it may agressively cache the file
data.
By enabling this option on all read-only shares or shares that you know
will only be accessed from one client at a time you will see a big
performance improvement on many operations. If you enable this option
on shares where multiple clients may be accessing the files read-write
at the same time you can get data corruption. Use this option
carefully!
This option is disabled by default.
.SS message command (G)
This specifies what command to run when the server receives a WinPopup

26
docs/textdocs/Speed.txt
View File

@ -30,6 +30,32 @@ hardware Samba should certainly be competitive in speed with other
systems.
OPLOCKS
-------
Oplocks are the way that SMB clients get permission from a server to
locally cache file operations. If a server grants an oplock
(opportunistic lock) then the client is free to assume that it is the
only one accessing the file and it will agressively cache file
data. With some oplock types the client may even cache file open/close
operations. This can give enormous performance benefits.
Samba does not support opportunistic locks because they are very
difficult to do under Unix. Samba can fake them, however, by granting
a oplock whenever a client asks for one. This is controlled using the
smb.conf option "fake oplocks". If you set "fake oplocks = yes" then
you are telling the client that it may agressively cache the file
data.
By enabling this option on all read-only shares or shares that you know
will only be accessed from one client at a time you will see a big
performance improvement on many operations. If you enable this option
on shares where multiple clients may be accessing the files read-write
at the same time you can get data corruption. Use this option
carefully!
This option is disabled by default.
SOCKET OPTIONS
--------------