Date: Sun, 10 Aug 2003 10:08:15 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Christoph Kukulies <kuku@physik.rwth-aachen.de> Cc: freebsd-current@freebsd.org Subject: Re: openpam_load_module():no pam_wheel.so found Message-ID: <Pine.NEB.3.96L.1030810100635.15658A-100000@fledge.watson.org> In-Reply-To: <200308101338.h7ADcnO02356@accms33.physik.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1030810100635.15658A-100000>