From owner-freebsd-ports@FreeBSD.ORG Mon Sep 4 21:22:16 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C294F16A4DA for ; Mon, 4 Sep 2006 21:22:16 +0000 (UTC) (envelope-from craig@yekse.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52B0F43D46 for ; Mon, 4 Sep 2006 21:22:14 +0000 (GMT) (envelope-from craig@yekse.gank.org) Received: by ion.gank.org (Postfix, from userid 1001) id 9FFD91105C; Mon, 4 Sep 2006 16:22:13 -0500 (CDT) Date: Mon, 4 Sep 2006 16:22:11 -0500 From: Craig Boston To: Lee Dilkie Message-ID: <20060904212211.GA26914@nowhere> Mail-Followup-To: Craig Boston , Lee Dilkie , ports@freebsd.org References: <44F9DF50.6020104@dilkie.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44F9DF50.6020104@dilkie.com> User-Agent: Mutt/1.4.2.2i Cc: ports@freebsd.org Subject: Re: Samba upgrade, users cannot connect X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2006 21:22:16 -0000 On Sat, Sep 02, 2006 at 03:45:20PM -0400, Lee Dilkie wrote: > Anyway, I cannot connect to a share anymore. Correction. I can connect > to a share that has "users = somelogonid" but connecting to a share that > has "users = @agroup" fails. Samba seems to be deteriorating with each release. I'm not sure how much is a Samba issue and how much is a FreeBSD ports issue. Here's my current set of workarounds in rough chronological order of when I started using them. You may want to give some of them a try in your samba config and see if it helps... I'd try the "fam change notify = no" first since you mentioned FAM errors, but it doesn't sound like the same symptoms that I had. I see that the 3.0.23c commit message mentions something about changes to "valid users", so I suspect I may have to add yet another workaround when I upgrade to it. Craig ------ smb.conf ------ # (circa 2004) # Something broke with oplocks between Samba 2.x and Samba 3.x # Anything that uses Installshield will fail to install from a samba # share, dying with a cryptic error message. Use with caution on # readwrite shares fake oplocks = yes locking = no # 8/16/2006 # Samba uses FAM now, but it's broken. Lots of errors about being # unable to launch gamin and long delays connecting to shares. Polling # works good enough, just shut it off. fam change notify = no # 8/28/2006 # Apparently Samba now defaults everything to being a DFS root whether # you're using DFS or not. Software installs via group policy # mysteriously fail claiming they're unable to find the source when the # installation source is a DFS root. Revert to previous default. host msdfs = no