roctaiwan <nettreeinc at gmail.com> writes:
> [root at Master-DB-Slony-I ~]# ps -ef | grep slon
> postgres 19093     1  0 10:40 pts/2    00:00:00
> /opt/PostgresPlus/8.3/bin/slon.bi        n -f master.slon
> postgres 19094 19093  0 10:40 pts/2    00:00:00
> /opt/PostgresPlus/8.3/bin/slon.bi        n -f master.slon
> postgres 19138     1  0 10:41 pts/2    00:00:00
> /opt/PostgresPlus/8.3/bin/slon.bi        n -f slave.slon
> postgres 19139 19138  0 10:41 pts/2    00:00:01
> /opt/PostgresPlus/8.3/bin/slon.bi        n -f slave.slon
> root     26844 18122  0 14:00 pts/2    00:00:00 grep slon
>
>
> could someone explain above log to me. Is above saying I started total 4
> slon engine, two on master db and two on slave db? 

If this is Linux we're talking about, it is probable that this is in
fact just two processes, each with two threads.  

The slon process spawns a thread for each node with which it
communicates, and on Linux, threads are expressed as processes.

> If I would like to kill the slon using kill slon or pkill slon and needs to
> address which one to kill by including the PID. What are the PID numbers
> should I kill to close all the slon process? 19093 and 19094 for master and
> 19138 and 19139 for slave?

I suspect that processes 19094 and 19139 are "child threads"; if you
kill the parent processes, 19093 and 19138, that would also kill off
the child threads.  It is possible that killing the children would
also take out the parents; I'm not certain.
-- 
output = reverse("ofni.sailifa.ac" "@" "enworbbc")
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"