From owner-freebsd-questions@FreeBSD.ORG Tue Jul 15 19:27:41 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 549CA37B401 for ; Tue, 15 Jul 2003 19:27:41 -0700 (PDT) Received: from alpsgiken.alpsgiken.gr.jp (www.alpsgiken.gr.jp [210.166.150.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAEAF43F75 for ; Tue, 15 Jul 2003 19:27:39 -0700 (PDT) (envelope-from joel@alpsgiken.alpsgiken.gr.jp) Received: from zz_radiant2 (www1.alpsgiken.gr.jp [61.114.244.165]) by alpsgiken.alpsgiken.gr.jp (8.9.1a/3.7W) with ESMTP id LAA17251; Wed, 16 Jul 2003 11:27:37 +0900 Date: Wed, 16 Jul 2003 11:30:30 +0900 From: Joel Rees To: freebsd-questions@freebsd.org In-Reply-To: <20030715105147.87DF.JOEL@alpsgiken.gr.jp> References: <20030715001127.GB29352@teddy.fas.com> <20030715105147.87DF.JOEL@alpsgiken.gr.jp> Message-Id: <20030716112109.19F7.JOEL@alpsgiken.gr.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.00.11 cc: stan Subject: Re: Problems with Samba shared files X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 02:27:41 -0000 > 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.) -- Joel Rees, programmer, Kansai Systems Group Altech Corporation (Alpsgiken), Osaka, Japan http://www.alpsgiken.co.jp