I'm not sure if existing entries are added automatically when you enable the plugin. I would assume so, but in any case at any time you can run the fix-up task that will sync the attributes. You can define the scope for the task using a filter, for example, fix only ou=orgunit,ou=People,... branch of the DIT. -- Lars Remes / Service Quality lars.remes@xxxxxxxxxx www.symbio.com > -----Original Message----- > From: 389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx [mailto:389-users- > bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Vesa Alho > Sent: 21. lokakuuta 2013 15:50 > To: 389-users@xxxxxxxxxxxxxxxxxxxxxxx > Subject: Re: MemberOf Plugin - experiences? > > On 10/21/2013 01:37 PM, Lars Remes wrote: > > We are using the memberOf plugin in a global, multi-master-multi-slave > setup, and so far we have not encountered any major issues. > > > > You can easily change the membership attribute, for example, to > memberUid. > > MMR is handled by not replicating the memberOf attribute between > masters, but the attribute IS copied to slaves. Each master runs own instance > of the plugin. > > > > Sometimes you may need to manual launch the fix-up task, but that has > been quite rare. > > If necessary, you can schedule it to run periodically. > > How does it work for already existing entries if I enable the plugin? Do > I need add them "manually" or does the plugin add them automatically? > > Naturally I will test this well before changing production, but just > interested what it takes to start using it. > > Thanks for replying! > > -Vesa > > -- > 389 users mailing list > 389-users@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
