Re: [pamldap] RE: [nssldap] pam_ldap and nss_ldap can't connect to LDAP server(s)
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
Re: [pamldap] RE: [nssldap] pam_ldap and nss_ldap can't connect to LDAP server(s)
- From: Guillaume Rousse <Guillaume.Rousse [at] inria.fr>
- To: nssldap [at] padl.com
- Subject: Re: [pamldap] RE: [nssldap] pam_ldap and nss_ldap can't connect to LDAP server(s)
- Date: Fri, 26 Jun 2009 10:01:33 +0200
Aaron Hicks a écrit :
>It's also clear that it's asking for attributes that aren't stored in
> the AD, some I don't want to set (e.g. home directory, we have some
>servers where it should be /home/user and others where it should be
>/export/home/user) so I hope if nss is unable to set them, then the
>system defaults are used.
Unfortunatly for you, I don't think there is anything as 'system
default' for nss values. In a mixed environment, user account
information is perceived exactly the same on every system, which cause
heavy troubles when login shell is different from '/bin/sh', for
instance (BSD systems don't have /bin/bash, usually).
Either you ensure an constant home directory is usable everywhere, by
customising your filesystem setup (a local nfs mount is supposed to have
a very restricted I/O perf impact), either you override your user
account locally when needed (but you can't override just one attribute,
you have to override the whole account).
--
BOFH excuse #323:
Your processor has processed too many instructions. Turn it off
immediately, do not type any commands!!
RE: [nssldap] pam_ldap and nss_ldap can't connect to LDAP server(s),
Aaron Hicks
Re: [nssldap] pam_ldap and nss_ldap can't connect to LDAP server(s),
Thomas Koeller
Message not available