Runs the Bcfg2 configuration process on the current host. This process
consists of first fetching and executing probes, uploading probe
results, fetching the client configuration, checking the current
client state, attempting to install the desired configuration, and
finally uploading statistics about the Bcfg2 execution and client
Specify alternate bcfg2.conf location.
Specify a set of Bcfg2 tool drivers. NOTE: only drivers listed will be
loaded. (IE, if you don't include POSIX, you will be unable to
verify/install ConfigFiles, etc).
Specify the encoding of Cfg files.
Run bcfg2 in interactive mode. The user will be prompted before each
Omit lock check.
Run bcfg2 in paranoid mode. Diffs will be logged for
configuration files marked as paranoid by the Bcfg2 server.
-R <retry count>
Specify the number of times that the client will attempt to retry
Manually specify the server location (as opposed to using the value in
Run bcfg2 against one or multiple bundles in the configuration.
Cache a copy of the configuration in cachefile.
Run bcfg2 in debug mode.
When in verbose mode, display extra entry information (temporary until
-f <specification path>
Configure from a file rather than querying the server.
Print Usage information.
Run in bulletproof mode. This currently only affects behavior in the
debian toolset; it calls apt-get update and clean and
dpkg --configure --pending.
Run the client in the server decision list mode. This approach is needed
when particular changes are deemed "high risk". It gives the ability to
centrally specify these changes, but only install them on clients when
administrator supervision is available. Because collaborative
configuration is one of the remaining hard issues in configuration
management, these issues typically crop up in environments with several
administrators and much configuration variety.
Run bcfg2 in dry-run mode. No changes will be made to the
-o <LogFile Path>
Writes a log to the specified path.
Assert a profile for the current client.
Run bcfg2 in quick mode. Package checksum verification won't be
performed. This mode relaxes the constraints of correctness, and thus
should only be used in safe conditions.
Cause bcfg2 to remove extra configuration elements it detects. Mode is
one of all, Services, or Packages. All removes all entries. Likewise,
Services and Packages remove only the extra configuration elements of
the respective type.
-s <service mode>
Set bcfg2 interaction level for services. Default behavior is to
modify all services affected by reconfiguration. build mode attempts
to stop all services started. disabled suppresses all attempts to