Thu Apr 30 08:24:24 PDT 2009
- Previous message: [Slony1-commit] slony1-engine RELEASE
- Next message: [Slony1-commit] slony1-engine/share slon.conf-sample
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine/share In directory main.slony.info:/tmp/cvs-serv32426 Modified Files: Tag: REL_2_0_STABLE slon.conf-sample Log Message: Per bug #91, some config parameters were not documented in the sample slon.conf file Index: slon.conf-sample =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/share/slon.conf-sample,v retrieving revision 1.7.2.1 retrieving revision 1.7.2.2 diff -C2 -d -r1.7.2.1 -r1.7.2.2 *** slon.conf-sample 5 Jan 2009 22:04:09 -0000 1.7.2.1 --- slon.conf-sample 30 Apr 2009 15:24:21 -0000 1.7.2.2 *************** *** 52,55 **** --- 52,59 ---- #sync_max_largemem=5242880 + # How long to wait (in seconds) before timeout when querying for remote events + # Range: [30,30000], default: 300 + # remote_listen_timeout=300 + # If this parameter is 1, messages go both to syslog and the standard # output. A value of 2 sends output only to syslog (some messages will *************** *** 109,111 **** # Directory in which to stow sync archive files ! # archive_dir="/tmp/somewhere" \ No newline at end of file --- 113,124 ---- # Directory in which to stow sync archive files ! # archive_dir="/tmp/somewhere" ! ! # These are used to cause a node to watch for a final SYNC, and then ! # terminate. You must supply the provider and the SYNC number ! # quit_sync_provider=1 ! # quit_sync_finalsync=21341 ! ! # Should the cleanup thread DELETE data from sl_log_1/2, or ! # should it leave the trimming to the TRUNCATE? ! # cleanup_deletelogs=false \ No newline at end of file
- Previous message: [Slony1-commit] slony1-engine RELEASE
- Next message: [Slony1-commit] slony1-engine/share slon.conf-sample
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list