I posted a question about PAM & Passwd on 4.2. It seems that passwd "ignores" any passwd lines in pam.conf. I tried the pam.d thing (Run Linux compatibility, copy rc.d/* from Redhat 6.1 to BSD. When you try to log in, the login terminates, and syslog shows:
/kernel: pid 22202 (login), uid 0: exited on siglan 10 (core dumped)
Rename pam.d, and all is happy (which means I'm back to pam.conf).
I have 300Mb swap (all unused) and 26Mb RAM inactive. I don't think that memory / out of swap space is the problem in this case. (I gather from what I could see on the net, that the main culprit for signal 10 seems to be swap space / memory)
Can anyone give me an example line for the passwd entry in pam.conf (seems to be happier, although it seems to ignore my changes)
I'm using the following:
passwd password required pam_xxxxxxx options_options......
I tried pam_cracklib.so with it's options, as well as pam_passwdqc and it's options. I am being ignored.
Regards.
Niekie
-----Original Message-----
From: Stijn Hoop [SMTP:[EMAIL PROTECTED]]
Sent: Monday, January 22, 2001 12:07 PM
To: Dominic Mitchell
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: PAM (was: Re: MAIL set by whom?)
On Mon, Jan 22, 2001 at 09:46:47AM +0000, Dominic Mitchell wrote:
> Would it be a good idea to start using /etc/pam.d ala RedHat, instead of
> the monolithic /etc/pam.conf?
>
> As far as I can see the support is already there, it's just not being
> used due to the presence of the /etc/pam.conf.
>
> This would make installing PAM entries far easier for the ports.
Seconded. I don't see any reason *not* to do it this way.
OTOH, ports are not supposed to install in /etc, so the best way would
be to extend pam to support /usr/local/etc/pam.d *and* /etc/pam.d
(if it doesn't already do this).
No, I'm not sending patches, sorry :)
--Stijn
--
Nostalgia ain't what it used to be.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
