Slony is brilliant!! Quite simple to setup and it works flawlessl (so 
far). Thanks guys!

We now have a website using two databases which allows us to spread the 
server load. Some non critical (readonly) content is coming from our 
replicated slave while the rest of the site accesses the main/master 
database. Since we don't have a huge volume of inserts or updates, the 
slave seeme to keep up really well.

Question: We have sys v init scripts to start and stop postgres 
automatically on server reboots and stop/starts.

What is the perceived wisdom for starting and stopping slon - can we use 
similar scripts to do this, and is there an order in which the services 
must be started?

Can slon be started as root? Or should it only be started under the 
postgres/slon user account?

What about logging output from slon - we see very few messages, but it 
would be reassuring to have them captured.

If a sys v init script is OK, can anyone provide an example?

Thanks

John Sidney-Woollett