From owner-freebsd-stable Wed Sep 12 17: 7:33 2001 Delivered-To: freebsd-stable@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 8C35837B40D for ; Wed, 12 Sep 2001 17:07:27 -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 f8D07Mm21577 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Thu, 13 Sep 2001 01:07:24 +0100 (BST) (envelope-from ianjhart@ntlworld.com) Message-ID: <3B9FF8BA.F53AE81@ntlworld.com> Date: Thu, 13 Sep 2001 01:07:22 +0100 From: ian j hart X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "David W. Chapman Jr." Cc: "stable@FreeBSD.ORG" Subject: Re: kernel oplocks References: <3B9FE8D6.40EBB7E@ntlworld.com> <20010912180539.B75181@leviathan.inethouston.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "David W. Chapman Jr." wrote: > > On Wed, Sep 12, 2001 at 11:59:34PM +0100, ian j hart wrote: > > Samba now comes configured with kernel oplocks enabled by > > default, implying this is part of the kernel. Can someone > > confirm the status of this. ie is it established, or is it > > a new feature. I wouldn't mind knowing where the source is. > > A quick search revealed nothing. > > > I do not believe our kernel supports this in version 4.4 of FreeBSD, > but you said you had problems even when you turned this off. That's in the other post (ports). To clarify for stable readers. [part quote] Got the server running okay. Now I'm getting "no response received to oplock break request..." [mostly the logon.bat file] [snip] This goes away if I disable oplocks (no really), but this causes some clients to fail to load the logon.bat file. This is a major problem as all the shares load via 'net use'. [end quote] When the client cannot lock the file it bails out. I'm not sure this is wrong, as I'm not a lock expert. I think when you disable oplocks it should request and wait for a _normal_ lock. > The > oplocks setting of "ON" should simply not work if you actually don't > have oplocks support. Sounds like a bug in samba, what version are > you using? I agree with both statements. It's 4.4-RC + samba 2.2.1a_2 Thanks again for the super quick reply. > > -- > David W. Chapman Jr. > dwcjr@inethouston.net Raintree Network Services, Inc. > dwcjr@freebsd.org FreeBSD Committer -- ian j hart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message