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
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
[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 Sm
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
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=0xbfbf
