From owner-freebsd-ports Sat Sep 15 7:51: 6 2001
Delivered-To: freebsd-ports@freebsd.org
Received: from pc1-cove4-0-cust214.bir.cable.ntl.com (pc1-cove4-0-cust214.bir.cable.ntl.com [213.105.93.214])
by hub.freebsd.org (Postfix) with ESMTP
id 4C60037B408; Sat, 15 Sep 2001 07:51:03 -0700 (PDT)
Received: from ntlworld.com (alpha.private [192.168.0.2])
(authenticated)
by pc1-cove4-0-cust214.bir.cable.ntl.com (8.11.3/8.11.3) with ESMTP id f8FEoxm32696
(using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO);
Sat, 15 Sep 2001 15:51:01 +0100 (BST)
(envelope-from ianjhart@ntlworld.com)
Message-ID: <3BA36AD3.1AC260A@ntlworld.com>
Date: Sat, 15 Sep 2001 15:50:59 +0100
From: ian j hart <ianjhart@ntlworld.com>
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ports@FreeBSD.ORG, dwcjr@FreeBSD.ORG
Subject: Re: samba oplocks (was samba PDC / kernel tuning)
References: <3B9FE85A.4D33E107@ntlworld.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-ports.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-ports>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-ports>
X-Loop: FreeBSD.org
kernel oplocks (from stable)
Either the docs or the value in smb.conf.default is wrong. This
is what had me confused. From the (html) docs.
<quote>
kernel oplocks (G)
For UNIXes that support kernel based oplocks (currently
only IRIX and the Linux 2.4 kernel), this parameter allows
the use of them to be turned on or off.
Kernel oplocks support allows Samba oplocks to be broken
whenever a local UNIX process or NFS operation accesses a
file that smbd(8) has oplocked. This allows complete data
consistency between SMB/CIFS, NFS and local file access
(and is a very cool feature :-).
=> This parameter defaults to on on systems that have the
support, and off on systems that don't. You should never
need to touch this parameter.
See also the oplocks and level2 oplocks parameters.
=>? Default: kernel oplocks = yes
</quote>
Defaults to yes, but we don't have this feature (yet).
--
ian j hart
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message