Atom Powers wrote: > > What are the other strategies for making a service highly available? We have used load sharing devices (in our case, the ones we make) to provide load sharing and high availability for LDAP. Note that this is more of a problem for Kerberos, so with AD we don't do this - but AD is already built to fail over 'gracefully'.
Another technique - client-side caching. This can alleviate the need to have instant LDAP availability for most operations except authentication (so existing tasks keep running while an occasional login may fail). This doesn't work well for large directories, but is viable for passwd/group/home directory information. Don't try it with the million-entry telephone directory! - Richard _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
