Table of Contents
It is recommended to run cdist with public key authentication. +
Table of Contents
It is recommended to run cdist with public key authentication. This requires a private/public key pair and the entry "PermitRootLogin without-password" in the sshd server. See sshd_config(5) and ssh-keygen(1).
When connecting to a new host, the initial delay with ssh connections diff --git a/software/cdist/man/cdist-cache.html b/software/cdist/man/cdist-cache.html new file mode 100644 index 00000000..b9a2733a --- /dev/null +++ b/software/cdist/man/cdist-cache.html @@ -0,0 +1,6 @@ + + +
Table of Contents
cdist-cache moves away the objects created during last run so the +next run can use the previous information and compare them with +the current status.
Table of Contents
Table of Contents
Table of Contents
cdist-code-run executes generated code from a given OBJECT. +
Table of Contents
cdist-code-run executes generated code from a given OBJECT. The OBJECT must be located below OBJECT_DIR. TYPE must be either local or remote and determines which code part is to be executed.
Table of Contents
Cdist-config is sourced by cdist programs and provides hints on where to find +
Table of Contents
Cdist-config is sourced by cdist programs and provides hints on where to find types, manifests, etc. Generally speaking, it’s just usable from within the core and is only of interest for cdist-developers.
Table of Contents
Deploy configurations to the specified host, as configured in the initial +
Table of Contents
Deploy configurations to the specified host, as configured in the initial manifest. This script triggers the execution of several other scripts, in so called stages. It is intented to run either from the command line or from cron.
If the environment variable cdist_conf_dir is not set, the
configuration is read from /etc/cdist. The local output directory can
diff --git a/software/cdist/man/cdist-dir.html b/software/cdist/man/cdist-dir.html
index f7e7a2c5..fcf4ba21 100644
--- a/software/cdist/man/cdist-dir.html
+++ b/software/cdist/man/cdist-dir.html
@@ -1,6 +1,6 @@
- Table of Contents cdist-dir either pushes a local directory to the target host
+ Table of Contents cdist-dir either pushes a local directory to the target host
or pulls a remote directory from a target host to the local host. In the push case SRC_DIR is local, in the pull case remote.
In the push case DST_DIR is remote, in the pull case local. cdist-dir does not cleanup DST_DIR and thus it may contain old
stuff if used multiple times. cdist-dir does not rely on rsync or other high level tools, because
diff --git a/software/cdist/man/cdist-env.html b/software/cdist/man/cdist-env.html
index 003c9095..d72425dc 100644
--- a/software/cdist/man/cdist-env.html
+++ b/software/cdist/man/cdist-env.html
@@ -1,6 +1,6 @@
- Table of Contents cdist-env outputs two strings suitable for usage in your current shell,
+ Table of Contents cdist-env outputs two strings suitable for usage in your current shell,
so you can use cdist from the checkout. cdist-env essentially helps you
to easily setup PATH and MANPATH. If you’ve multiple checkouts of cdist and run cdist-env from the various
checkouts, a new run will prepend the last directory, thus ensures you
diff --git a/software/cdist/man/cdist-explorer-run-global.html b/software/cdist/man/cdist-explorer-run-global.html
index 84184002..cc9735f2 100644
--- a/software/cdist/man/cdist-explorer-run-global.html
+++ b/software/cdist/man/cdist-explorer-run-global.html
@@ -1,6 +1,6 @@
- Table of Contents Transfer the global explorers to HOSTNAME, execute them and transfer
+ Table of Contents Transfer the global explorers to HOSTNAME, execute them and transfer
back the results. Table of Contents Explorer are small shell scripts, which will be executed on the target
+ Table of Contents Explorer are small shell scripts, which will be executed on the target
host. The aim of the explorer is to give hints to types on how to act on the
target system. An explorer outputs the result to stdout, which is usually
a one liner, but may be empty or multi line especially in the case of
diff --git a/software/cdist/man/cdist-hacker.html b/software/cdist/man/cdist-hacker.html
index 57dda706..b340b2a7 100644
--- a/software/cdist/man/cdist-hacker.html
+++ b/software/cdist/man/cdist-hacker.html
@@ -1,6 +1,6 @@
- Table of Contents Welcome dear hacker! I invite you to a tour of pointers to
+ Table of Contents Welcome dear hacker! I invite you to a tour of pointers to
get into the usable configuration mangament system, cdist. The first thing to know is probably that cdist is brought to
you by people who care about how code looks like and who think
twice before merging or implementing a feature: Less features
diff --git a/software/cdist/man/cdist-manifest-run-all.html b/software/cdist/man/cdist-manifest-run-all.html
index 52e66da9..9b1604cd 100644
--- a/software/cdist/man/cdist-manifest-run-all.html
+++ b/software/cdist/man/cdist-manifest-run-all.html
@@ -1,6 +1,6 @@
- Table of Contents cdist-manifest-run-all iterates over every existing object and
+ Table of Contents cdist-manifest-run-all iterates over every existing object and
executes the manifest of its type. Table of Contents cdist-manifest-run-init executes the initial manifest, which creates
+ Table of Contents cdist-manifest-run-init executes the initial manifest, which creates
the first objects. Table of Contents cdist-manifest-run executes the given MANIFEST and saves the output into
+ Table of Contents Table of Contents Manifests exist to define which configurations should be applied to a specific
+ Table of Contents Manifests exist to define which configurations should be applied to a specific
host as well as to define which configurations should be applied within a
type. Manifests are executed locally and the resulting objects are stored in
an internal database. The same object can be redefined in multiple different manifests as long as
diff --git a/software/cdist/man/cdist-object-explorer-all.html b/software/cdist/man/cdist-object-explorer-all.html
index e5d3b89a..2909c8cd 100644
--- a/software/cdist/man/cdist-object-explorer-all.html
+++ b/software/cdist/man/cdist-object-explorer-all.html
@@ -1,6 +1,6 @@
- Table of Contents For every object, it checks whether the type has one or more explorers.
+ Table of Contents For every object, it checks whether the type has one or more explorers.
If so, the explorers of the type are copied to the target and executed
once per object. Table of Contents Table of Contents Table of Contents For the given object, run the gencode executable. The output of this
+ Table of Contents For the given object, run the gencode executable. The output of this
executable on stdout will be used by cdist-object-gencode-all(1). Table of Contents cdist-quickstart is an interactive guide to cdist. It should be one
+ Table of Contents cdist-quickstart is an interactive guide to cdist. It should be one
of the first tools you use when you begin with cdist. To use cdist-quickstart, add the bin directory to your PATH, execute
cdist-quickstart and enjoy cdist: Various scripts which are not in the core need information on how
+ Various scripts which are not in the core need information on how
to find information. This manpage summarises the available environment
variables, types and paths and clearifies with part may access which variables. If not specified otherwise, all paths are relative to the checkout directory. Table of Contents cdist-remote-explorer-run is executed on the target.
+ Table of Contents cdist-remote-explorer-run is executed on the target.
It sets up the variable VARIABLE_NAME to point to the given
EXPLORER_DIR and runs all explorer found in EXPLORER_DIR.
The output of every run explorer is saved into OUT_DIR. Table of Contents cdist-run-remote runs the given executable on the remote host.
+ Table of Contents cdist-run-remote runs the given executable on the remote host.
It ensures PATH is setup correctly on the target side. Table of Contents Starting the execution of deployment with cdist-deploy-to(1), cdist passes
+ Table of Contents Starting the execution of deployment with cdist-deploy-to(1), cdist passes
through different stages, each can be triggered and debugged on its own.
Reading the source of the cdist-deploy-to executable shous the scripts
responsible for each stage. Before running the user facing stages, cdist prepares the target host
diff --git a/software/cdist/man/cdist-type-build-emulation.html b/software/cdist/man/cdist-type-build-emulation.html
index 6bf5eafe..e9f9b525 100644
--- a/software/cdist/man/cdist-type-build-emulation.html
+++ b/software/cdist/man/cdist-type-build-emulation.html
@@ -1,6 +1,6 @@
- Table of Contents cdist-type-build-emulation creates a link to cdist-type-emulator
+ Table of Contents cdist-type-build-emulation creates a link to cdist-type-emulator
for every TYPE. These links are placed in a OUT_DIR, which
is prepended into $PATH. This way the user can use TYPE in the
manifests like any other executable. Table of Contents cdist-type-emulator is normally called through a link to it of the
+ Table of Contents cdist-type-emulator is normally called through a link to it of the
name of a specifc type. It saves the given parameters into
a parameters directory and the requirements into a require file. It checks whether the parameters are valid: Table of Contents cdist-type-template creates a new type and adds the usual files to it.
+ Table of Contents cdist-type-template creates a new type and adds the usual files to it.
It is thought to be helpful when writing new types. Table of Contents __TYPE ID --parameter value [--parameter value …] __TYPE --parameter value [--parameter value …] (for singletons) Types are the main component of cdist and define functionality. If you
+ Table of Contents __TYPE ID --parameter value [--parameter value …] __TYPE --parameter value [--parameter value …] (for singletons) Types are the main component of cdist and define functionality. If you
use cdist, you’ll write a type for every functionality you would like
to use. You can use types from the initial manifest or the type manifest like a
normal command: Table of Contents This type can be used to check a file for existence of a
+ Table of Contents This type can be used to check a file for existence of a
specific line and adding it, if it was not found. Table of Contents Table of Contents Table of Contents Table of Contents Table of Contents Table of Contents Table of Contents Table of Contents Table of Contents Table of Contents Table of Contents This cdist type allows you to change values in a key value based config
+ Table of Contents Table of Contents This cdist type allows you to hard and symoblic links. The given
+ Table of Contents This cdist type allows you to hard and symoblic links. The given
object id is the destination for the link. Table of Contents Table of Contents Table of Contents This cdist type allows you to install or uninstall packages on the target.
+ Table of Contents This cdist type allows you to install or uninstall packages on the target.
It dispatches the actual work to the package system dependant types.# Bourne shell example
export PATH=$(pwd -P)/bin:$PATH
diff --git a/software/cdist/man/cdist-reference.html b/software/cdist/man/cdist-reference.html
index 6dfeb5bf..096527a1 100644
--- a/software/cdist/man/cdist-reference.html
+++ b/software/cdist/man/cdist-reference.html
@@ -1,6 +1,6 @@
-
# Creates empty file /etc/cdist-configured
diff --git a/software/cdist/man/cdist-type__addifnosuchline.html b/software/cdist/man/cdist-type__addifnosuchline.html
index 5a72ee75..6cb20d10 100644
--- a/software/cdist/man/cdist-type__addifnosuchline.html
+++ b/software/cdist/man/cdist-type__addifnosuchline.html
@@ -1,6 +1,6 @@
-