From 12f2c006e0d3770c248bcfe2602580f5e6ff00ad Mon Sep 17 00:00:00 2001
From: Jeremy Allison <jra@samba.org>
Date: Thu, 9 Oct 1997 18:48:12 +0000
Subject: Added definition of oplocks parameter. Jeremy (jallison@whistle.com)
 (This used to be commit f9df5ac008e368af86addee058f75c7e79ca74ce)

---
 docs/manpages/smb.conf.5 | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

(limited to 'docs/manpages')

diff --git a/docs/manpages/smb.conf.5 b/docs/manpages/smb.conf.5
index 989a395c15..bb43941439 100644
--- a/docs/manpages/smb.conf.5
+++ b/docs/manpages/smb.conf.5
@@ -596,6 +596,8 @@ only guest
 
 only user
 
+oplocks
+
 path
 
 postexec
@@ -2236,6 +2238,22 @@ of the user.
 .B Example: 
 	only user = True
 
+.SS oplocks (S)
+This boolean option tells smbd whether to issue oplocks (opportunistic
+locks) to file open requests on this share. The oplock code was introduced in
+Samba 1.9.18 and can dramatically (approx 30% or more) improve the speed
+of access to files on Samba servers. It allows the clients to agressively
+cache files locally and you may want to disable this option for unreliable
+network environments (it is turned on by default in Windows NT Servers).
+For more information see the file Speed.txt in the Samba docs/ directory.
+
+.B Default:
+    oplocks = True
+
+.B Example:
+    oplocks = False
+
+
 .SS os level (G)
 This integer value controls what level Samba advertises itself as for
 browse elections. See BROWSING.txt for details.
-- 
cgit