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 > 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. -- Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.deReceived on Mon Aug 11 2003 - 10:32:03 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:18 UTC