bcfg2 - reconfigure machine based on settings in BCFG2
bcfg2 [-d] [-v] [-p] [-c cache file] [-e] [-f config file] [-I] [-q]
[-b bundle] [-r removal mode]
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.
-A Run in agent (continuous) mode, wait for reconfigure command
-B Run bcfg2 in build mode. Services aren’t started, as the system
may still be in miniroot.
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.
Specify the server fingerprint.
-I Run bcfg2 in interactive mode. The user will be prompted before
-K <SSL key file>
Specify the path to the SSL key.
-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 only one bundle in the configuration.
Cache a copy of the configuration in cachefile
-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.
-g <agent port>
Allows you to specify which port to bind.
-h Print Usage information.
-i Daemonize the agent.
-k Run in bulletproof mode. This currently only effect behavior in
the debian toolset; it calls apt-get update and clean and dpkg
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.
-n Run bcfg2 in dry-run mode. No changes will be made to the
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.
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.
Attempt to authenticate as ’user’.
Use ’password’ for client communication.
-v Run bcfg2 in verbose mode.