The script can be either run on a schedule or as a daemon with the "D" flag:
-# pgbouncer_follower.pl -f <config file> [-D]
+```bash
+$ pgbouncer_follower.pl -f <config file> [-D]
+```
+
+To run as a daemon in debian:
+
+```bash
+$ sudo cp init.debian /etc/init.d/pgbouncer_follower_rw
+$ cp pgbouncer_follower.pl /var/slony/pgbouncer_follower/pgbouncer_follower.pl
+$ cp pgbouncer_follower_rw.conf /var/slony/pgbouncer_follower/pgbouncer_follower_rw.conf
+$ sudo chmod +x /etc/init.d/pgbouncer_follower_rw
+$ sudo update-rc.d pgbouncer_follower_rw start 99 2 3 4 5 . stop 24 0 1 6
+$ sudo invoke-rc.d pgbouncer_follower_rw start
+```
##Configuration options
| pgBouncer | sets_to_follow | text | *1* | Comma separated list of sets to follow or 'all' to follow all sets
| pgBouncer | pool_mode | 'ro/rw' | *'rw'* | Select a read-only subscriber or the origin for read-write
| pgBouncer | pool_all_databases | boolean | *'false'* | If true uses wildcard for database name in pgbouncer.ini, false uses slony database
+| pgBouncer | only_follow_origins | boolean | *'false'* | If true pgbouncer will only be reconfigured and reloaded when sets move origin
| pgBouncer | status_file | text | *'/tmp/pgbouncer_follower_%mode.status'* | File used to store a hash depicting the state of the cluster
| pgBouncer | log_file | text | *'/tmp/pgbouncer_follower_%mode.log'* | Log file for the script
| pgBouncer | pid_file | text | *'/tmp/pgbouncer_follower_%mode.log'* | PID file for the script when run as a daemon