From owner-freebsd-questions@FreeBSD.ORG Mon Jul 14 19:27:20 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 49F4137B401 for ; Mon, 14 Jul 2003 19:27:20 -0700 (PDT) Received: from alpsgiken.alpsgiken.gr.jp (www.alpsgiken.gr.jp [210.166.150.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFA8143F75 for ; Mon, 14 Jul 2003 19:27:18 -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 LAA09623 for ; Tue, 15 Jul 2003 11:27:16 +0900 Date: Tue, 15 Jul 2003 11:30:08 +0900 From: Joel Rees To: Free BSD Questions list In-Reply-To: <20030715001127.GB29352@teddy.fas.com> References: <3F134373.2060808@mac.com> <20030715001127.GB29352@teddy.fas.com> Message-Id: <20030715105147.87DF.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 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: Tue, 15 Jul 2003 02:27:20 -0000 > > >The tail -f works fine, but the application on the Windows side that should > > >be appending data to this file (think syslog like functionality) pops up an > > >error message about not being able to write to the file. > > > > > >I've mounted the share as read only, > > > > Um, why are you expecting the Windows application to be able to append to a > > file on a read-only Samba share? > > > The Samba filesystem is ON the windows box. it's whatever FS os on that > machine. I'm just mounting it via Samab. So, the read only semantics apply > to the FreeBSD side only. 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. -- Joel Rees, programmer, Kansai Systems Group Altech Corporation (Alpsgiken), Osaka, Japan http://www.alpsgiken.co.jp