PLEX86  x86- Virtual Machine (VM) Program
 Plex86  |  CVS  |  Mailing List  |  Download  |  Linux  |  Newsgroups

MultiMaster Replication in OpenLDAP 2.2.x


Your Ad Here

Your Ad Here

export DISPLAY from LnxBox1 to LnxBox2 not working
On 1 Feb 2006 07:43:48 -0800, Joseph staggered into the Black Sun and said: O RLY? YA RLY. NO WAI!!1! As of about 2 years ago...

Any reason you can't upgrade to Suse10.x and OpenLDAP 2.3.x ?

Multimaster has never been "supported" officially though you could get it to work, IIRC, in some (older?) versions. It does not conform to the standard, though commercial servers often support it as a "feature creature".

Look here for some recent comments which seem to be in synch with what I recall from past discussions:

The list thread is pretty recent (11-05) and touches on the problems of multimaster replication. A good review.

Remember, LDAP is optimized for fast reads but writes (of any kind) are slowwwwww! Novell has the "best" directory server (in many respects) and even they do not recommend multimaster replication. They use parbreastioning and distributed uptream-downstream update referrals in a manner broadly similar to OpenLDAP's syncrepl in 2.3.x.

These same problems occur with rdbms systems as well and there is no system yet that I'm convinced can't be "broken" by miconfiguration or misbehaving apps. Wholesale db write locks are the "safe" way to go, but you can imagine how popular that is.

Redhat has recently released the code for their Netscape-AOL directory server but I've not had a chance to look it over. Pretty sure it offers multimaster replication.

Yep, it does, in its own way:-)

If you need to run Suse, I would check out what Novell is doing to re: eDirectory and Linux, though I don't recall any suggestion that they will open any of the code. Still makes too much $ for them. The future?

good luck, prg



Your Ad Here

List | Previous | Next

export DISPLAY from LnxBox1 to LnxBox2 not working

Linux groups from Newsgroups

The #1 Usenet Provider on the Internet

a problem with nat table setting