From 575ad2c4b3da92f38eb710aa79dd07fb37b9d1a1 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sun, 12 Dec 2010 23:34:09 +0100 Subject: doc: Small changes --- doc/client/tools.txt | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 doc/client/tools.txt (limited to 'doc/client/tools.txt') diff --git a/doc/client/tools.txt b/doc/client/tools.txt new file mode 100644 index 000000000..7f6e6b667 --- /dev/null +++ b/doc/client/tools.txt @@ -0,0 +1,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: + + * -- cgit v1.2.3-1-g7c22