Date: Mon, 11 Aug 2003 15:35:47 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: "Christoph P. 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.1030811153429.66226G-100000@fledge.watson.org> In-Reply-To: <20030811193158.GA17695@gilberto.physik.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 11 Aug 2003, Christoph P. Kukulies wrote: > > 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). > > How can I find out which module is using pam_wheel.so? It is annoying > not to have a functioning 'su'. Since locate updatedb uses su also I'm > additionally impeded since I cannot locate libs and stuff efficiently. grep pam_wheel /etc/pam.d/* | grep -v '^#' should show you the list. 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.1030811153429.66226G-100000>