From owner-freebsd-questions@FreeBSD.ORG Thu Jul 3 05:39:22 2008 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 B6E361065677 for ; Thu, 3 Jul 2008 05:39:22 +0000 (UTC) (envelope-from unga888@yahoo.com) Received: from web57008.mail.re3.yahoo.com (web57008.mail.re3.yahoo.com [66.196.97.112]) by mx1.freebsd.org (Postfix) with SMTP id 682CE8FC19 for ; Thu, 3 Jul 2008 05:39:22 +0000 (UTC) (envelope-from unga888@yahoo.com) Received: (qmail 72391 invoked by uid 60001); 3 Jul 2008 05:39:21 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=0OQIHxnNsJk0xJcTTWNAUx3wyZpkoJFZ4bXuv+PNZG6GuPM43BvsNzgHPfWPrFxC64Vedxu3nO2ZynnS8kVXX6Ft0+vzEXo5XQQbjoSh6Gj6yb9uVOq3zSSxw2B2aqWjnrU1wjvIB1JBJLp/n3Ag1BhDqCfobG4hiPYqQvfkOD4=; Received: from [165.21.155.114] by web57008.mail.re3.yahoo.com via HTTP; Wed, 02 Jul 2008 22:39:21 PDT X-Mailer: YahooMailWebService/0.7.199 Date: Wed, 2 Jul 2008 22:39:21 -0700 (PDT) From: Unga To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <641564.72137.qm@web57008.mail.re3.yahoo.com> Subject: Getting PAM up inside chroot issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: unga888@yahoo.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 05:39:22 -0000 Hi all I'm trying to getting PAM up inside a chroot. I'm using FreeBSD 7.0 on i386. su -l shows following error: su: pam_start: system error strace su -l shows following failures: access("/etc/localtime", R_OK) = 0 open("/etc/localtime", O_RDONLY) = 4 fstat(4, {st_mode=S_IFLNK|S_ISGID|052, st_size=18445798717047743530, ...}) = 0 read(4, "3\244\374\377*\244\374\3773\244\374\3773\244\374\3773\244"..., 7944) = 171 close(4) = 0 socket(PF_UNIX, SOCK_DGRAM, 0) = 4 fcntl(4, F_SETFD, FD_CLOEXEC) = 0 connect(4, {sa_family=0xa4 /* AF_??? */, sa_data="\374\377\\[x\0%02x\0%1x"}, 106) = -1 ENOENT (No such file or directory) connect(4, {sa_family=0x2f /* AF_??? */, sa_data="ystem call\0Inp"}, 106) = -1 ENOENT (No such file or directory) connect(4, {sa_family=0x74 /* AF_??? */, sa_data="d processes\0Re"}, 106) = -1 ENOENT (No such file or directory) close(4) = 0 sendto(-1, "source deadlock avoided\0Cannot a"..., 72, 0, NULL, 0) = -1 EBADF (Bad file descriptor) socket(PF_UNIX, SOCK_DGRAM, 0) = 4 fcntl(4, F_SETFD, FD_CLOEXEC) = 0 connect(4, {sa_family=0x6c /* AF_??? */, sa_data="nk\0\0\0\0Operatio"}, 106) = -1 ENOENT (No such file or directory) There is no failure up to reading the /etc/localtime. This shows the socket (fd=4) disappeared before the connect. What am I still missing in my chroot? Where does this socket get created? is it the current directory where su initiated or somewhere else? Appreciate your help to identify the cause. Kind regards Unga