On Thu, 2006-02-23 at 22:53 -0600, Barry Brimer wrote:

On Fri, 24 Feb 2006, Oliver Schulze L. wrote:

...

Hi, I have a problem that when my slapd fails to start, I can no longer login via ssh as a user that is in /etc/passwd

How can I solve this? Editing /etc/nsswitch.conf o pam.d/ ?

The easiest thing to do is to use authconfig to change your authentication parameters. PAM and nsswitch will be updated accordingly.

---- not if you can't login...

what does 'grep passwd /etc/nsswitch.conf' look like?

Craig

Hi Josh and Barry, running system-config-authentication solved the problem.

The lines in system-auth looks like this: account required /lib/security/$ISA/pam_unix.so broken_shadow account sufficient /lib/security/$ISA/pam_succeed_if.so uid < 100 quiet account [default=bad success=ok user_unknown=ignore] /lib/security/$ISA/pam_ldap.so account required /lib/security/$ISA/pam_permit.so

I have CentOS 4.2 and is working now as expected

Many thanks Oliver

Josh Kelley wrote:

On 2/23/06, Oliver Schulze L. oliver@samera.com.py wrote:

...

I have a problem that when my slapd fails to start, I can no longer login via ssh as a user that is in /etc/passwd

How can I solve this? Editing /etc/nsswitch.conf o pam.d/ ?

Which version of CentOS? CentOS 4 adds "pam_succeed_if.so uid < 100 quiet" in /etc/pam.d/system-auth to hopefully fix this kind of problem, but CentOS 3 doesn't have anything like that.

Josh Kelley _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos