Date: Mon, 11 Aug 2003 22:27:35 +0200 From: "Christoph P. Kukulies" <kuku@physik.rwth-aachen.de> To: Robert Watson <rwatson@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: openpam_load_module():no pam_wheel.so found Message-ID: <20030811202735.GA18591@gilberto.physik.rwth-aachen.de> In-Reply-To: <Pine.NEB.3.96L.1030810100635.15658A-100000@fledge.watson.org> References: <200308101338.h7ADcnO02356@accms33.physik.rwth-aachen.de> <Pine.NEB.3.96L.1030810100635.15658A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > > > > Did you mergemaster when updating last? pam_wheel has, I believe, been > 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). Thanks again for the intermediate help (to look in /etc/pam.d) and this directory didn't get updated. There was the old 5.0 stuff in it. Now su works again. -- Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030811202735.GA18591>