From owner-freebsd-current@FreeBSD.ORG Sun Aug 10 07:44:53 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCE2C37B401; Sun, 10 Aug 2003 07:44:53 -0700 (PDT) Received: from accms33.physik.rwth-aachen.de (accms33.physik.RWTH-Aachen.DE [137.226.46.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63B2843F75; Sun, 10 Aug 2003 07:44:52 -0700 (PDT) (envelope-from kuku@accms33.physik.rwth-aachen.de) Received: (from kuku@localhost) by accms33.physik.rwth-aachen.de (8.11.6/8.9.3) id h7AEip203204; Sun, 10 Aug 2003 16:44:51 +0200 Date: Sun, 10 Aug 2003 16:44:51 +0200 From: "Christoph P. Kukulies" To: Robert Watson Message-ID: <20030810144451.GA3112@gilberto.physik.rwth-aachen.de> References: <200308101338.h7ADcnO02356@accms33.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i cc: Christoph Kukulies cc: freebsd-current@freebsd.org Subject: Re: openpam_load_module():no pam_wheel.so found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Aug 2003 14:44:54 -0000 On Sun, Aug 10, 2003 at 10:08:15AM -0400, Robert Watson wrote: > > On Sun, 10 Aug 2003, Christoph Kukulies wrote: > > > When I do an su command from a normal user on my 5.1-current of > > yesterday I'm getting a segfault/core dump. > > > > /var/log/messages then shows: > > Aug 10 15:27:44 kukuboo2k su: in openpam_load_module(): no pam_wheel.so found > > Aug 10 15:27:44 kukuboo2k kernel: pid 54586 (su), uid 0: exited on signal 10 (core dumped) > > > > I also get this when I try to do a sh /etc/periodic/weekly/310.locate. > > > > I almost there again with 5.1-current and X on my notebook after a disk > > crash and data loss. Compiled the XFree86-4.3.1 tree and NVIDIA drivers > > today after a complete cvsup and kernel build yesterday. > > Did you mergemaster when updating last? pam_wheel has, I believe, been No, I wasn't aware of mergemaster existing at all. :-) > replaced with pam_group. A coredump is an undesirable result, of course, > but I suspecft that this is the trigger. If you want to follow up on the > core dump, build a copy of su with debugging symbols, and enable > kern.sugid_coredump to get a coredump and stack tracfe from su (turn it > off again when done). I compiled su with -g and ran did a sysctl -w kern.sugid_coredump=1 ran ./su again but get no backtrace. I get a Bus error btw, not segfault. -- Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de