Hello,

I have already raised an issue along this line. I have configured an ldap server and a client to see the server. If the ldap server is available, both the remote and local accounts login are fine. But if the ldap server is not available, even the local user account takes a very very long time (5 to 10 minutes) to login. Following are the config files on my client:

/etc/ldap.conf:
URI ldaps://ldapserver/
BASE dc=domain,dc=com
TLS_REQUEST allow

/etc/nsswitch.conf:
passwd: files ldap
shadow: files ldap
group: files ldap
(rest of the nsswitch.conf are left to default and there is no other ldap presense anywhere in the file)

/etc/pam.d/system-auth:
auth required pam_env.so
auth sufficient pam_unix.so nullok try_first_pass
auth requisite pam_succeed_if.so uid >= 500 quiet
auth sufficient pam_ldap.so use_first_pass
auth required pam_deny.so

account required pam_unix.so broken_shadow
account sufficient pam_localuser.so
account sufficient pam_succeed_if.so uid < 500 quiet
account [default=bad success=ok user_unknown=ignore] pam_ldap.so
account required pam_permit.so

password requisite pam_cracklib.so try_first_pass retry=3
password sufficient pam_unix.so md5 shadow nullok try_first_pass use_authtok
password sufficient pam_ldap.so use_authtok
password required pam_deny.so

session optional pam_keyinit.so revoke
session required pam_limits.so
session optional pam_mkhomedir.so
session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
session required pam_unix.so
session optional pam_ldap.so

Any ideas?

Thanks

You would probably just need to change the LDAP server timeout on the client-side.

See this thread:

http://www.linuxquestions.org/questi...etting-847718/

That solved the problem of the long delay. Thanks Omnicronos.

But is there a way to prevent the client to poke the ldap server even for the local user?

Thanks