From d90a4ea71a17f22b9d65462189d6e074b4fa9e6e Mon Sep 17 00:00:00 2001 From: Alexander Bokovoy Date: Fri, 11 Apr 2003 15:01:39 +0000 Subject: Finish conversion of Locking options (This used to be commit 9613c217786147c9deda9770887dc069659b1deb) --- docs/docbook/smbdotconf/locking/level2oplocks.xml | 66 ++++++++++++----------- 1 file changed, 34 insertions(+), 32 deletions(-) (limited to 'docs/docbook/smbdotconf/locking/level2oplocks.xml') diff --git a/docs/docbook/smbdotconf/locking/level2oplocks.xml b/docs/docbook/smbdotconf/locking/level2oplocks.xml index adae6d268f..c2c090b1a8 100644 --- a/docs/docbook/smbdotconf/locking/level2oplocks.xml +++ b/docs/docbook/smbdotconf/locking/level2oplocks.xml @@ -1,39 +1,41 @@ - - level2 oplocks (S) - This parameter controls whether Samba supports - level2 (read-only) oplocks on a share. + + + This parameter controls whether Samba supports + level2 (read-only) oplocks on a share. - Level2, or read-only oplocks allow Windows NT clients - that have an oplock on a file to downgrade from a read-write oplock - to a read-only oplock once a second client opens the file (instead - of releasing all oplocks on a second open, as in traditional, - exclusive oplocks). This allows all openers of the file that - support level2 oplocks to cache the file for read-ahead only (ie. - they may not cache writes or lock requests) and increases performance - for many accesses of files that are not commonly written (such as - application .EXE files). + Level2, or read-only oplocks allow Windows NT clients + that have an oplock on a file to downgrade from a read-write oplock + to a read-only oplock once a second client opens the file (instead + of releasing all oplocks on a second open, as in traditional, + exclusive oplocks). This allows all openers of the file that + support level2 oplocks to cache the file for read-ahead only (ie. + they may not cache writes or lock requests) and increases performance + for many accesses of files that are not commonly written (such as + application .EXE files). - Once one of the clients which have a read-only oplock - writes to the file all clients are notified (no reply is needed - or waited for) and told to break their oplocks to "none" and - delete any read-ahead caches. + Once one of the clients which have a read-only oplock + writes to the file all clients are notified (no reply is needed + or waited for) and told to break their oplocks to "none" and + delete any read-ahead caches. - It is recommended that this parameter be turned on - to speed access to shared executables. + It is recommended that this parameter be turned on to + speed access to shared executables. - For more discussions on level2 oplocks see the CIFS spec. + For more discussions on level2 oplocks see the CIFS spec. - Currently, if kernel - oplocks are supported then level2 oplocks are - not granted (even if this parameter is set to yes). - Note also, the oplocks - parameter must be set to yes on this share in order for - this parameter to have any effect. + Currently, if kernel + oplocks are supported then level2 oplocks are + not granted (even if this parameter is set to yes). + Note also, the oplocks + parameter must be set to yes on this share in order for + this parameter to have any effect. - See also the oplocks - and kernel oplocks - parameters. + See also the oplocks + and kernel oplocks + parameters. - Default: level2 oplocks = yes - - + Default: level2 oplocks = yes + + -- cgit