From owner-freebsd-questions@FreeBSD.ORG Fri Apr 20 19:11:24 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFC531065672 for ; Fri, 20 Apr 2012 19:11:24 +0000 (UTC) (envelope-from clarkjp@charter.net) Received: from mail.cluebytwelve.org (clueby12.org [198.186.190.239]) by mx1.freebsd.org (Postfix) with ESMTP id 7AFD18FC0C for ; Fri, 20 Apr 2012 19:11:24 +0000 (UTC) Received: from localdomain.local (24-158-157-74.dhcp.jcsn.tn.charter.com [24.158.157.74]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cluebytwelve.org (Postfix) with ESMTPSA id 43CCE1B5D9 for ; Fri, 20 Apr 2012 15:03:30 -0400 (EDT) Received: by localdomain.local (Postfix, from userid 1001) id DC0774504E; Fri, 20 Apr 2012 14:03:31 -0500 (CDT) Date: Fri, 20 Apr 2012 14:03:31 -0500 From: "J. Porter Clark" To: freebsd-questions@freebsd.org Message-ID: <20120420190331.GA84130@auricle.charter.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: http://www.angelfire.com/ego/porterclark/ User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Samba 3.6.4 winbindd X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Apr 2012 19:11:25 -0000 Has anyone out there gotten winbindd from Samba 3.6.anything to work on FreeBSD 9.0-STABLE? It starts up with no obvious problems--although with Samba's usual cryptic error messages it's hard for me to tell--and then just sits there doing nothing. Wbinfo commands time out and pam_winbind.so doesn't work. When I run /usr/local/etc/rc.d/samba stop, it hangs waiting for winbindd to die, and I have to kill -KILL winbindd. I'm using security = domain. Other settings, logs, etc. available upon request. I've had to drop back to Samba 3.5.14_1 to get most things to work, but I really need to go to 3.6.* for the NTLMv2 support. -- J. Porter Clark