1bcfg2(1) General Commands Manual bcfg2(1)
2
6 bcfg2 - reconfigure machine based on settings in Bcfg2
7
9 bcfg2 [-d] [-v] [-p] [-c cache file] [-e] [-f config file] [-I] [-q]
10 [-b bundle] [-r removal mode]
11
13 bcfg2 Runs the Bcfg2 configuration process on the current host. This
14 process consists of first fetching and executing probes, upload‐
15 ing probe results, fetching the client configuration, checking
16 the current client state, attempting to install the desired con‐
17 figuration, and finally uploading statistics about the Bcfg2
18 execution and client state.
19
22 -C <configfile>
23 Specify alternate bcfg2.conf location.
24 -D <driver1>,<driver2>
27 Specify a set of Bcfg2 tool drivers. NOTE: only drivers listed
28 will be loaded. (IE, if you don't include POSIX, you will be
29 unable to verify/install ConfigFiles, etc).
30 -E <encoding>
33 Specify the encoding of Cfg files.
34 -I Run bcfg2 in interactive mode. The user will be prompted before
37 each change.
38 -O Omit lock check.
41 -P Run bcfg2 in paranoid mode. Diffs will be logged for configura‐
44 tion files marked as paranoid by the Bcfg2 server.
45 -R <retry count>
48 Specify the number of times that the client will attempt to
49 retry network communication.
50 -S https://server:port
53 Manually specify the server location (as opposed to using the
54 value in bcfg2.conf).
55 -b <bundle1>:<bundle2>
58 Run bcfg2 against one or multiple bundles in the configuration.
59 -c <cachefile>
62 Cache a copy of the configuration in cachefile.
63 -d Run bcfg2 in debug mode.
66 -e When in verbose mode, display extra entry information (temporary
69 until verbosity rework).
70 -f <specification path>
73 Configure from a file rather than querying the server.
74 -h Print Usage information.
77 -k Run in bulletproof mode. This currently only affects behavior in
80 the debian toolset; it calls apt-get update and clean and dpkg
81 --configure --pending.
82 -l <whitelist|blacklist>
85 Run the client in the server decision list mode. This approach
86 is needed when particular changes are deemed "high risk". It
87 gives the ability to centrally specify these changes, but only
88 install them on clients when administrator supervision is avail‐
89 able. Because collaborative configuration is one of the remain‐
90 ing hard issues in configuration management, these issues typi‐
91 cally crop up in environments with several administrators and
92 much configuration variety.
93 -n Run bcfg2 in dry-run mode. No changes will be made to the sys‐
96 tem.
97 -o <LogFile Path>
100 Writes a log to the specified path.
101 -p <profile>
104 Assert a profile for the current client.
105 -q Run bcfg2 in quick mode. Package checksum verification won't be
108 performed. This mode relaxes the constraints of correctness, and
109 thus should only be used in safe conditions.
110 -r <mode>
113 Cause bcfg2 to remove extra configuration elements it detects.
114 Mode is one of all, Services, or Packages. All removes all
115 entries. Likewise, Services and Packages remove only the extra
116 configuration elements of the respective type.
117 -s <service mode>
120 Set bcfg2 interaction level for services. Default behavior is to
121 modify all services affected by reconfiguration. build mode
122 attempts to stop all services started. disabled suppresses all
123 attempts to modify services.
124 --ssl-key=<ssl key>
127 Specifiy the path to the SSL key.
128 -u <user>
131 Attempt to authenticate as 'user'.
132 -x <password>
135 Use 'password' for client communication.
136 -v Run bcfg2 in verbose mode.
139
141 bcfg2-server(8), bcfg2-info(8)
142
144 bcfg2(1)