Re: [Fedora-directory-users] Chain on Update Problem

2006-09-05 Thread James B Newby
=hg,dc=com nsUniqueID: fd033081-1dd111b2-80cef01a-e856 [EMAIL PROTECTED] bin]# Richard Megginson wrote: James B Newby wrote: Yes, it is a read-only consumer, set up as per instructions in the administration guide. My multi-master replication scheme works fine. When chaining is not set up

Re: [Fedora-directory-users] Chain on Update Problem

2006-09-05 Thread James B Newby
they do not propagate to the master. Are there any other queries I should make to the server in order to give you more information? Richard Megginson wrote: James B Newby wrote: Yes. I can add or modify entries on the consumer with update chaining set up, but those changes do not propagate to

Re: [Fedora-directory-users] Chain on Update Problem

2006-09-03 Thread James B Newby
n answer but no luck. Richard Megginson wrote: James B Newby wrote: Well actually the entry was already there; I just made a small change to one of the attributes on the consumer through the directory console. I added a new entry on the consumer from the command line: [EMAIL PROTECTED] bin]# .

Re: [Fedora-directory-users] Chain on Update Problem

2006-09-01 Thread James B Newby
; scope=0 filter="(objectClass=*)" attrs="*" [01/Sep/2006:18:20:05 -0500] conn=1 op=27 RESULT err=0 tag=101 nentries=1 etime=0 [01/Sep/2006:18:20:05 -0500] conn=1 op=28 SRCH base="uid=nbody,ou=people,o=thgg,dc=hg,dc=com" scope=0 filter="(|(objectClass=*)(objectClass=

Re: [Fedora-directory-users] Chain on Update Problem

2006-09-01 Thread James B Newby
g,dc=com" scope=0 filter="(|(objectClass=*)(objectClass=ldapsubentry))" attrs="objectClass numSubordinates ref aci" [01/Sep/2006:17:41:41 -0500] conn=0 op=18 SORT cn givenName o ou sn (1) [01/Sep/2006:17:41:41 -0500] conn=0 op=18 RESULT err=0 tag=101 nentries=1 etime=0

[Fedora-directory-users] Chain on Update Problem

2006-09-01 Thread James B Newby
Hello all, I'm having a problem with my consumer's chain on update. I have a setup with two masters and one consumer. Multi-master replication is working properly. Changes made on either master propagate to the other master and to the consumer. Before setting up chaining, changes made on