blob: 7f6e6b6675d7f0064bbdffa2c94c0a5fd7e6f12e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
.. -*- mode: rst -*-
.. _client-tools-index:
Available client tools
======================
Client tool drivers allow Bcfg2 to execute configuration operations
by interfacing with platform and distribution specific tools.
Tool drivers handle any reconfiguration or verification operation.
So far we have tools that primarily deal with packaging systems
and service management. The POSIX tool also handles file system
and permissions/groups operations. To write your own tool driver,
to handle a new packaging format, or new service architecture see
:ref:`development-client-driver`.
When the Bcfg2 client is run, it attempts to instantiate each of
these drivers. The succeeding list of drivers are printed as a
debug message after this process has completed. Drivers can
supercede one another, for example, the Yum driver conflicts (and
unloads) the RPM driver. This behavior can be overridden by running
the Bcfg2 client with the ``-D`` flag. This flag takes a colon
delimited list of drivers to use on the system.
Currently these are the tool drivers that are distributed with Bcfg2:
.. toctree::
:maxdepth: 1
:glob:
*
|
