roctaiwan nettreeinc at gmail.com
Thu Aug 6 00:10:21 PDT 2009
for me, I find the slon PID first and kill it by it's PID #. 

To find out your PID, su postgres first then type: ps -ef | grep slon

u may have 3 PID#'s but I usually choose the number shown in between. Find
the PID# then do: kill (pid#) until it got killed off.



Sweta Mulgavker wrote:
> 
> Hello ,
> 
> Can anyone tell me how to stop slony....
> 
> I tried slon_kill but it says
> 
> bash-3.2$ /usr/bin/slon_kill
> slon_kill.pl...   Killing all slon and slon_watchdog instances for the
> cluster replication
> 1.  Kill slon watchdogs
> No watchdogs found
> 
> 2. Kill slon processes
> No slon processes found
> 
> 
> i have started the replication daemons on master & slave by using
> following
> command
> 
> On master run
> /usr/local/pgsql/bin/slon $CLUSTERNAME "dbname=$MASTERDBNAME
> user=$MASTERDBA
> host=$MASTERHOST port=$MASTERPORT" > slon.log &
> 
> On slave run
> /usr/local/pgsql/bin/slon $CLUSTERNAME "dbname=$SLAVEDBNAME user=$SLAVEDBA
> host=$SLAVEHOST port=$SLAVEPORT" > slon.log &
> 
> 
> 
> 
> Now I dont know how to stop it ...
> 
> Regards ,
> Sweta.
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
> 
> 

-- 
View this message in context: http://www.nabble.com/Stop-Slon-tp24805270p24840623.html
Sent from the Slony-I -- General mailing list archive at Nabble.com.



More information about the Slony1-general mailing list