Am Tue, 25 Feb 2014 18:24:14 -0300
schrieb Italo Valcy italova...@gmail.com:
Hello Dieter,
On Tue, Feb 25, 2014 at 5:05 PM, Dieter Klünter die...@dkluenter.de
wrote:
No, syncrepl (consumer) does not reqire operational attributs. Only
if the ldap backend is also defined as syncprov
Hi Italo
On Tue, Feb 25, 2014 at 2:08 AM, Italo Valcy italova...@gmail.com wrote:
Dear all,
I`m trying to setup replication from OpenLDAP to Fedora 389 DS.
Honestly I don't know the actual state of this implementation, but I
suggest you have a look at:
- the changelog of 389DS 1.3.2.2 [1
Hello guys,
Thanks for the replies! I'll take a look at each suggestion and give you a
reply soon.
Regards, Italo.
--
Saudações,
Italo Valcy :: http://wiki.dcc.ufba.br/Main/ItaloValcy
Hi Clément,
On Tue, Feb 25, 2014 at 5:06 AM, Clément OUDOT clem.ou...@gmail.com wrote:
you should give a try to LSC : http://lsc-project.org/wiki/
This engine allows you to define which attributes to sync, and can use
syncrepl to get all modifications done on OpenLDAP on the fly.
Thanks
Am Tue, 25 Feb 2014 08:37:41 -0300
schrieb Italo Valcy italova...@gmail.com:
Hi Dieter,
Thanks for the tip!
Actually the problem here is not which attributes are get by ryncrepl
from the provider. The problem is that the backend seems to insert the
attributes again and then send to the
Hello Dieter,
On Tue, Feb 25, 2014 at 5:05 PM, Dieter Klünter die...@dkluenter.de wrote:
No, syncrepl (consumer) does not reqire operational attributs. Only if
the ldap backend is also defined as syncprov (provider), than some
operational attributes are required in order to provide valid
Italo Valcy wrote:
Hi Dieter,
Thanks for the tip!
Actually the problem here is not which attributes are get by ryncrepl from the
provider. The problem is that the backend seems to insert the attributes again
and then send to the consumer (lastmod on, which is mandatory to syncrepl), do
you
