Can't su
Current -CURRENT won't let me run su; it dies with SIGSEGV. The backtrace says: #0 0x28078c57 in openpam_add_module (policy=0xbfbff700, chain=0, flag=1, modpath=0xbfbff28f pam_nologin.so, optc=-1, optv=0xbfbfee78) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/openpam_load.c:182 #1 0x2807796d in openpam_read_policy_file (policy=0xbfbff700, service=0x2807967f other, filename=0x804c1e0 /etc/pam.d/other, style=1) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/openpam_configure.c:189 #2 0x28077b83 in openpam_load_policy (policy=0xbfbff700, service=0x2807967f other) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/openpam_configure.c:236 #3 0x28077c81 in openpam_configure (pamh=0x804f000, service=0x804a250 su) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/openpam_configure.c:275 #4 0x280751b8 in pam_start (service=0x804a250 su, user=0x804a223 root, pam_conv=0xbfbffbd4, pamh=0x804b4ac) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/pam_start.c:68 #5 0x804948f in main (argc=1, argv=0xbfbffc38) at /usr/src/usr.bin/su/su.c:211 #6 0x8049061 in _start () Everything in /etc/pam.d is up to date. I can't run xdm either, (the X server starts, it sits for awhile without a greeter, the server exits and everything starts over) but I don't know if that's related or not. -Peter- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't su
On Fri, May 03, 2002 at 12:30:15AM -0700, Peter S. Housel wrote: Current -CURRENT won't let me run su; it dies with SIGSEGV. The backtrace says: #0 0x28078c57 in openpam_add_module (policy=0xbfbff700, chain=0, flag=1, modpath=0xbfbff28f pam_nologin.so, optc=-1, optv=0xbfbfee78) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/openpam_load.c:182 #1 0x2807796d in openpam_read_policy_file (policy=0xbfbff700, service=0x2807967f other, filename=0x804c1e0 /etc/pam.d/other, style=1) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/openpam_configure.c:189 #2 0x28077b83 in openpam_load_policy (policy=0xbfbff700, service=0x2807967f other) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/openpam_configure.c:236 #3 0x28077c81 in openpam_configure (pamh=0x804f000, service=0x804a250 su) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/openpam_configure.c:275 #4 0x280751b8 in pam_start (service=0x804a250 su, user=0x804a223 root, pam_conv=0xbfbffbd4, pamh=0x804b4ac) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/pam_start.c:68 #5 0x804948f in main (argc=1, argv=0xbfbffc38) at /usr/src/usr.bin/su/su.c:211 #6 0x8049061 in _start () Everything in /etc/pam.d is up to date. I can't run xdm either, (the X server starts, it sits for awhile without a greeter, the server exits and everything starts over) but I don't know if that's related or not. You're not the only one, I noticed it because I have dnetc run in the background on startup by use of su and I suddenly say su dying. (Not used xdm so no idea about that one) -- Simon Dick [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't su
Also have the same problem with su on -CURRENT from yesterday. Yuri On Fri, 3 May 2002, Peter S. Housel wrote: Current -CURRENT won't let me run su; it dies with SIGSEGV. The backtrace says: #0 0x28078c57 in openpam_add_module (policy=0xbfbff700, chain=0, flag=1, modpath=0xbfbff28f pam_nologin.so, optc=-1, optv=0xbfbfee78) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/openpam_load.c:182 #1 0x2807796d in openpam_read_policy_file (policy=0xbfbff700, service=0x2807967f other, filename=0x804c1e0 /etc/pam.d/other, style=1) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/openpam_configure.c:189 #2 0x28077b83 in openpam_load_policy (policy=0xbfbff700, service=0x2807967f other) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/openpam_configure.c:236 #3 0x28077c81 in openpam_configure (pamh=0x804f000, service=0x804a250 su) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/openpam_configure.c:275 #4 0x280751b8 in pam_start (service=0x804a250 su, user=0x804a223 root, pam_conv=0xbfbffbd4, pamh=0x804b4ac) at /usr/src/lib/libpam/libpam/../../../contrib/openpam/lib/pam_start.c:68 #5 0x804948f in main (argc=1, argv=0xbfbffc38) at /usr/src/usr.bin/su/su.c:211 #6 0x8049061 in _start () Everything in /etc/pam.d is up to date. I can't run xdm either, (the X server starts, it sits for awhile without a greeter, the server exits and everything starts over) but I don't know if that's related or not. -Peter- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't su
[EMAIL PROTECTED] (Peter S. Housel) writes: Current -CURRENT won't let me run su; it dies with SIGSEGV. The backtrace says: Yep, I see what the error is. All I can say is arrrgh! since I've been running this code for a while now and it never segfaults on my box :( DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't su
On 3 May 2002, Dag-Erling Smorgrav wrote: [EMAIL PROTECTED] (Peter S. Housel) writes: Current -CURRENT won't let me run su; it dies with SIGSEGV. The backtrace says: Yep, I see what the error is. All I can say is arrrgh! since I've been running this code for a while now and it never segfaults on my box :( DES DES: also seeing problems with ftpd: it dumps core on signal 10 a gdb/backtrace of it: #0 0x280cd9c7 in openpam_add_module () from /usr/lib/libpam.so.2 (gdb) bt #0 0x280cd9c7 in openpam_add_module () from /usr/lib/libpam.so.2 #1 0x280ccc58 in openpam_dispatch () from /usr/lib/libpam.so.2 #2 0x280cce1a in openpam_dispatch () from /usr/lib/libpam.so.2 #3 0x280ccedf in openpam_configure () from /usr/lib/libpam.so.2 #4 0x280caf13 in pam_start () from /usr/lib/libpam.so.2 #5 0x804c50a in getsockname () #6 0x804c749 in getsockname () #7 0x8050c98 in getsockname () #8 0x804b71d in getsockname () #9 0x804ac05 in getsockname () ouch. -Trish -- Trish Lynch [EMAIL PROTECTED] FreeBSD The Power to Serve Ecartis Core Team [EMAIL PROTECTED] http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't su
Trish Lynch [EMAIL PROTECTED] writes: DES: also seeing problems with ftpd: Same bug, same fix. Cvsup and rebuild libpam. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
