summaryrefslogtreecommitdiffstats
path: root/src
diff options
context:
space:
mode:
authorMichael Fenn <fennm@deshawresearch.com>2014-07-07 11:41:17 -0400
committerMichael Fenn <fennm@deshawresearch.com>2014-07-07 11:41:17 -0400
commit63049a81dc0f9cbfa7fe2fca6ca875f96aad359d (patch)
tree783033b712d70c821435bf1b9ddd11316960169d /src
parenta0a0a5394136d5d0c384a264244526615982fdee (diff)
downloadbcfg2-63049a81dc0f9cbfa7fe2fca6ca875f96aad359d.tar.gz
bcfg2-63049a81dc0f9cbfa7fe2fca6ca875f96aad359d.tar.bz2
bcfg2-63049a81dc0f9cbfa7fe2fca6ca875f96aad359d.zip
Change fam_blocking default to True
Based on discussion in #bcfg2, the consensus seems to be that the behavior provided by fam_blocking = True is the least surprising of the two options (i.e. the server should not process data until it is ready). 1.4 seems like a good time to make this change.
Diffstat (limited to 'src')
-rw-r--r--src/lib/Bcfg2/Server/Core.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/lib/Bcfg2/Server/Core.py b/src/lib/Bcfg2/Server/Core.py
index 544f417b4..4b2f5da0e 100644
--- a/src/lib/Bcfg2/Server/Core.py
+++ b/src/lib/Bcfg2/Server/Core.py
@@ -131,7 +131,7 @@ class Core(object):
Bcfg2.Options.Common.repository,
Bcfg2.Options.Common.filemonitor,
Bcfg2.Options.BooleanOption(
- cf=('server', 'fam_blocking'), default=False,
+ cf=('server', 'fam_blocking'), default=True,
help='FAM blocks on startup until all events are processed'),
Bcfg2.Options.BooleanOption(
cf=('logging', 'performance'), dest="perflog",