From owner-freebsd-questions@FreeBSD.ORG Wed Nov 19 13:02:16 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 D474D16A4CE for ; Wed, 19 Nov 2003 13:02:16 -0800 (PST) Received: from mail.tsgincorporated.com (mail.tsgincorporated.com [67.66.242.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F3B343FEA for ; Wed, 19 Nov 2003 13:02:15 -0800 (PST) (envelope-from micheal@tsgincorporated.com) Received: (from root@localhost) by mail.tsgincorporated.com (8.12.8/8.12.8) id hAJL2D4r002558 for freebsd-questions@freebsd.org; Wed, 19 Nov 2003 15:02:13 -0600 (CST) (envelope-from micheal@tsgincorporated.com) Received: from micheal (micheal.tsgincorporated.com [67.66.242.77]) hAJL25Ec002528 for ; Wed, 19 Nov 2003 15:02:06 -0600 (CST) (envelope-from micheal@tsgincorporated.com) Message-ID: <0ef701c3aee0$638e18b0$4df24243@tsgincorporated.com> From: "Micheal Patterson" To: Date: Wed, 19 Nov 2003 15:02:02 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by AMaViS 0.3.12 Subject: Sharity Light -v- SMBFS 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, 19 Nov 2003 21:02:17 -0000 I've got an interesting issue that I'm having trouble locating anything on. Here's the situation. I've got a win2k server running IIS that keeps it's logs on a local drive. I'm running awstats from my fbsd server. Here's the glitch that I'm running into. If I use smbfs to access the shares so I can run awstats on the iis log files, I can't read the current log file if iis is running. However, if I run sharity light on the same share, I can then read the current file. At first glance, there appears to be a lock in place that smbfs honors whereas sharity light does not. I would prefer to use smbfs as it's internal to the os, and I'm mounting to a remote san connected to another windows server for my daily dump backups. I'd prefer not to have to use both of them to get the job done. Has anyone any information at all on just what is occuring here or is there something just plain simple that I'm missing? The smbfs mount is configured as noauto,rw in fstab. I can write to the slice, but just can't read the active server log file. Thanks. -- Micheal Patterson TSG Network Administration 405-917-0600 Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.