When you use slonik scripts to create your replicated tables, you can 
run them through slonik on any machine that can login as the slony users 
to all of the database servers. Here's a breakdown of how I usually do it:


Setup your slony users on each database server.

Setup your slon-dbname.conf on each database server.

If your slonik scripts don't, create the matching schema for your 
replicated tables on each database.

Run your slonik scripts to initialize the slony installation for the 
databases on the master. When you do this, slonik will connect to the 
replicas as necessary to create the slony schema in those databases.

With the slony schema installed, then you can start the slon process for 
each database, on each machine. If you use SYNC( ID = source); and then 
a WAIT FOR EVENT to confirm in your slonik to confirm config and 
replication, you will need to start the slon on each machine before your 
script will exit cleanly.


If you watch the logs, you'll see a bunch of activity until all the 
replicas are up to date.



Alex Haugg wrote:
> hi, i have a question:
>
> in every examples you have the master and the slave on the same host
> (local host). 
> but i would like to know the configuration from slony master and slony
> slave on two several hosts.
>
> were will defined the cluster and the tables( i think on the master )?
>
> were will initialized the connection of slony master and the slony
> slave?
>
> were will started the slon process ( i think on the master for the
> master and on the slave for the slave )?
>
> please help me.
>
> Thank you very much indeed.
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>   

-- 



Nicholas J. Kiraly
Collaborative Fusion, Inc.
nkiraly at collaborativefusion.com
412-422-3463 x4024
5849 Forbes Avenue
Pittsburgh, PA 15217 

****************************************************************
IMPORTANT: This message contains confidential information
and is intended only for the individual named. If the reader of
this message is not an intended recipient (or the individual
responsible for the delivery of this message to an intended
recipient), please be advised that any re-use, dissemination,
distribution or copying of this message is prohibited. Please
notify the sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The
sender therefore does not accept liability for any errors or
omissions in the contents of this message, which arise as a
result of e-mail transmission.
****************************************************************