From owner-freebsd-questions Thu Sep 20 14:58:50 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.the-i-pa.com (mail.the-i-pa.com [151.201.71.132]) by hub.freebsd.org (Postfix) with SMTP id D06BC37B405 for ; Thu, 20 Sep 2001 14:58:47 -0700 (PDT) Received: (qmail 75191 invoked from network); 20 Sep 2001 22:09:26 -0000 Received: from unknown (HELO proxy.the-i-pa.com) (151.201.71.210) by mail.the-i-pa.com with SMTP; 20 Sep 2001 22:09:26 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Bill Moran Organization: Potential Technology To: Trevin Chow , Subject: Re: Flaky samba server Date: Thu, 20 Sep 2001 18:01:46 -0400 X-Mailer: KMail [version 1.2] References: <20010920132912.W50413-100000@benny.geektank.org> In-Reply-To: <20010920132912.W50413-100000@benny.geektank.org> MIME-Version: 1.0 Message-Id: <01092018014600.01333@proxy.the-i-pa.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thursday 20 September 2001 16:31, Trevin Chow wrote: > Does this indicate any problems that can be fixed? Yes. Consider turning oplocks off. It's a M$ problem, not samba, many M$ clients don't handle oplocks properly. Win95 is especially nasty with this, but I've heard (unconfirmed) rumors that the progeny of 95 (i.e. 98, ME, XP) have inherited those problems. Best bet, turn oplocks off totally on the samba server. See the samba docs. The performance loss doesn't seem to be very noticable, unless you've got a lot of file-based databases on the server, in which case, consider setting up MySQL and putting ODBC on the clients - that works very nicely! -- Bill Moran Potential Technology technical services (412) 793-4257 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message