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 
> #2  0x28077b83 in openpam_load_policy (policy=0xbfbff700, 
>     service=0x2807967f "other")
>     at 
> #3  0x28077c81 in openpam_configure (pamh=0x804f000, service=0x804a250 "su")
>     at 
> #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

Reply via email to