From 76725c1b0db5923069fdc5734c37551a2efa68a6 Mon Sep 17 00:00:00 2001
From: Nico Schottelius <nico@kr.ethz.ch>
Date: Fri, 25 Mar 2011 23:43:23 +0100
Subject: [PATCH] begin to document cache

Signed-off-by: Nico Schottelius <nico@kr.ethz.ch>
---
 doc/dev/todo/niconext    | 25 ++-------------------
 doc/man/cdist-cache.text | 47 ++++++++++++++++++++++++++++++++++++++++
 2 files changed, 49 insertions(+), 23 deletions(-)
 create mode 100644 doc/man/cdist-cache.text

diff --git a/doc/dev/todo/niconext b/doc/dev/todo/niconext
index ada791ca..6b0891a2 100644
--- a/doc/dev/todo/niconext
+++ b/doc/dev/todo/niconext
@@ -1,27 +1,6 @@
-Core:
-   - support $__self = relative_type/object_id
-
 Cache:
-   - add manpage
    - add example how to use 
    - export variable $__cache
       -> to all hosts or this host?
-
-   Assume you want to configure stuff one host ("monitor node"),
-   depending on the configuration of other hosts ("cluster nodes").
-
-   For instance, the monitor host would like to know,
-   which hosts are configured with the provider
-   "apache" and option --start true.
-
-   This requires the monitor node to be able to
-   query all other configured nodes. It can't
-   ask for all hosts, because cdist does not
-   know which hosts are configured or may exist.
-
-   Example implementation
-
-   If cdist keeps ("caches") the configuration of every
-   node it configures, each new node can query the
-   cache for existing nodes that acquired the given
-   configuration.
+Core:
+   - support $__self = relative_type/object_id
diff --git a/doc/man/cdist-cache.text b/doc/man/cdist-cache.text
new file mode 100644
index 00000000..cbf4c9d7
--- /dev/null
+++ b/doc/man/cdist-cache.text
@@ -0,0 +1,47 @@
+cdist-cache(1)
+==============
+Nico Schottelius <nico-cdist--@--schottelius.org>
+
+
+NAME
+----
+cdist-cache - Cache output of last run
+
+
+SYNOPSIS
+--------
+cdist-cache TARGET_HOST
+
+
+DESCRIPTION
+-----------
+
+   Assume you want to configure stuff one host ("monitor node"),
+   depending on the configuration of other hosts ("cluster nodes").
+
+   For instance, the monitor host would like to know,
+   which hosts are configured with the provider
+   "apache" and option --start true.
+
+   This requires the monitor node to be able to
+   query all other configured nodes. It can't
+   ask for all hosts, because cdist does not 
+   know which hosts are configured or may exist.
+
+   Example implementation
+
+   If cdist keeps ("caches") the configuration of every
+   node it configures, each new node can query the 
+   cache for existing nodes that acquired the given
+   configuration.
+
+
+SEE ALSO
+--------
+cdist(7)
+
+
+COPYING
+-------
+Copyright \(C) 2011 Nico Schottelius. Free use of this software is
+granted under the terms of the GNU General Public License version 3 (GPLv3).