[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: replica allowing updates
- To: Jim Roberts <jroberts@realmedia.com>
- Subject: Re: replica allowing updates
- From: "Michael J. Maravillo" <mike.maravillo@ramcargroup.com>
- Date: Tue, 30 May 2000 23:50:19 +0800
- Cc: openldap-software@OpenLDAP.org
- Content-disposition: inline
- In-reply-to: <Pine.LNX.4.21.0005300903290.30343-100000@localhost.localdomain>; from jroberts@realmedia.com on Tue, May 30, 2000 at 09:07:08AM -0400
- Organization: Ramcar Food Group IT
- References: <Pine.LNX.4.21.0005300903290.30343-100000@localhost.localdomain>
- User-agent: Mutt/1.1.12i
On Tue, May 30, 2000 at 09:07:08AM -0400, Jim Roberts wrote:
>
> I have a master ldap server set up and a slave running
> as a replica. The replication works fine, but if I
> try updating the slave (as rootdn), it accepts the
> update.
I've seen this happen. You might have set the slave to have the
same rootdn and updatedn. I'm not sure though if this is the
right behaviour for updates on this situation.
However, using an entry in the directory as dn for updatedn
returns a referral to the master for updates.
> I thought I saw the referral rule to prevent this
> somewhere in the docs, but cannot find it now. Can
> someone point me in the right direction? It's just a
> matter of referring updates to the master, right?
Cheers,
Mike