Re: openpam_load_module():no pam_wheel.so found
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.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: openpam_load_module():no pam_wheel.so found
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 [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: openpam_load_module():no pam_wheel.so found
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 [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: openpam_load_module():no pam_wheel.so found
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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
openpam_load_module():no pam_wheel.so found
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. -- Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: openpam_load_module():no pam_wheel.so found
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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
