> I've gone through a good bit of trial and error, but I'd like to make 
> sure I have my facts straight.

Hello Matt,

I use and prefer the 'altperl' scripts, but I do find that the
documentation is lacking. Patches welcome.

> Very simple configuration:  one cluster, two nodes (two servers), one 
> set.    db1 is the origin.  db2 is a subscriber.
> My question is very simple.  Which commands need to be run on which 
> machine?
> 
>  From the docs:
> 
> $ slonik_init_cluster  | slonik
> 
> I assume that the slonik_init_cluster command only needs to be run on 
> db1, the origin server.

Right.

Next, you are missing the step to start one 'slon' daemon for each node:

slon_start 1
slon_start 2

I made myself a simple "rc.d" style script that starts and stops the
slons I need this way.

> $ slonik_create_set 1 | slonik
> 
> I assume that the slonik_create_set command needs to be run on both db1 
> and db2, the subscriber.

You just run it once. It talks to the 'slon' daemons, and they talk to
each other, and take care of what they need to.

> $ slonik_subscribe_set  1 2 | slonik
> 
> I assume that the slonik_subscribe_set command only needs to be run on 
> db2, the subscriber.

I would run these commands on the server, where the slons are running.
The slons talks to both databases as needed. But yes, just run it once. 

I think you've got things basically right.

We've been using slony for a year (or two?) now on a business national
website and have no serious problems. The worst case scenerio is
dropping replication and rebuilding it from scratch. In our case, with
about a 1 G database, this can be done in about 10 minutes, and traffic
normally set to the slave can be set to the master for this time
(assuming the master can handle it).

    Mark


-- 
 . . . . . . . . . . . . . . . . . . . . . . . . . . . 
   Mark Stosberg            Principal Developer  
   mark at summersault.com     Summersault, LLC     
   765-939-9301 ext 202     database driven websites
 . . . . . http://www.summersault.com/ . . . . . . . .