Provided by: bcfg2_1.2.2-1ubuntu2_all
bcfg2 - reconfigure machine based on settings in Bcfg2
bcfg2 [-d] [-v] [-p] [-c cache file] [-e] [-f config file] [-I] [-q]
[-z] [-b bundle] [-r removal mode] [--ca-cert=file] [--ssl-cns=list]
bcfg2 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 state.
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.
-I Run bcfg2 in interactive mode. The user will be prompted before
-O Omit lock check.
-P 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 network communication.
Manually specify the server location (as opposed to using the
value in bcfg2.conf).
Run bcfg2 against one or multiple bundles in the configuration.
Cache a copy of the configuration in cachefile.
Specifiy the path to the SSL CA certificate.
-d Run bcfg2 in debug mode.
-e When in verbose mode, display extra entry information (temporary
until verbosity rework).
-f <specification path>
Configure from a file rather than querying the server.
-h Print Usage information.
-k Run in bulletproof mode. This currently only affects behavior in
the debian toolset; it calls apt-get update and clean and dpkg
Run the client in the server decision list mode (unless "none"
is specified, which can be done in order to override the
decision list mode specified in bcfg2.conf). 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. (This setting will be ignored if the -f
option is also specified.)
-n 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.
-q 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.
-Q Run bcfg2 in "bundle quick" mode, where only entries in a bundle
are verified or installed. This runs much faster than -q, but
doesn't provide statistics to the server at all. In order for
this option to work, the -b option must also be provided. This
option is incompatible with -r.
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 modify services.
Specifiy the path to the SSL certificate.
List of acceptable SSL server Common Names.
Specifiy the path to the SSL key.
Attempt to authenticate as 'user'.
Use 'password' for client communication.
Set the timeout (in seconds) for client communication. Default
is 90 seconds.
-v Run bcfg2 in verbose mode.
-z Only configure independent entries, ignore bundles.