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
> -----Original Message-----
> From: email@example.com [mailto:389-users-
> firstname.lastname@example.org] On Behalf Of Vesa Alho
> Sent: 21. lokakuuta 2013 15:50
> To: email@example.com
> Subject: Re: [389-users] 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
> > 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!
> 389 users mailing list
389 users mailing list