The slony1 ebuild needs to support more than 1 cluster. Both the /etc/conf.d/slony1 and /etc/init.d/slony1 would likely need to be updated in some way. I'll try to come up with a soltuion as well since I need this for an enterprise deployment. I have a custom init script that I have been using on RHEL, but I'd rather improve the gentoo ebuild.
Created attachment 150179 [details]
new slony1 init.d script and conf.d example
Here is a replacement version of the slony1 init script with a conf.d example. One change is using the slon_start and slon_kill scripts that handle watchdog processes as well to keep slon running. This necessitates setting up configuration files by the admin that are used by the perl admin scripts for slony that will contain variables needed for slon_start like the cluster name, dbhost, etc. Do you think this is too big of an assumption? perhaps a useflag for this style init? Or maybe just some docs?
Created attachment 341880 [details]
Created attachment 341882 [details]
Here's my version. Based on start-stop-daemon and compatible with 2.x.x slony1.
Available at my overlay alongside with slony 2.1.3 at https://code.google.com/p/barzog-gentoo-overlay/