From owner-freebsd-ports@FreeBSD.ORG Mon Oct 4 20:01:05 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 014E4106566B for ; Mon, 4 Oct 2010 20:01:05 +0000 (UTC) (envelope-from ml@netfence.it) Received: from cp-out7.libero.it (cp-out7.libero.it [212.52.84.107]) by mx1.freebsd.org (Postfix) with ESMTP id 8C8398FC19 for ; Mon, 4 Oct 2010 20:01:04 +0000 (UTC) Received: from soth.ventu (151.51.54.64) by cp-out7.libero.it (8.5.107) id 4C9778C301DE7278; Mon, 4 Oct 2010 22:00:31 +0200 Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.4/8.14.4) with ESMTP id o94K0Qio057176; Mon, 4 Oct 2010 22:00:26 +0200 (CEST) (envelope-from ml@netfence.it) Message-ID: <4CAA325A.6060506@netfence.it> Date: Mon, 04 Oct 2010 22:00:26 +0200 From: Andrea Venturoli User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; it-IT; rv:1.9.2.9) Gecko/20100917 Thunderbird/3.1.4 MIME-Version: 1.0 To: freebsd-ports@freebsd.org, rde@tavi.co.uk References: <4C9A6F48.6000107@netfence.it> <20100922225856.0891aee7@raksha.tavi.co.uk> In-Reply-To: <20100922225856.0891aee7@raksha.tavi.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.1.2.13 Cc: timur@freebsd.org, airlied@samba.org Subject: Re: Upgrading Samba 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 Oct 2010 20:01:05 -0000 On 09/22/10 23:58, Bob Eager wrote: Thanks for your answer. > My logbook says that it wanted to use /var/run/samba34 (a directory) > instead of the previous default. That was easy. In fact, yes, I too had to copy some files around, but that was more than easy. > Probably wasn't necessary, but I moved smbusers > to /usr/local/etc/samba34, and updated smb.conf. I did the same with smbpasswd. > Also that smbd wouldn't start because it needed the avahi-app package > (and dependencies) but this presumably wasn't listed as a dependency > because I had to install it by hand. No need for that in my case, but I didn't choose avahi in "make config". > I had to re-add the user rights for some reason - YMMV - this may be > the use of different directories for 3.4. Not sure what you mean. In any case, I had samba34 working in a little more than a few minutes, with users still accessing shares, XP machines still doing domain logons and the new W7 box integrated at first try. So far so good, it seemed, but it was not so. First, I noticed profiles could not be copied back on the server at logoff: a quick search pointed to full_audit being buggy and in fact removing it turned out to be the correct workaround. What I find strange is that it is deamed as not working in 3.4.7, but corrected in 3.4.8; this is evidently not true. Later I upgraded to 3.4.9, but had no time to test it again. I will ASAP and eventually report on the Samba newsgroup. The second problem is harder: pam_smb stopped working, so I had domain logons and file sharing ok, but any other service rejecting users. I could not come to any solution to this; I even tried pam_smbpass and setting up winbindd, but to no avail. Time was not on my side, so I ended up putting every password into the UNIX database and forget about PAM for the moment. However I'll have to fix this soon, so I'm in search of any hint on how to debug this. I tried putting "debug" next to pam_smb_auth.so in /etc/pam.d/*, but this didn't help much. Using Postgres (as an example) I get in my logs: xxxxxx pamsmbd[93053]: cache_check: no entry xxxxxx pamsmbd[93053]: server: remote auth user unix:yyyyy nt:yyyyy NTDOM:ZZZZZZ PDC:XXXXXX BDC:XXXXXX xxxxxx postgres[16385]: pamsmbd: Got something back... 3 xxxxxx pamsmbd[93053]: cache_check: no entry xxxxxx pamsmbd[93053]: server: remote auth user unix:yyyyy nt:yyyyy NTDOM:ZZZZZZ PDC:XXXXXX BDC:XXXXXX xxxxxx postgres[16387]: pamsmbd: Got something back... 3 but then: psql: FATAL: PAM authentication failed for user "yyyyy" FATAL: PAM authentication failed for user "yyyyy" In the meantime, I get absolutely nothing in /var/log/samba34/log.smbd. Any hint? bye & Thanks av.