On Thu, 2007-08-09 at 13:26 -0400, Jan Wieck wrote:
> On 7/31/2007 6:54 PM, Jerry Sievers wrote:
> > 
> > Chris, this is very helpful.  Thanks!> 
> > 
> > Basically, I misunderstood the documentation and believe that what I
> > was trying was supported and straightforward to do.  You have affirmed
> > that it is not. 
> 
> What you intended to do is well supported and was so from day one. What 
> the "subscribe set" command, that is supposed to let slave2 become a 
> direct subscriber, requires is a path to the master. If that didn't 
> exist, the subscribe should have failed. So all you have to do is
> 
>      store path (master->slave2)
>      store path (slave2->master)
>      subscribe set (...)
> 
> After that subscribe set finished and slave2 is catching up again, you 
> can drop slave1 and are done.
> 
> I am not sure if 1.1.5 maintained the sl_listen table automagically. So 
> you might want to add the appropriate "store listen" commands in there 
> as well.

store listen is a no-op in 1.1.5, resubmit your store paths and it will
regenerate the correct listen entries. 
-- 
Brad Nicholson  416-673-4106
Database Administrator, Afilias Canada Corp.