Log Message:
-----------
Slony-I doesn't need to start after pgpool; they're fairly independent.

And if they were more codependent than they are now, slon processes would
probably need to start first...

Modified Files:
--------------
    slony1-engine:
        RELEASE-1.2.0 (r1.10 -> r1.11)

-------------- next part --------------
Index: RELEASE-1.2.0
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/RELEASE-1.2.0,v
retrieving revision 1.10
retrieving revision 1.11
diff -LRELEASE-1.2.0 -LRELEASE-1.2.0 -u -w -r1.10 -r1.11
--- RELEASE-1.2.0
+++ RELEASE-1.2.0
@@ -85,7 +85,8 @@
   some form of "watchdog."  The new behaviour points more towards
   "init" / "rc.d"-like handling, where, upon boot-up, one "rc.d" script
   might start up PostgreSQL, another one starts pgpool, and a third
-  (which must run third!) starts up a slon.
+  (which must be invoked after PostgreSQL is started) starts up a
+  slon.
 
 - Subscribe set aggressively locks tables on the subscriber to avoid
   failures