Thanks for all the suggestions.
I decided in the end to just patch 'pgsql.sh' to start and stop the
slons as well. Part of the consideration is that we are are already
using the altperl wrapper, which already provides a simple syntax and
handles "watchdog" scripts as well, I believe.
Here's the patch to pgsql.sh I made. We still use "slon_start 1" and
"slon_kill" to directly affect slon, which are already simple enough
commands.
--- pgsql.sh.bak Tue Jun 12 17:46:50 2007
+++ pgsql.sh Tue Jun 12 17:48:08 2007
@@ -11,13 +11,16 @@
[ -x /usr/local/pgsql/bin/pg_ctl ] && {
su -l postgres -c \
'exec /usr/local/pgsql/bin/pg_ctl -w start
> /usr/local/pgsql/logs/errlog 2>&1'
- echo -n ' pgsql'
+ /usr/local/bin/slon_start 1
+ /usr/local/bin/slon_start 2
+ echo -n ' pgsql & 2 slons started '
}
;;
stop)
[ -x /usr/local/pgsql/bin/pg_ctl ] && {
exec su -l postgres -c 'exec /usr/local/pgsql/bin/pg_ctl -w -m
fast stop'
+ /usr/local/bin/slon_kill
}
;;
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
