[Date Prev][Date Next]
Re: Transparent redundancy
-----BEGIN PGP SIGNED MESSAGE-----
Quanah Gibson-Mount wrote:
| --On Thursday, July 15, 2004 4:43 PM +0200 Sensei <firstname.lastname@example.org> wrote:
|> All the
|> users acquire informations (naming, home dirs...) on an openldap server.
|> Now, my question about it is: how to make it redundant?
|> We have a quite unreliable network. The server is on one floor and I'm
|> thinking about having a second server on the second floor. I need these
|> two cells to work cooperatively but ``independent'' one from each other.
|> In other words, if the link between the two servers goes down, each
|> floor keep to authenticate and work. Login can work fine, even without
|> the home directory, which can reside on the other server. How can I do
|> Do not bother about krb5 or afs. I'm dealing now with the ldap issues.
| I suggest having several ldap replicas in a load-balance pool, and point
| your systems to use the load balanced pool name.
Or, just list all the ldap server host names instead of the single host
name (if you can't do load-balancing), and all programs using libldap
will fail over to each server in the list.
For example, for nss_ldap (which would imply this is the wrong list for
this question ...) you could have this in /etc/ldap.conf:
host slave1 slave2 master
Buchan Milne Senior Support Technician
Obsidian Systems http://www.obsidian.co.za
B.Eng RHCE (803004789010797)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----