From owner-freebsd-questions@FreeBSD.ORG Wed Jul 16 04:14:32 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8F1337B401 for ; Wed, 16 Jul 2003 04:14:32 -0700 (PDT) Received: from mail3.panix.com (mail3.panix.com [166.84.1.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id B37F643F3F for ; Wed, 16 Jul 2003 04:14:31 -0700 (PDT) (envelope-from stanb@panix.com) Received: from panix.com (brillig.panix.com [166.84.1.76]) by mail3.panix.com (Postfix) with ESMTP id 0D50B983FB; Wed, 16 Jul 2003 07:14:31 -0400 (EDT) Received: from teddy.fas.com (pcp01010374pcs.mplsnt01.sc.comcast.net [68.58.176.69]) by panix.com (Postfix) with ESMTP id E14C92AA3D; Wed, 16 Jul 2003 07:14:30 -0400 (EDT) Received: from stan by teddy.fas.com with local (Exim 3.36 #1 (Debian)) id 19ckEw-00017l-00; Wed, 16 Jul 2003 07:14:30 -0400 Date: Wed, 16 Jul 2003 07:14:30 -0400 From: stan To: Joel Rees Message-ID: <20030716111430.GB4278@teddy.fas.com> Mail-Followup-To: Joel Rees , Free BSD Questions list References: <20030715001127.GB29352@teddy.fas.com> <20030715105147.87DF.JOEL@alpsgiken.gr.jp> <20030716112109.19F7.JOEL@alpsgiken.gr.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030716112109.19F7.JOEL@alpsgiken.gr.jp> X-Editor: gVim X-Operating-System: Debian GNU/Linux X-Kernel-Version: 2.4.21 X-Uptime: 07:12:15 up 29 days, 18:14, 2 users, load average: 0.02, 0.02, 0.00 User-Agent: Mutt/1.5.4i Sender: Stan Brown cc: Free BSD Questions list Subject: Re: Problems with Samba shared files X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 11:14:33 -0000 On Wed, Jul 16, 2003 at 11:30:30AM +0900, Joel Rees wrote: > > Hmm. I would either think it a bug for Samba to be unable to tell > > MSWindows that it had a file open for read, or a rather advanced > > technique for Samba to be able to understand from simply mounting the > > share as read-only that it could let MSWindows forego a lock on a > > multiply opened file. > > > > Mayb I'm just confused. > > Confused, yes, the man is confused! > > I guess I should have visited > > http://www.samba.org and > http://www.oreilly.com/catalog/samba/chapter/book/ch05_05.html > > and a few other places before I started dissing MSWindows. Now I know > about oplocks, I can diss MSW with real meaning. What were they thinking? > > But that doesn't help anyone. > > Stan, check your smb.conf and your samba logs. That should get you > headed in the right direction. > > (Hopefully, your problem has nothing to do with opportunistic locking.) > Thanks for the pointers! -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin