Merge branch '0.24.x'

Conflicts:

	install.rb
	lib/puppet/defaults.rb
	man/man8/puppet.8

10 files changed, 2650 insertions, 77 deletions

diff --git a/man/man8/filebucket.8 b/man/man8/filebucket.8
new file mode 100644
index 000000000..fdaca9f31
--- /dev/null
+++ b/man/man8/filebucket.8
@@ -0,0 +1,116 @@
+.TH   "" "" ""
+.SH NAME
+ \- 
+
+.\" Man page generated from reStructeredText.
+
+.SH SYNOPSIS
+A stand\-alone Puppet filebucket client.
+
+
+.SH USAGE
+
+.\" visit_block_quote
+
+.TP
+.B filebucket [\-h|\-\-help] [\-V|\-\-version] [\-d|\-\-debug] [\-v|\-\-verbose]
+[\-l|\-\-local] [\-r|\-\-remote]
+[\-s|\-\-server <server>] [\-b|\-\-bucket <directory>] <file> <file> ...
+
+
+.\" depart_block_quote
+
+.SH DESCRIPTION
+This is a stand\-alone filebucket client for sending files to a local or
+central filebucket.
+
+
+.SH USAGE
+This client can operate in three modes, with only one mode per call:
+
+
+.TP
+.B backup:  Send one or more files to the specified file bucket. Each sent
+file is printed with its resulting md5 sum.
+
+
+.TP
+.B get:     Return the text associated with an md5 sum. The text is printed
+to stdout, and only one file can be retrieved at a time.
+
+
+.TP
+.B restore: Given a file path and an md5 sum, store the content associated
+with the sum into the specified file path. You can specify an
+entirely new path to this argument; you are not restricted to
+restoring the content to its original location.
+
+Note that +filebucket+ defaults to using a network\-based filebucket
+available on the server named +puppet+. To use this, you\'ll have to be
+running as a user with valid Puppet certificates. Alternatively, you can
+use your local file bucket by specifying +\-\-local+.
+
+
+.SH EXAMPLE
+
+.\" visit_block_quote
+$ filebucket backup /etc/passwd
+/etc/passwd: 429b225650b912a2ee067b0a4cf1e949
+$ filebucket restore /tmp/passwd 429b225650b912a2ee067b0a4cf1e949
+$
+
+
+.\" depart_block_quote
+
+.SH OPTIONS
+Note that any configuration parameter that\'s valid in the configuration
+file is also a valid long argument. For example, \'ssldir\' is a valid
+configuration parameter, so you can specify \'\-\-ssldir <directory>\' as an
+argument.
+
+See the configuration file documentation at
+http://reductivelabs.com/projects/puppet/reference/configref.html for
+the full list of acceptable parameters. A commented list of all
+configuration options can also be generated by running puppet with
+\'\-\-genconfig\'.
+
+debug:   Enable full debugging.
+
+help:    Print this help message
+
+
+.TP
+.B local:   Use the local filebucket. This will use the default
+configuration information.
+
+
+.TP
+.B remote:  Use a remote filebucket. This will use the default
+configuration information.
+
+server:  The server to send the file to, instead of locally.
+
+verbose: Print extra information.
+
+version: Print version information.
+
+
+.SH EXAMPLE
+
+.\" visit_block_quote
+filebucket \-b /tmp/filebucket /my/file
+
+
+.\" depart_block_quote
+
+.SH AUTHOR
+Luke Kanies
+
+
+.SH COPYRIGHT
+Copyright (c) 2005 Reductive Labs, LLC Licensed under the GNU Public
+License
+
+
+.\" Generated by docutils manpage writer on 2008-03-22 17:46.
+.\" 
diff --git a/man/man8/pi.8 b/man/man8/pi.8
new file mode 100644
index 000000000..da13d8e52
--- /dev/null
+++ b/man/man8/pi.8
@@ -0,0 +1,34 @@
+.TH   "" "" ""
+.SH NAME
+ \- 
+
+.\" Man page generated from reStructeredText.
+
+.TP
+.B bin/pi [options] [type]
+
+.TP
+.B Print documentation for puppet types and their parameters
+
+.TP
+.B \-l , \-\-list
+List all types
+
+
+.TP
+.B \-p , \-\-providers
+Describe providers in detail
+
+
+.TP
+.B \-s , \-\-short
+Only list parameters without detail
+
+
+.TP
+.B \-m , \-\-meta
+Include metaparams
+
+
+.\" Generated by docutils manpage writer on 2008-03-22 17:46.
+.\" 
diff --git a/man/man8/puppet.8 b/man/man8/puppet.8
index 2eefc6a0a..0281d330e 100644
--- a/man/man8/puppet.8
+++ b/man/man8/puppet.8
@@ -20,81 +20,10 @@ Run a stand\-alone +puppet+ script.
 .\" depart_block_quote
 
 .SH DESCRIPTION
+This is the standalone puppet execution script; use it to execute
+individual scripts that you write. If you need to execute site\-wide
+scripts, use +puppetd+ and +puppetmasterd+.
 
-This document is intended as a secondary reference only.  Please refer to the complete documentation on the
-.B puppet
-website:
-.PP
-\h"4"http://www.reductivelabs.com/trac/puppet/wiki/DocumentationStart
-.PP
-Every 
-.B puppet
-executable (with the exception of 
-.B puppetdoc
-) accepts all of the arguments below, but not all of the arguments make sense for every executable. Each argument has a section listed with it in parentheses; often, that section will map to an executable (e.g., 
-.B puppetd
-), in which case it probably only makes sense for that one executable. If 
-.B puppet
-is listed as the section, it is most likely an option that is valid for everyone.
-.PP
-This will not always be the case. I have tried to be as thorough as possible in the descriptions of the arguments, so it should be obvious whether an argument is appropriate or not.
-.PP
-These arguments can be supplied to the executables either as command-line arugments or in the configuration file for the appropriate executable. For instance, the command-line invocation below would set the configuration directory to /private/puppet:
-.PP
-\h"4"$ puppetd --confdir=/private/puppet
-.PP
-Note that boolean options are turned on and off with a slightly different syntax on the command line:
-.PP
-\h"4"$ puppetd --storeconfigs
-.PP
-\h"4"$ puppetd --no-storeconfigs
-.PP
-The invocations above will enable and disable, respectively, the storage of the client configuration.
-.PP
-As mentioned above, the configuration parameters can also be stored in a configuration file located in the configuration directory (/etc/puppet by default). The file is called puppet.conf.
-.PP
-The file, which follows INI-style formatting, should contain a bracketed heading named for each executable, followed by pairs of parameters with their values. Here is an example of a very simple puppet.conf file:
-.PP
-\h"4"[puppetd]
-.br
-\h"4"confdir = /private/puppet
-.br
-\h"4"storeconfigs = true
-.br
-.PP
-Note that boolean parameters must be explicitly specified as true or false as seen above.
-.PP
-If you're starting out with a fresh configuration, you may wish to let the executable generate a template configuration file for you by invoking the executable in question with the --genconfig command. The executable will print a template configuration to standard output, which can be redirected to a file like so:
-.PP
-\h"4"$ puppetd --genconfig > /etc/puppet/puppet.conf
-.PP
-Note that this invocation will "clobber" (throw away) the contents of any pre-existing puppet.conf file, so make a backup of your present config if it contains valuable information.
-.PP
-Like the --genconfig argument, the executables also accept a --genmanifest argument, which will generate a manifest that can be used to manage all of 
-.B Puppet's
-directories and files and prints it to standard output. This can likewise be redirected to a file:
-.PP
-\h"4"$ puppetd --genmanifest > /etc/puppet/manifests/site.pp
-.PP
-.B Puppet
-can also create user and group accounts for itself (one puppet group and one puppet user) if it is invoked as root with the --mkusers argument:
-.PP
-\h"4"$ puppetd --mkusers
-.PP
-.SH SIGNALS
-The 
-.B puppetd
-and
-.B puppetmasterd
-executables catch some signals for special handling. Both daemons catch (SIGHUP), which forces the server to restart tself. Predictably, interrupt and terminate (SIGINT and SIGHUP) will shut down the server, whether it be an instance of 
-.B puppetd
-or
-.B puppetmasterd.
-.PP
-Sending the SIGUSR1 signal to an instance of 
-.B puppetd
-will cause it to immediately begin a new configuration transaction with the server. This signal has no effect on 
-.B puppetmasterd.
 
 .SH OPTIONS
 Note that any configuration parameter that\'s valid in the configuration
@@ -138,12 +67,11 @@ puppet \-l /tmp/script.log script.pp
 
 .SH AUTHOR
 Luke Kanies
-
-
+.\" Generated by docutils manpage writer on 2008-01-20 10:28.
 .SH COPYRIGHT
 Copyright (c) 2005 Reductive Labs, LLC Licensed under the GNU Public
 License
 
 
-.\" Generated by docutils manpage writer on 2008-01-20 10:28.
+.\" Generated by docutils manpage writer on 2008-03-22 17:46.
 .\" 
diff --git a/man/man8/puppet.conf.8 b/man/man8/puppet.conf.8
new file mode 100644
index 000000000..e8040fb8e
--- /dev/null
+++ b/man/man8/puppet.conf.8
@@ -0,0 +1,1747 @@
+.TH Configuration Reference  "" "" ""
+.SH NAME
+Configuration Reference \- 
+
+.\" Man page generated from reStructeredText.
+This page is autogenerated; any changes will get overwritten 
+.I (last generated on Sat Mar 22 17:46:15 +1100 2008)
+
+
+
+.\" topic: Contents
+.\" 
+.\" Specifying Configuration Parameters
+.\" 
+.\" Signals
+.\" 
+.\" Configuration Parameter Reference
+
+.SH Specifying Configuration Parameters
+
+.SS On The Command\-Line
+Every Puppet executable (with the exception of 
+.\" visit_literal
+puppetdoc
+.\" depart_literal
+) accepts all of
+the parameters below, but not all of the arguments make sense for every executable.
+Each parameter has a section listed with it in parentheses; often, that section
+will map to an executable (e.g., 
+.\" visit_literal
+puppetd
+.\" depart_literal
+), in which case it probably only
+makes sense for that one executable.  If 
+.\" visit_literal
+main
+.\" depart_literal
+ is listed as the section,
+it is most likely an option that is valid for everyone.
+
+I have tried to be as thorough as possible in the descriptions of the
+arguments, so it should be obvious whether an argument is appropriate or not.
+
+These parameters can be supplied to the executables either as command\-line
+options or in the configuration file.  For instance, the command\-line
+invocation below would set the configuration directory to 
+.\" visit_literal
+/private/puppet
+.\" depart_literal
+:
+
+
+.nf
+$ puppetd \-\-confdir=/private/puppet
+.fi
+Note that boolean options are turned on and off with a slightly different
+syntax on the command line:
+
+
+.nf
+$ puppetd \-\-storeconfigs
+
+$ puppetd \-\-no\-storeconfigs
+.fi
+The invocations above will enable and disable, respectively, the storage of
+the client configuration.
+
+
+.SS Configuration Files
+As mentioned above, the configuration parameters can also be stored in a
+configuration file, located in the configuration directory.  As root, the
+default configuration directory is 
+.\" visit_literal
+/etc/puppet
+.\" depart_literal
+, and as a regular user, the
+default configuration directory is 
+.\" visit_literal
+~user/.puppet
+.\" depart_literal
+.  As of 0.23.0, all
+executables look for 
+.\" visit_literal
+puppet.conf
+.\" depart_literal
+ in their configuration directory
+(although they previously looked for separate files).  For example,
+
+.\" visit_literal
+puppet.conf
+.\" depart_literal
+ is located at 
+.\" visit_literal
+/etc/puppet/puppet.conf
+.\" depart_literal
+ as root and
+
+.\" visit_literal
+~user/.puppet/puppet.conf
+.\" depart_literal
+ as a regular user by default.
+
+All executables will set any parameters set within the 
+.\" visit_literal
+main
+.\" depart_literal
+ section,
+while each executable will also look for a section named for the executable
+and load those parameters.  For example, 
+.\" visit_literal
+puppetd
+.\" depart_literal
+ will look for a
+section named 
+.\" visit_literal
+puppetd
+.\" depart_literal
+, and 
+.\" visit_literal
+puppetmasterd
+.\" depart_literal
+ looks for a section
+named 
+.\" visit_literal
+puppetmasterd
+.\" depart_literal
+.  This allows you to use a single configuration file
+to customize the settings for all of your executables.
+
+
+.SS File Format
+The file follows INI\-style formatting.  Here is an example of a very simple
+
+.\" visit_literal
+puppet.conf
+.\" depart_literal
+ file:
+
+
+.nf
+[main]
+    confdir = /private/puppet
+    storeconfigs = true
+.fi
+Note that boolean parameters must be explicitly specified as 
+.I true
+ or
+
+.I false
+ as seen above.
+
+If you need to change file parameters (e.g., reset the mode or owner), do
+so within curly braces on the same line:
+
+
+.nf
+[main]
+    myfile = /tmp/whatever {owner = root, mode = 644}
+.fi
+If you\'re starting out with a fresh configuration, you may wish to let
+the executable generate a template configuration file for you by invoking
+the executable in question with the 
+.I \-\-genconfig
+ command.  The executable
+will print a template configuration to standard output, which can be
+redirected to a file like so:
+
+
+.nf
+$ puppetd \-\-genconfig > /etc/puppet/puppet.conf
+.fi
+Note that this invocation will replace the contents of any pre\-existing
+
+.I puppet.conf
+ file, so make a backup of your present config if it contains
+valuable information.
+
+All parameters will be under a single section heading matching the name of
+the process used to generate the configuraiton (\'puppetd\', in this case).
+
+Like the 
+.I \-\-genconfig
+ argument, the executables also accept a 
+.I \-\-genmanifest
+
+argument, which will generate a manifest that can be used to manage all of
+Puppet\'s directories and files and prints it to standard output.  This can
+likewise be redirected to a file:
+
+
+.nf
+$ puppetd \-\-genmanifest > /etc/puppet/manifests/site.pp
+.fi
+Puppet can also create user and group accounts for itself (one 
+.I puppet
+ group
+and one 
+.I puppet
+ user) if it is invoked as 
+.I root
+ with the 
+.I \-\-mkusers
+ argument:
+
+
+.nf
+$ puppetd \-\-mkusers
+.fi
+
+.SH Signals
+The 
+.\" visit_literal
+puppetd
+.\" depart_literal
+ and 
+.\" visit_literal
+puppetmasterd
+.\" depart_literal
+ executables catch some signals for special
+handling.  Both daemons catch (
+.\" visit_literal
+SIGHUP
+.\" depart_literal
+), which forces the server to restart
+tself.  Predictably, interrupt and terminate (
+.\" visit_literal
+SIGINT
+.\" depart_literal
+ and 
+.\" visit_literal
+SIGHUP
+.\" depart_literal
+) will shut
+down the server, whether it be an instance of 
+.\" visit_literal
+puppetd
+.\" depart_literal
+ or 
+.\" visit_literal
+puppetmasterd
+.\" depart_literal
+.
+
+Sending the 
+.\" visit_literal
+SIGUSR1
+.\" depart_literal
+ signal to an instance of 
+.\" visit_literal
+puppetd
+.\" depart_literal
+ will cause it to
+immediately begin a new configuration transaction with the server.  This
+signal has no effect on 
+.\" visit_literal
+puppetmasterd
+.\" depart_literal
+.
+
+
+.SH Configuration Parameter Reference
+Below is a list of all documented parameters.  Not all of them are valid with all
+Puppet executables, but the executables will ignore any inappropriate values.
+
+
+.SS authconfig
+The configuration file that defines the rights to the different namespaces and methods.  This can be used as a coarse\-grained authorization system for both 
+.\" visit_literal
+puppetd
+.\" depart_literal
+ and 
+.\" visit_literal
+puppetmasterd
+.\" depart_literal
+.
+
+
+.TP 2
+\(bu
+Default: $confdir/namespaceauth.conf
+
+
+.SS autoflush
+Whether log files should always flush to disk.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS autosign
+Whether to enable autosign.  Valid values are true (which autosigns any key request, and is a very bad idea), false (which never autosigns any key request), and the path to a file, which uses that configuration file to determine which keys to sign.
+
+
+.TP 2
+\(bu
+Default: $confdir/autosign.conf
+
+
+.SS bindaddress
+The address to bind to.  Mongrel servers default to 127.0.0.1 and WEBrick defaults to 0.0.0.0.
+
+
+.SS bucketdir
+Where FileBucket files are stored.
+
+
+.TP 2
+\(bu
+Default: $vardir/bucket
+
+
+.SS ca
+Wether the master should function as a certificate authority.
+
+
+.TP 2
+\(bu
+Default: true
+
+
+.SS ca_days
+How long a certificate should be valid.  This parameter is deprecated, use ca_ttl instead
+
+
+.SS ca_md
+The type of hash used in certificates.
+
+
+.TP 2
+\(bu
+Default: md5
+
+
+.SS ca_port
+The port to use for the certificate authority.
+
+
+.TP 2
+\(bu
+Default: $masterport
+
+
+.SS ca_server
+The server to use for certificate authority requests.  It\'s a separate server because it cannot and does not need to horizontally scale.
+
+
+.TP 2
+\(bu
+Default: $server
+
+
+.SS ca_ttl
+The default TTL for new certificates; valid values  must be an integer, optionally followed by one of the units  \'y\' (years of 365 days), \'d\' (days), \'h\' (hours), or  \'s\' (seconds). The unit defaults to seconds. If this parameter is set, ca_days is ignored. Examples are \'3600\' (one hour)  and \'1825d\', which is the same as \'5y\' (5 years)
+
+
+.TP 2
+\(bu
+Default: 5y
+
+
+.SS cacert
+The CA certificate.
+
+
+.TP 2
+\(bu
+Default: $cadir/ca_crt.pem
+
+
+.SS cacrl
+The certificate revocation list (CRL) for the CA. Set this to \'false\' if you do not want to use a CRL.
+
+
+.TP 2
+\(bu
+Default: $cadir/ca_crl.pem
+
+
+.SS cadir
+The root directory for the certificate authority.
+
+
+.TP 2
+\(bu
+Default: $ssldir/ca
+
+
+.SS cakey
+The CA private key.
+
+
+.TP 2
+\(bu
+Default: $cadir/ca_key.pem
+
+
+.SS capass
+Where the CA stores the password for the private key
+
+
+.TP 2
+\(bu
+Default: $caprivatedir/ca.pass
+
+
+.SS caprivatedir
+Where the CA stores private certificate information.
+
+
+.TP 2
+\(bu
+Default: $cadir/private
+
+
+.SS capub
+The CA public key.
+
+
+.TP 2
+\(bu
+Default: $cadir/ca_pub.pem
+
+
+.SS casesensitive
+Whether matching in case statements and selectors should be case\-sensitive.  Case insensitivity is handled by downcasing all values before comparison.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS cert_inventory
+A Complete listing of all certificates
+
+
+.TP 2
+\(bu
+Default: $cadir/inventory.txt
+
+
+.SS certdir
+The certificate directory.
+
+
+.TP 2
+\(bu
+Default: $ssldir/certs
+
+
+.SS certdnsnames
+The DNS names on the Server certificate as a colon\-separated list. If it\'s anything other than an empty string, it will be used as an alias in the created certificate.  By default, only the server gets an alias set up, and only for \'puppet\'.
+
+
+.SS certname
+The name to use when handling certificates.  Defaults to the fully qualified domain name.
+
+
+.TP 2
+\(bu
+Default: absinthe.lovedthanlost.net
+
+
+.SS classfile
+The file in which puppetd stores a list of the classes associated with the retrieved configuration.  Can be loaded in the separate 
+.\" visit_literal
+puppet
+.\" depart_literal
+ executable using the 
+.\" visit_literal
+\-\-loadclasses
+.\" depart_literal
+ option.
+
+
+.TP 2
+\(bu
+Default: $statedir/classes.txt
+
+
+.SS clientbucketdir
+Where FileBucket files are stored locally.
+
+
+.TP 2
+\(bu
+Default: $vardir/clientbucket
+
+
+.SS code
+Code to parse directly.  This is essentially only used by 
+.\" visit_literal
+puppet
+.\" depart_literal
+, and should only be set if you\'re writing your own Puppet executable
+
+
+.SS color
+Whether to use colors when logging to the console. Valid values are 
+.\" visit_literal
+ansi
+.\" depart_literal
+ (equivalent to 
+.\" visit_literal
+true
+.\" depart_literal
+), 
+.\" visit_literal
+html
+.\" depart_literal
+ (mostly used during testing with TextMate), and 
+.\" visit_literal
+false
+.\" depart_literal
+, which produces no color.
+
+
+.TP 2
+\(bu
+Default: ansi
+
+
+.SS confdir
+The main Puppet configuration directory.  The default for this parameter is calculated based on the user.  If the process is runnig as root or the user that 
+.\" visit_literal
+puppetmasterd
+.\" depart_literal
+ is supposed to run as, it defaults to a system directory, but if it\'s running as any other user, it defaults to being in 
+.\" visit_literal
+~
+.\" depart_literal
+.
+
+
+.TP 2
+\(bu
+Default: /etc/puppet
+
+
+.SS config
+The configuration file for puppetdoc.
+
+
+.TP 2
+\(bu
+Default: $confdir/puppet.conf
+
+
+.SS configprint
+Print the value of a specific configuration parameter.  If a parameter is provided for this, then the value is printed and puppet exits.  Comma\-separate multiple values.  For a list of all values, specify \'all\'.  This feature is only available in Puppet versions higher than 0.18.4.
+
+
+.SS configtimeout
+How long the client should wait for the configuration to be retrieved before considering it a failure.  This can help reduce flapping if too many clients contact the server at one time.
+
+
+.TP 2
+\(bu
+Default: 120
+
+
+.SS csrdir
+Where the CA stores certificate requests
+
+
+.TP 2
+\(bu
+Default: $cadir/requests
+
+
+.SS daemonize
+Send the process into the background.  This is the default.
+
+
+.TP 2
+\(bu
+Default: true
+
+
+.SS dbadapter
+The type of database to use.
+
+
+.TP 2
+\(bu
+Default: sqlite3
+
+
+.SS dblocation
+The database cache for client configurations.  Used for querying within the language.
+
+
+.TP 2
+\(bu
+Default: $statedir/clientconfigs.sqlite3
+
+
+.SS dbmigrate
+Whether to automatically migrate the database.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS dbname
+The name of the database to use.
+
+
+.TP 2
+\(bu
+Default: puppet
+
+
+.SS dbpassword
+The database password for Client caching. Only used when networked databases are used.
+
+
+.TP 2
+\(bu
+Default: puppet
+
+
+.SS dbserver
+The database server for Client caching. Only used when networked databases are used.
+
+
+.TP 2
+\(bu
+Default: localhost
+
+
+.SS dbsocket
+The database socket location. Only used when networked databases are used.  Will be ignored if the value is an empty string.
+
+
+.SS dbuser
+The database user for Client caching. Only used when networked databases are used.
+
+
+.TP 2
+\(bu
+Default: puppet
+
+
+.SS diff
+Which diff command to use when printing differences between files.
+
+
+.TP 2
+\(bu
+Default: diff
+
+
+.SS diff_args
+Which arguments to pass to the diff command when printing differences between files.
+
+
+.SS downcasefacts
+Whether facts should be made all lowercase when sent to the server.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS dynamicfacts
+Facts that are dynamic; these facts will be ignored when deciding whether changed facts should result in a recompile.  Multiple facts should be comma\-separated.
+
+
+.TP 2
+\(bu
+Default: memorysize,memoryfree,swapsize,swapfree
+
+
+.SS environment
+The environment Puppet is running in.  For clients (e.g., 
+.\" visit_literal
+puppetd
+.\" depart_literal
+) this determines the environment itself, which is used to find modules and much more.  For servers (i.e., 
+.\" visit_literal
+puppetmasterd
+.\" depart_literal
+) this provides the default environment for nodes we know nothing about.
+
+
+.TP 2
+\(bu
+Default: development
+
+
+.SS environments
+The valid environments for Puppet clients. This is more useful as a server\-side setting than client, but any environment chosen must be in this list.  Values should be separated by a comma.
+
+
+.TP 2
+\(bu
+Default: production,development
+
+
+.SS evaltrace
+Whether each resource should log when it is being evaluated.  This allows you to interactively see exactly what is being done.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS external_nodes
+An external command that can produce node information.  The output must be a YAML dump of a hash, and that hash must have one or both of 
+.\" visit_literal
+classes
+.\" depart_literal
+ and 
+.\" visit_literal
+parameters
+.\" depart_literal
+, where 
+.\" visit_literal
+classes
+.\" depart_literal
+ is an array and 
+.\" visit_literal
+parameters
+.\" depart_literal
+ is a hash.  For unknown nodes, the commands should exit with a non\-zero exit code. This command makes it straightforward to store your node mapping information in other data sources like databases.
+
+
+.TP 2
+\(bu
+Default: none
+
+
+.SS factdest
+Where Puppet should store facts that it pulls down from the central server.
+
+
+.TP 2
+\(bu
+Default: $vardir/facts
+
+
+.SS factpath
+Where Puppet should look for facts.  Multiple directories should be colon\-separated, like normal PATH variables.
+
+
+.TP 2
+\(bu
+Default: $vardir/facts
+
+
+.SS factsignore
+What files to ignore when pulling down facts.
+
+
+.TP 2
+\(bu
+Default: .svn CVS
+
+
+.SS factsource
+From where to retrieve facts.  The standard Puppet 
+.\" visit_literal
+file
+.\" depart_literal
+ type is used for retrieval, so anything that is a valid file source can be used here.
+
+
+.TP 2
+\(bu
+Default: puppet://$server/facts
+
+
+.SS factsync
+Whether facts should be synced with the central server.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS fileserverconfig
+Where the fileserver configuration is stored.
+
+
+.TP 2
+\(bu
+Default: $confdir/fileserver.conf
+
+
+.SS filetimeout
+The minimum time to wait (in seconds) between checking for updates in configuration files.  This timeout determines how quickly Puppet checks whether a file (such as manifests or templates) has changed on disk.
+
+
+.TP 2
+\(bu
+Default: 15
+
+
+.SS genconfig
+Whether to just print a configuration to stdout and exit.  Only makes sense when used interactively.  Takes into account arguments specified on the CLI.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS genmanifest
+Whether to just print a manifest to stdout and exit.  Only makes sense when used interactively.  Takes into account arguments specified on the CLI.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS graph
+Whether to create dot graph files for the different configuration graphs.  These dot files can be interpreted by tools like OmniGraffle or dot (which is part of ImageMagick).
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS graphdir
+Where to store dot\-outputted graphs.
+
+
+.TP 2
+\(bu
+Default: $statedir/graphs
+
+
+.SS group
+The group puppetmasterd should run as.
+
+
+.TP 2
+\(bu
+Default: puppet
+
+
+.SS hostcert
+Where individual hosts store and look for their certificates.
+
+
+.TP 2
+\(bu
+Default: $certdir/$certname.pem
+
+
+.SS hostcsr
+Where individual hosts store and look for their certificates.
+
+
+.TP 2
+\(bu
+Default: $ssldir/csr_$certname.pem
+
+
+.SS hostprivkey
+Where individual hosts store and look for their private key.
+
+
+.TP 2
+\(bu
+Default: $privatekeydir/$certname.pem
+
+
+.SS hostpubkey
+Where individual hosts store and look for their public key.
+
+
+.TP 2
+\(bu
+Default: $publickeydir/$certname.pem
+
+
+.SS http_enable_post_connection_check
+Boolean; wheter or not puppetd should validate the server SSL certificate against the request hostname.
+
+
+.TP 2
+\(bu
+Default: true
+
+
+.SS http_proxy_host
+The HTTP proxy host to use for outgoing connections.  Note: You may need to use a FQDN for the server hostname when using a proxy.
+
+
+.TP 2
+\(bu
+Default: none
+
+
+.SS http_proxy_port
+The HTTP proxy port to use for outgoing connections
+
+
+.TP 2
+\(bu
+Default: 3128
+
+
+.SS httplog
+Where the puppetd web server logs.
+
+
+.TP 2
+\(bu
+Default: $logdir/http.log
+
+
+.SS ignorecache
+Ignore cache and always recompile the configuration.  This is useful for testing new configurations, where the local cache may in fact be stale even if the timestamps are up to date \- if the facts change or if the server changes.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS ignoreimport
+A parameter that can be used in commit hooks, since it enables you to parse\-check a single file rather than requiring that all files exist.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS ignoreschedules
+Boolean; whether puppetd should ignore schedules.  This is useful for initial puppetd runs.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS keylength
+The bit length of keys.
+
+
+.TP 2
+\(bu
+Default: 1024
+
+
+.SS ldapattrs
+The LDAP attributes to include when querying LDAP for nodes.  All returned attributes are set as variables in the top\-level scope. Multiple values should be comma\-separated.  The value \'all\' returns all attributes.
+
+
+.TP 2
+\(bu
+Default: all
+
+
+.SS ldapbase
+The search base for LDAP searches.  It\'s impossible to provide a meaningful default here, although the LDAP libraries might have one already set.  Generally, it should be the \'ou=Hosts\' branch under your main directory.
+
+
+.SS ldapclassattrs
+The LDAP attributes to use to define Puppet classes.  Values should be comma\-separated.
+
+
+.TP 2
+\(bu
+Default: puppetclass
+
+
+.SS ldapnodes
+Whether to search for node configurations in LDAP.  See http://reductivelabs.com/puppet/trac/wiki/LdapNodes/ for more information.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS ldapparentattr
+The attribute to use to define the parent node.
+
+
+.TP 2
+\(bu
+Default: parentnode
+
+
+.SS ldappassword
+The password to use to connect to LDAP.
+
+
+.SS ldapport
+The LDAP port.  Only used if 
+.\" visit_literal
+ldapnodes
+.\" depart_literal
+ is enabled.
+
+
+.TP 2
+\(bu
+Default: 389
+
+
+.SS ldapserver
+The LDAP server.  Only used if 
+.\" visit_literal
+ldapnodes
+.\" depart_literal
+ is enabled.
+
+
+.TP 2
+\(bu
+Default: ldap
+
+
+.SS ldapssl
+Whether SSL should be used when searching for nodes. Defaults to false because SSL usually requires certificates to be set up on the client side.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS ldapstring
+The search string used to find an LDAP node.
+
+
+.TP 2
+\(bu
+Default: (&(objectclass=puppetClient)(cn=%s))
+
+
+.SS ldaptls
+Whether TLS should be used when searching for nodes. Defaults to false because TLS usually requires certificates to be set up on the client side.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS ldapuser
+The user to use to connect to LDAP.  Must be specified as a full DN.
+
+
+.SS lexical
+Whether to use lexical scoping (vs. dynamic).
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS libdir
+An extra search path for Puppet.  This is only useful for those files that Puppet will load on demand, and is only guaranteed to work for those cases.  In fact, the autoload mechanism is responsible for making sure this directory is in Ruby\'s search path
+
+
+.TP 2
+\(bu
+Default: $vardir/lib
+
+
+.SS listen
+Whether puppetd should listen for connections.  If this is true, then by default only the 
+.\" visit_literal
+runner
+.\" depart_literal
+ server is started, which allows remote authorized and authenticated nodes to connect and trigger 
+.\" visit_literal
+puppetd
+.\" depart_literal
+ runs.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS localcacert
+Where each client stores the CA certificate.
+
+
+.TP 2
+\(bu
+Default: $certdir/ca.pem
+
+
+.SS localconfig
+Where puppetd caches the local configuration.  An extension indicating the cache format is added automatically.
+
+
+.TP 2
+\(bu
+Default: $statedir/localconfig
+
+
+.SS logdir
+The Puppet log directory.
+
+
+.TP 2
+\(bu
+Default: $vardir/log
+
+
+.SS manifest
+The entry\-point manifest for puppetmasterd.
+
+
+.TP 2
+\(bu
+Default: $manifestdir/site.pp
+
+
+.SS manifestdir
+Where puppetmasterd looks for its manifests.
+
+
+.TP 2
+\(bu
+Default: $confdir/manifests
+
+
+.SS masterhttplog
+Where the puppetmasterd web server logs.
+
+
+.TP 2
+\(bu
+Default: $logdir/masterhttp.log
+
+
+.SS masterlog
+Where puppetmasterd logs.  This is generally not used, since syslog is the default log destination.
+
+
+.TP 2
+\(bu
+Default: $logdir/puppetmaster.log
+
+
+.SS masterport
+Which port puppetmasterd listens on.
+
+
+.TP 2
+\(bu
+Default: 8140
+
+
+.SS maximum_uid
+The maximum allowed UID.  Some platforms use negative UIDs but then ship with tools that do not know how to handle signed ints, so the UIDs show up as huge numbers that can then not be fed back into the system.  This is a hackish way to fail in a slightly more useful way when that happens.
+
+
+.TP 2
+\(bu
+Default: 4294967290
+
+
+.SS mkusers
+Whether to create the necessary user and group that puppetd will run as.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS modulepath
+The search path for modules as a colon\-separated list of directories.
+
+
+.TP 2
+\(bu
+Default: $confdir/modules:/usr/share/puppet/modules
+
+
+.SS name
+The name of the service, if we are running as one.  The default is essentially $0 without the path or 
+.\" visit_literal
+.rb
+.\" depart_literal
+.
+
+
+.TP 2
+\(bu
+Default: puppetdoc
+
+
+.SS node_name
+How the puppetmaster determines the client\'s identity  and sets the \'hostname\', \'fqdn\' and \'domain\' facts for use in the manifest,  in particular for determining which \'node\' statement applies to the client.  Possible values are \'cert\' (use the subject\'s CN in the client\'s  certificate) and \'facter\' (use the hostname that the client  reported in its facts)
+
+
+.TP 2
+\(bu
+Default: cert
+
+
+.SS node_terminus
+Where to find information about nodes.
+
+
+.TP 2
+\(bu
+Default: plain
+
+
+.SS noop
+Whether puppetd should be run in noop mode.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS paramcheck
+Whether to validate parameters during parsing.
+
+
+.TP 2
+\(bu
+Default: true
+
+
+.SS parseonly
+Just check the syntax of the manifests.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS passfile
+Where puppetd stores the password for its private key. Generally unused.
+
+
+.TP 2
+\(bu
+Default: $privatedir/password
+
+
+.SS path
+The shell search path.  Defaults to whatever is inherited from the parent process.
+
+
+.TP 2
+\(bu
+Default: none
+
+
+.SS pidfile
+The pid file
+
+
+.SS plugindest
+Where Puppet should store plugins that it pulls down from the central server.
+
+
+.TP 2
+\(bu
+Default: $libdir
+
+
+.SS pluginpath
+Where Puppet should look for plugins.  Multiple directories should be colon\-separated, like normal PATH variables.  As of 0.23.1, this option is deprecated; download your custom libraries to the $libdir instead.
+
+
+.TP 2
+\(bu
+Default: $vardir/plugins
+
+
+.SS pluginsignore
+What files to ignore when pulling down plugins.
+
+
+.TP 2
+\(bu
+Default: .svn CVS
+
+
+.SS pluginsource
+From where to retrieve plugins.  The standard Puppet 
+.\" visit_literal
+file
+.\" depart_literal
+ type is used for retrieval, so anything that is a valid file source can be used here.
+
+
+.TP 2
+\(bu
+Default: puppet://$server/plugins
+
+
+.SS pluginsync
+Whether plugins should be synced with the central server.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS privatedir
+Where the client stores private certificate information.
+
+
+.TP 2
+\(bu
+Default: $ssldir/private
+
+
+.SS privatekeydir
+The private key directory.
+
+
+.TP 2
+\(bu
+Default: $ssldir/private_keys
+
+
+.SS publickeydir
+The public key directory.
+
+
+.TP 2
+\(bu
+Default: $ssldir/public_keys
+
+
+.SS puppetdlockfile
+A lock file to temporarily stop puppetd from doing anything.
+
+
+.TP 2
+\(bu
+Default: $statedir/puppetdlock
+
+
+.SS puppetdlog
+The log file for puppetd.  This is generally not used.
+
+
+.TP 2
+\(bu
+Default: $logdir/puppetd.log
+
+
+.SS puppetport
+Which port puppetd listens on.
+
+
+.TP 2
+\(bu
+Default: 8139
+
+
+.SS rails_loglevel
+The log level for Rails connections.  The value must be a valid log level within Rails.  Production environments normally use 
+.\" visit_literal
+info
+.\" depart_literal
+ and other environments normally use 
+.\" visit_literal
+debug
+.\" depart_literal
+.
+
+
+.TP 2
+\(bu
+Default: info
+
+
+.SS railslog
+Where Rails\-specific logs are sent
+
+
+.TP 2
+\(bu
+Default: $logdir/rails.log
+
+
+.SS report
+Whether to send reports after every transaction.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS reportdir
+The directory in which to store reports received from the client.  Each client gets a separate subdirectory.
+
+
+.TP 2
+\(bu
+Default: $vardir/reports
+
+
+.SS reportfrom
+The \'from\' email address for the reports.
+
+
+.TP 2
+\(bu
+Default: report@absinthe.lovedthanlost.net
+
+
+.SS reports
+The list of reports to generate.  All reports are looked for in puppet/reports/<name>.rb, and multiple report names should be comma\-separated (whitespace is okay).
+
+
+.TP 2
+\(bu
+Default: store
+
+
+.SS reportserver
+The server to which to send transaction reports.
+
+
+.TP 2
+\(bu
+Default: $server
+
+
+.SS req_bits
+The bit length of the certificates.
+
+
+.TP 2
+\(bu
+Default: 2048
+
+
+.SS rrddir
+The directory where RRD database files are stored. Directories for each reporting host will be created under this directory.
+
+
+.TP 2
+\(bu
+Default: $vardir/rrd
+
+
+.SS rrdgraph
+Whether RRD information should be graphed.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS rrdinterval
+How often RRD should expect data. This should match how often the hosts report back to the server.
+
+
+.TP 2
+\(bu
+Default: $runinterval
+
+
+.SS rundir
+Where Puppet PID files are kept.
+
+
+.TP 2
+\(bu
+Default: $vardir/run
+
+
+.SS runinterval
+How often puppetd applies the client configuration; in seconds.
+
+
+.TP 2
+\(bu
+Default: 1800
+
+
+.SS sendmail
+Where to find the sendmail binary with which to send email.
+
+
+.SS serial
+Where the serial number for certificates is stored.
+
+
+.TP 2
+\(bu
+Default: $cadir/serial
+
+
+.SS server
+The server to which server puppetd should connect
+
+
+.TP 2
+\(bu
+Default: puppet
+
+
+.SS servertype
+The type of server to use.  Currently supported options are webrick and mongrel.  If you use mongrel, you will need a proxy in front of the process or processes, since Mongrel cannot speak SSL.
+
+
+.TP 2
+\(bu
+Default: webrick
+
+
+.SS show_diff
+Whether to print a contextual diff when files are being replaced.  The diff is printed on stdout, so this option is meaningless unless you are running Puppet interactively. This feature currently requires the 
+.\" visit_literal
+diff/lcs
+.\" depart_literal
+ Ruby library.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS signeddir
+Where the CA stores signed certificates.
+
+
+.TP 2
+\(bu
+Default: $cadir/signed
+
+
+.SS smtpserver
+The server through which to send email reports.
+
+
+.TP 2
+\(bu
+Default: none
+
+
+.SS splay
+Whether to sleep for a pseudo\-random (but consistent) amount of time before a run.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS splaylimit
+The maximum time to delay before runs.  Defaults to being the same as the run interval.
+
+
+.TP 2
+\(bu
+Default: $runinterval
+
+
+.SS ssl_client_header
+The header containing an authenticated client\'s SSL DN.  Only used with Mongrel.  This header must be set by the proxy to the authenticated client\'s SSL DN (e.g., 
+.\" visit_literal
+/CN=puppet.reductivelabs.com
+.\" depart_literal
+). See http://reductivelabs.com/puppet/trac/wiki/UsingMongrel for more information.
+
+
+.TP 2
+\(bu
+Default: HTTP_X_CLIENT_DN
+
+
+.SS ssl_client_verify_header
+The header containing the status message of the client verification. Only used with Mongrel.  This header must be set by the proxy to \'SUCCESS\' if the client successfully authenticated, and anything else otherwise. See http://reductivelabs.com/puppet/trac/wiki/UsingMongrel for more information.
+
+
+.TP 2
+\(bu
+Default: HTTP_X_CLIENT_VERIFY
+
+
+.SS ssldir
+Where SSL certificates are kept.
+
+
+.TP 2
+\(bu
+Default: $confdir/ssl
+
+
+.SS statedir
+The directory where Puppet state is stored.  Generally, this directory can be removed without causing harm (although it might result in spurious service restarts).
+
+
+.TP 2
+\(bu
+Default: $vardir/state
+
+
+.SS statefile
+Where puppetd and puppetmasterd store state associated with the running configuration.  In the case of puppetmasterd, this file reflects the state discovered through interacting with clients.
+
+
+.TP 2
+\(bu
+Default: $statedir/state.yaml
+
+
+.SS storeconfigs
+Whether to store each client\'s configuration.  This requires ActiveRecord from Ruby on Rails.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS summarize
+Whether to print a transaction summary.
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS syslogfacility
+What syslog facility to use when logging to syslog.  Syslog has a fixed list of valid facilities, and you must choose one of those; you cannot just make one up.
+
+
+.TP 2
+\(bu
+Default: daemon
+
+
+.SS tagmap
+The mapping between reporting tags and email addresses.
+
+
+.TP 2
+\(bu
+Default: $confdir/tagmail.conf
+
+
+.SS tags
+Tags to use to find resources.  If this is set, then only resources tagged with the specified tags will be applied. Values must be comma\-separated.
+
+
+.SS templatedir
+Where Puppet looks for template files.
+
+
+.TP 2
+\(bu
+Default: $vardir/templates
+
+
+.SS trace
+Whether to print stack traces on some errors
+
+
+.TP 2
+\(bu
+Default: false
+
+
+.SS typecheck
+Whether to validate types during parsing.
+
+
+.TP 2
+\(bu
+Default: true
+
+
+.SS usecacheonfailure
+Whether to use the cached configuration when the remote configuration will not compile.  This option is useful for testing new configurations, where you want to fix the broken configuration rather than reverting to a known\-good one.
+
+
+.TP 2
+\(bu
+Default: true
+
+
+.SS user
+The user puppetmasterd should run as.
+
+
+.TP 2
+\(bu
+Default: puppet
+
+
+.SS vardir
+Where Puppet stores dynamic and growing data.  The default for this parameter is calculated specially, like confdir.
+
+
+.TP 2
+\(bu
+Default: /var/puppet
+
+
+.SS yamldir
+The directory in which YAML data is stored, usually in a subdirectory.
+
+
+.TP 2
+\(bu
+Default: $vardir/yaml
+
+
+.sp
+.ce
+----
+
+.ce 0
+.sp
+
+.I This page autogenerated on Sat Mar 22 17:46:15 +1100 2008
+
+
+
+.\" Generated by docutils manpage writer on 2008-03-22 17:46.
+.\" 
diff --git a/man/man8/puppetca.8 b/man/man8/puppetca.8
new file mode 100644
index 000000000..42d6c1f1f
--- /dev/null
+++ b/man/man8/puppetca.8
@@ -0,0 +1,116 @@
+.TH   "" "" ""
+.SH NAME
+ \- 
+
+.\" Man page generated from reStructeredText.
+
+.SH SYNOPSIS
+Stand\-alone certificate authority. Capable of generating certificates
+but mostly meant for signing certificate requests from puppet clients.
+
+
+.SH USAGE
+
+.\" visit_block_quote
+
+.TP
+.B puppetca [\-h|\-\-help] [\-V|\-\-version] [\-d|\-\-debug] [\-v|\-\-verbose]
+[\-g|\-\-generate] [\-l|\-\-list] [\-s|\-\-sign] [\-r|\-\-revoke]
+[\-p|\-\-print] [\-c|\-\-clean] [\-\-verify] [host]
+
+
+.\" depart_block_quote
+
+.SH DESCRIPTION
+Because the puppetmasterd daemon defaults to not signing client
+certificate requests, this script is available for signing outstanding
+requests. It can be used to list outstanding requests and then either
+sign them individually or sign all of them.
+
+
+.SH OPTIONS
+Note that any configuration parameter that\'s valid in the configuration
+file is also a valid long argument. For example, \'ssldir\' is a valid
+configuration parameter, so you can specify \'\-\-ssldir <directory>\' as an
+argument.
+
+See the configuration file documentation at
+http://reductivelabs.com/projects/puppet/reference/configref.html for
+the full list of acceptable parameters. A commented list of all
+configuration options can also be generated by running puppetca with
+\'\-\-genconfig\'.
+
+
+.TP
+.B all:      Operate on all outstanding requests. Only makes sense with
+\'\-\-sign\', or \'\-\-list\'.
+
+
+.TP
+.B clean:    Remove all files related to a host from puppetca\'s storage.
+This is useful when rebuilding hosts, since new certificate
+signing requests will only be honored if puppetca does not
+have a copy of a signed certificate for that host. The
+certificate of the host remains valid.
+
+debug:    Enable full debugging.
+
+
+.TP
+.B generate: Generate a certificate for a named client. A
+certificate/keypair will be generated for each client named on
+the command line.
+
+help:     Print this help message
+
+
+.TP
+.B list:     List outstanding certificate requests. If \'\-\-all\' is
+specified, signed certificates are also listed, prefixed by
+\'+\'.
+
+print:    Print the full\-text version of a host\'s certificate.
+
+
+.TP
+.B revoke:   Revoke the certificate of a client. The certificate can be
+specified either by its serial number, given as a decimal
+number or a hexadecimal number prefixed by \'0x\', or by its
+hostname. The certificate is revoked by adding it to the
+Certificate Revocation List given by the \'cacrl\' config
+parameter. Note that the puppetmasterd needs to be restarted
+after revoking certificates.
+
+
+.TP
+.B sign:     Sign an outstanding certificate request. Unless \'\-\-all\' is
+specified, hosts must be listed after all flags.
+
+verbose:  Enable verbosity.
+
+version:  Print the puppet version number and exit.
+
+verify:   Verify the named certificate against the local CA certificate.
+
+
+.SH EXAMPLE
+
+.\" visit_block_quote
+$ puppetca \-l
+culain.madstop.com
+$ puppetca \-s culain.madstop.com
+
+
+.\" depart_block_quote
+
+.SH AUTHOR
+Luke Kanies
+
+
+.SH COPYRIGHT
+Copyright (c) 2005 Reductive Labs, LLC Licensed under the GNU Public
+License
+
+
+.\" Generated by docutils manpage writer on 2008-03-22 17:46.
+.\" 
diff --git a/man/man8/puppetd.8 b/man/man8/puppetd.8
new file mode 100644
index 000000000..83b172809
--- /dev/null
+++ b/man/man8/puppetd.8
@@ -0,0 +1,184 @@
+.TH Synopsis  "" "" ""
+.SH NAME
+Synopsis \- 
+
+.\" Man page generated from reStructeredText.
+Retrieve the client configuration from the central puppet server and
+apply it to the local host.
+
+Currently must be run out periodically, using cron or something similar.
+
+
+.SH USAGE
+
+.\" visit_block_quote
+
+.TP
+.B puppetd  [\-D|\-\-daemonize|\-\-no\-daemonize] [\-d|\-\-debug] [\-\-disable] [\-\-enable]
+[\-h|\-\-help] [\-\-fqdn <host name>] [\-l|\-\-logdest syslog|<file>|console]
+[\-o|\-\-onetime] [\-\-serve <handler>] [\-t|\-\-test]
+[\-V|\-\-version] [\-v|\-\-verbose] [\-w|\-\-waitforcert <seconds>]
+
+
+.\" depart_block_quote
+
+.SH DESCRIPTION
+This is the main puppet client. Its job is to retrieve the local
+machine\'s configuration from a remote server and apply it. In order to
+successfully communicate with the remote server, the client must have a
+certificate signed by a certificate authority that the server trusts;
+the recommended method for this, at the moment, is to run a certificate
+authority as part of the puppet server (which is the default). The
+client will connect and request a signed certificate, and will continue
+connecting until it receives one.
+
+Once the client has a signed certificate, it will retrieve its
+configuration and apply it.
+
+
+.SH USAGE NOTES
++puppetd+ does its best to find a compromise between interactive use and
+daemon use. Run with no arguments and no configuration, it will go into
+the backgroun, attempt to get a signed certificate, and retrieve and
+apply its configuration every 30 minutes.
+
+Some flags are meant specifically for interactive use \-\- in particular,
++test+ and +tags+ are useful. +test+ enables verbose logging, causes the
+daemon to stay in the foreground, exits if the server\'s configuration is
+invalid (this happens if, for instance, you\'ve left a syntax error on
+the server), and exits after running the configuration once (rather than
+hanging around as a long\-running process).
+
++tags+ allows you to specify what portions of a configuration you want
+to apply. Puppet elements are tagged with all of the class or definition
+names that contain them, and you can use the +tags+ flag to specify one
+of these names, causing only configuration elements contained within
+that class or definition to be applied. This is very useful when you are
+testing new configurations \-\- for instance, if you are just starting to
+manage +ntpd+, you would put all of the new elements into an +ntpd+
+class, and call puppet with +\-\-tags ntpd+, which would only apply that
+small portion of the configuration during your testing, rather than
+applying the whole thing.
+
+
+.SH OPTIONS
+Note that any configuration parameter that\'s valid in the configuration
+file is also a valid long argument. For example, \'server\' is a valid
+configuration parameter, so you can specify \'\-\-server <servername>\' as
+an argument.
+
+See the configuration file documentation at
+http://reductivelabs.com/projects/puppet/reference/configref.html for
+the full list of acceptable parameters. A commented list of all
+configuration options can also be generated by running puppetd with
+\'\-\-genconfig\'.
+
+daemonize:    Send the process into the background. This is the default.
+
+no\-daemonize: Do not send the process into the background.
+
+debug:        Enable full debugging.
+
+
+.TP
+.B disable:      Disable working on the local system. This puts a lock file
+in place, causing +puppetd+ not to work on the system
+until the lock file is removed. This is useful if you are
+testing a configuration and do not want the central
+configuration to override the local state until everything
+is tested and committed.
+
++puppetd+ uses the same lock file while it is running, so no more than
+one +puppetd+ process is working at a time.
+
++puppetd+ exits after executing this.
+
+
+.TP
+.B enable:       Enable working on the local system. This removes any lock
+file, causing +puppetd+ to start managing the local system
+again (although it will continue to use its normal
+scheduling, so it might not start for another half hour).
+
++puppetd+ exits after executing this.
+
+
+.TP
+.B fqdn:         Set the fully\-qualified domain name of the client. This is
+only used for certificate purposes, but can be used to
+override the discovered hostname. If you need to use this
+flag, it is generally an indication of a setup problem.
+
+help:         Print this help message
+
+
+.TP
+.B logdest:      Where to send messages. Choose between syslog, the
+console, and a log file. Defaults to sending messages to
+syslog, or the console if debugging or verbosity is
+enabled.
+
+
+.TP
+.B no\-client:    Do not create a config client. This will cause the daemon
+to run without ever checking for its configuration
+automatically, and only makes sense when used in
+conjunction with \-\-listen.
+
+
+.TP
+.B onetime:      Run the configuration once, rather than as a long\-running
+daemon. This is useful for interactively running puppetd.
+
+
+.TP
+.B serve:        Start another type of server. By default, +puppetd+ will
+start a service handler that allows authenticated and
+authorized remote nodes to trigger the configuration to be
+pulled down and applied. You can specify any handler here
+that does not require configuration, e.g., filebucket, ca,
+or resource. The handlers are in
++lib/puppet/network/handler+, and the names must match
+exactly, both in the call to +serve+ and in
++namespaceauth.conf+.
+
+
+.TP
+.B test:         Enable the most common options used for testing. These are
++onetime+, +verbose+, +ignorecache, and
++no\-usecacheonfailure+.
+
+verbose:      Turn on verbose reporting.
+
+version:      Print the puppet version number and exit.
+
+
+.TP
+.B waitforcert:  This option only matters for daemons that do not yet have
+certificates and it is enabled by default, with a value of
+120 (seconds). This causes +puppetd+ to connect to the
+server every 2 minutes and ask it to sign a certificate
+request. This is useful for the initial setup of a puppet
+client. You can turn off waiting for certificates by
+specifying a time of 0.
+
+
+.SH EXAMPLE
+
+.\" visit_block_quote
+puppetd \-\-server puppet.domain.com
+
+
+.\" depart_block_quote
+
+.SH AUTHOR
+Luke Kanies
+
+
+.SH COPYRIGHT
+Copyright (c) 2005, 2006 Reductive Labs, LLC Licensed under the GNU
+Public License
+
+
+.\" Generated by docutils manpage writer on 2008-03-22 17:46.
+.\" 
diff --git a/man/man8/puppetdoc.8 b/man/man8/puppetdoc.8
new file mode 100644
index 000000000..d7aacee75
--- /dev/null
+++ b/man/man8/puppetdoc.8
@@ -0,0 +1,62 @@
+.TH   "" "" ""
+.SH NAME
+ \- 
+
+.\" Man page generated from reStructeredText.
+
+.SH SYNOPSIS
+Generate a reference for all Puppet types. Largely meant for internal
+Reductive Labs use.
+
+
+.SH USAGE
+
+.\" visit_block_quote
+puppetdoc [\-a|\-\-all] [\-h|\-\-help] [\-m|\-\-mode <text|pdf|trac> [\-r|\-\-reference <[type]|configuration|..>]
+
+
+.\" depart_block_quote
+
+.SH DESCRIPTION
+This command generates a restructured\-text document describing all
+installed Puppet types or all allowable arguments to puppet executables.
+It is largely meant for internal use and is used to generate the
+reference document available on the Reductive Labs web site.
+
+
+.SH OPTIONS
+all:       Output the docs for all of the reference types.
+
+help:      Print this help message
+
+
+.TP
+.B mode:      Determine the output mode. Valid modes are \'text\', \'trac\',
+and \'pdf\'. Note that \'trac\' mode only works on Reductive Labs
+servers. The default mode is \'text\'.
+
+
+.TP
+.B reference: Build a particular reference. Get a list of references by
+running +puppetdoc \-\-list+.
+
+
+.SH EXAMPLE
+
+.\" visit_block_quote
+$ puppetdoc \-r type > /tmp/type_reference.rst
+
+
+.\" depart_block_quote
+
+.SH AUTHOR
+Luke Kanies
+
+
+.SH COPYRIGHT
+Copyright (c) 2005\-2007 Reductive Labs, LLC Licensed under the GNU
+Public License
+
+
+.\" Generated by docutils manpage writer on 2008-03-22 17:46.
+.\" 
diff --git a/man/man8/puppetmasterd.8 b/man/man8/puppetmasterd.8
new file mode 100644
index 000000000..5a8f02751
--- /dev/null
+++ b/man/man8/puppetmasterd.8
@@ -0,0 +1,87 @@
+.TH   "" "" ""
+.SH NAME
+ \- 
+
+.\" Man page generated from reStructeredText.
+
+.SH SYNOPSIS
+The central puppet server. Functions as a certificate authority by
+default.
+
+
+.SH USAGE
+
+.\" visit_block_quote
+
+.TP
+.B puppetmasterd [\-D|\-\-daemonize|\-\-no\-daemonize] [\-d|\-\-debug] [\-h|\-\-help]
+[\-l|\-\-logdest <file>|console|syslog] [\-\-nobucket] [\-\-nonodes]
+[\-v|\-\-verbose] [\-V|\-\-version]
+
+
+.\" depart_block_quote
+
+.SH DESCRIPTION
+This is the puppet central daemon.
+
+
+.SH OPTIONS
+Note that any configuration parameter that\'s valid in the configuration
+file is also a valid long argument. For example, \'ssldir\' is a valid
+configuration parameter, so you can specify \'\-\-ssldir <directory>\' as an
+argument.
+
+See the configuration file documentation at
+http://reductivelabs.com/projects/puppet/reference/configref.html for
+the full list of acceptable parameters. A commented list of all
+configuration options can also be generated by running puppetmasterdd
+with \'\-\-genconfig\'.
+
+daemonize:    Send the process into the background. This is the default.
+
+no\-daemonize: Do not send the process into the background.
+
+debug:        Enable full debugging.
+
+help:         Print this help message.
+
+
+.TP
+.B logdest:      Where to send messages. Choose between syslog, the
+console, and a log file. Defaults to sending messages to
+syslog, or the console if debugging or verbosity is
+enabled.
+
+nobucket:     Do not function as a file bucket.
+
+
+.TP
+.B nonodes:      Do not use individual node designations; each node will
+receive the result of evaluating the entire configuration.
+
+noreports:    Do not start the reports server.
+
+verbose:      Enable verbosity.
+
+version:      Print the puppet version number and exit.
+
+
+.SH EXAMPLE
+
+.\" visit_block_quote
+puppetmasterd
+
+
+.\" depart_block_quote
+
+.SH AUTHOR
+Luke Kanies
+
+
+.SH COPYRIGHT
+Copyright (c) 2005 Reductive Labs, LLC Licensed under the GNU Public
+License
+
+
+.\" Generated by docutils manpage writer on 2008-03-22 17:46.
+.\" 
diff --git a/man/man8/puppetrun.8 b/man/man8/puppetrun.8
new file mode 100644
index 000000000..753be1ca0
--- /dev/null
+++ b/man/man8/puppetrun.8
@@ -0,0 +1,151 @@
+.TH   "" "" ""
+.SH NAME
+ \- 
+
+.\" Man page generated from reStructeredText.
+
+.SH SYNOPSIS
+Trigger a puppetd run on a set of hosts.
+
+
+.SH USAGE
+
+.\" visit_block_quote
+
+.TP
+.B puppetrun [\-a|\-\-all] [\-c|\-\-class <class>] [\-d|\-\-debug] [\-f|\-\-foreground]
+[\-h|\-\-help] [\-\-host <host>] [\-\-no\-fqdn] [\-\-ignoreschedules]
+[\-t|\-\-tag <tag>] [\-\-test]
+
+
+.\" depart_block_quote
+
+.SH DESCRIPTION
+This script can be used to connect to a set of machines running
++puppetd+ and trigger them to run their configurations. The most common
+usage would be to specify a class of hosts and a set of tags, and
++puppetrun+ would look up in LDAP all of the hosts matching that class,
+then connect to each host and trigger a run of all of the objects with
+the specified tags.
+
+If you are not storing your host configurations in LDAP, you can specify
+hosts manually.
+
+You will most likely have to run +puppetrun+ as root to get access to
+the SSL certificates.
+
++puppetrun+ reads +puppetmaster+\'s configuration file, so that it can
+copy things like LDAP settings.
+
+
+.SH USAGE NOTES
++puppetrun+ is useless unless +puppetd+ is listening. See its
+documentation for more information, but the gist is that you must enable
++listen+ on the +puppetd+ daemon, either using +\-\-listen+ on the command
+line or adding \'listen: true\' in its config file. In addition, you need
+to set the daemons up to specifically allow connections by creating the
++namespaceauth+ file, normally at \'/etc/puppet/namespaceauth.conf\'. This
+file specifies who has access to each namespace; if you create the file
+you must add every namespace you want any Puppet daemon to allow \-\- it
+is currently global to all Puppet daemons.
+
+An example file looks like this:
+
+
+.nf
+[fileserver]
+    allow *.madstop.com
+
+[puppetmaster]
+    allow *.madstop.com
+
+[puppetrunner]
+    allow culain.madstop.com
+.fi
+This is what you would install on your Puppet master; non\-master hosts
+could leave off the \'fileserver\' and \'puppetmaster\' namespaces.
+
+Expect more documentation on this eventually.
+
+
+.SH OPTIONS
+Note that any configuration parameter that\'s valid in the configuration
+file is also a valid long argument. For example, \'ssldir\' is a valid
+configuration parameter, so you can specify \'\-\-ssldir <directory>\' as an
+argument.
+
+See the configuration file documentation at
+http://reductivelabs.com/projects/puppet/reference/configref.html for
+the full list of acceptable parameters. A commented list of all
+configuration options can also be generated by running puppetmasterdd
+with \'\-\-genconfig\'.
+
+
+.TP
+.B all:             Connect to all available hosts. Requires LDAP support
+at this point.
+
+
+.TP
+.B class:           Specify a class of machines to which to connect. This
+only works if you have LDAP configured, at the moment.
+
+debug:           Enable full debugging.
+
+
+.TP
+.B foreground:      Run each configuration in the foreground; that is, when
+connecting to a host, do not return until the host has
+finished its run. The default is false.
+
+help:            Print this help message
+
+
+.TP
+.B host:            A specific host to which to connect. This flag can be
+specified more than once.
+
+
+.TP
+.B ignoreschedules: Whether the client should ignore schedules when running
+its configuration. This can be used to force the client
+to perform work it would not normally perform so soon.
+The default is false.
+
+
+.TP
+.B parallel:        How parallel to make the connections. Parallelization
+is provided by forking for each client to which to
+connect. The default is 1, meaning serial execution.
+
+
+.TP
+.B tag:             Specify a tag for selecting the objects to apply. Does
+not work with the \-\-test option.
+
+
+.TP
+.B test:            Print the hosts you would connect to but do not
+actually connect. This option requires LDAP support at
+this point.
+
+
+.SH EXAMPLE
+
+.\" visit_block_quote
+sudo puppetrun \-p 10 \-\-host host1 \-\-host host2 \-t remotefile \-t webserver
+
+
+.\" depart_block_quote
+
+.SH AUTHOR
+Luke Kanies
+
+
+.SH COPYRIGHT
+Copyright (c) 2005 Reductive Labs, LLC Licensed under the GNU Public
+License
+
+
+.\" Generated by docutils manpage writer on 2008-03-22 17:46.
+.\" 
diff --git a/man/man8/ralsh.8 b/man/man8/ralsh.8
new file mode 100644
index 000000000..fc84fe0df
--- /dev/null
+++ b/man/man8/ralsh.8
@@ -0,0 +1,148 @@
+.TH   "" "" ""
+.SH NAME
+ \- 
+
+.\" Man page generated from reStructeredText.
+vim: softtabstop=4 shiftwidth=4 expandtab
+
+
+.SH SYNOPSIS
+Use the Puppet RAL to directly interact with the system.
+
+
+.SH USAGE
+
+.\" visit_block_quote
+
+.TP
+.B ralsh [\-h|\-\-help] [\-d|\-\-debug] [\-v|\-\-verbose] [\-e|\-\-edit] [\-H|\-\-host <host>]
+[\-p|\-\-param <param>] [\-t|\-\-types] type <name>
+
+
+.\" depart_block_quote
+
+.SH DESCRIPTION
+This command provides simple facilities for converting current system
+state into Puppet code, along with some ability to use Puppet to affect
+the current state.
+
+By default, you must at least provide a type to list, which case ralsh
+will tell you everything it knows about all instances of that type. You
+can optionally specify an instance name, and ralsh will only describe
+that single instance.
+
+You can also add +\-\-edit+ as an argument, and ralsh will write its
+output to a file, open that file in an editor, and then apply the file
+as a Puppet transaction. You can easily use this to use Puppet to make
+simple changes to a system.
+
+
+.SH OPTIONS
+Note that any configuration parameter that\'s valid in the configuration
+file is also a valid long argument. For example, \'ssldir\' is a valid
+configuration parameter, so you can specify \'\-\-ssldir <directory>\' as an
+argument.
+
+See the configuration file documentation at
+http://reductivelabs.com/projects/puppet/reference/configref.html for
+the full list of acceptable parameters. A commented list of all
+configuration options can also be generated by running puppet with
+\'\-\-genconfig\'.
+
+debug: Enable full debugging.
+
+edit:
+
+
+.\" visit_block_quote
+Write the results of the query to a file, open the file in an editor,
+and read the file back in as an executable Puppet manifest.
+
+
+.\" depart_block_quote
+host:
+
+
+.\" visit_block_quote
+When specified, connect to the resource server on the named host
+and retrieve the list of resouces of the type specified.
+
+
+.\" depart_block_quote
+help:
+
+
+.\" visit_block_quote
+Print this help message.
+
+
+.\" depart_block_quote
+param:
+
+
+.\" visit_block_quote
+Add more parameters to be outputted from queries.
+
+
+.\" depart_block_quote
+types:
+
+
+.\" visit_block_quote
+List all available types.
+
+
+.\" depart_block_quote
+verbose: Print extra information.
+
+
+.SH EXAMPLE
+This example uses 
+.\" visit_literal
+ralsh
+.\" depart_literal
+ to return Puppet configuration for the user
+
+.\" visit_literal
+luke
+.\" depart_literal
+:
+
+
+.nf
+$ ralsh user luke
+.fi
+
+.\" visit_block_quote
+
+.TP
+.B user { \'luke\':
+home => \'/home/luke\',
+uid => \'100\',
+ensure => \'present\',
+comment => \'Luke Kanies,,,\',
+gid => \'1000\',
+shell => \'/bin/bash\',
+groups => [\'sysadmin\',\'audio\',\'video\',\'puppet\']
+
+\.SH system-message
+System Message: WARNING/2 (./ralsh.rst:, line 87)
+Definition list ends without a blank line; unexpected unindent.
+
+
+}
+
+
+.\" depart_block_quote
+
+.SH AUTHOR
+Luke Kanies
+
+
+.SH COPYRIGHT
+Copyright (c) 2005\-2007 Reductive Labs, LLC Licensed under the GNU
+Public License
+
+
+.\" Generated by docutils manpage writer on 2008-03-22 17:46.
+.\"