chef 0.10.4 → 0.10.6.beta.1

data/distro/common/man/man1/shef.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "SHEF" "1" "August 2011" "Chef 0.10.4" "Chef Manual"
+.TH "SHEF" "1" "October 2011" "Chef 0.10.6.beta.1" "Chef Manual"
 .
 .SH "NAME"
 \fBshef\fR \- Interactive Chef Console

data/distro/common/man/man8/chef-client.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "CHEF\-CLIENT" "8" "August 2011" "Chef 0.10.4" "Chef Manual"
+.TH "CHEF\-CLIENT" "8" "October 2011" "Chef 0.10.6.beta.1" "Chef Manual"
 .
 .SH "NAME"
 \fBchef\-client\fR \- Runs a client node connecting to a chef\-server\.
@@ -34,6 +34,10 @@ Run chef\-client periodically, in seconds
 Load attributes from a JSON file or URL
 .
 .TP
+\fB\-E\fR, \fB\-\-environment ENVIRONMENT\fR
+Set the Chef Environment on the node
+.
+.TP
 \fB\-l\fR, \fB\-\-log_level LEVEL\fR
 Set the log level (debug, info, warn, error, fatal)
 .
@@ -50,6 +54,14 @@ Ensures logging goes to STDOUT as well as to other configured log location(s)\.
 The node name for this client
 .
 .TP
+\fB\-K\fR, \fB\-\-validation_key KEY_FILE\fR
+Set the validation key file location, used for registering new clients
+.
+.TP
+\fB\-k\fR, \fB\-\-client_key KEY_FILE\fR
+Set the client key file location
+.
+.TP
 \fB\-s\fR, \fB\-\-splay SECONDS\fR
 The splay time for running at intervals, in seconds
 .
@@ -58,6 +70,14 @@ The splay time for running at intervals, in seconds
 User to set privilege to
 .
 .TP
+\fB\-P\fR, \fB\-\-pid PIDFILE\fR
+Set the PID file location, defaults to /tmp/chef\-client\.pid
+.
+.TP
+\fB\-\-once\fR
+Cancel any interval or splay options, run chef once and exit
+.
+.TP
 \fB\-v\fR, \fB\-\-version\fR
 Show chef version
 .

data/distro/common/man/man8/chef-expander.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "CHEF\-EXPANDER" "8" "August 2011" "Chef 0.10.4" "Chef Manual"
+.TH "CHEF\-EXPANDER" "8" "October 2011" "Chef 0.10.6.beta.1" "Chef Manual"
 .
 .SH "NAME"
 \fBchef\-expander\fR \- fetches messages from RabbitMQ, processes, and loads into chef\-solr

data/distro/common/man/man8/chef-expanderctl.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "CHEF\-EXPANDERCTL" "8" "August 2011" "Chef 0.10.4" "Chef Manual"
+.TH "CHEF\-EXPANDERCTL" "8" "October 2011" "Chef 0.10.6.beta.1" "Chef Manual"
 .
 .SH "NAME"
 \fBchef\-expanderctl\fR \- management program for chef\-expander

data/distro/common/man/man8/chef-server-webui.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "CHEF\-SERVER\-WEBUI" "8" "August 2011" "Chef 0.10.4" "Chef Manual"
+.TH "CHEF\-SERVER\-WEBUI" "8" "October 2011" "Chef 0.10.6.beta.1" "Chef Manual"
 .
 .SH "NAME"
 \fBchef\-server\-webui\fR \- Start the Chef Server merb application slice providing Web User Interface (Management Console)\.

data/distro/common/man/man8/chef-server.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "CHEF\-SERVER" "8" "August 2011" "Chef 0.10.4" "Chef Manual"
+.TH "CHEF\-SERVER" "8" "October 2011" "Chef 0.10.6.beta.1" "Chef Manual"
 .
 .SH "NAME"
 \fBchef\-server\fR \- Start the Chef Server merb application slice\.

data/distro/common/man/man8/chef-solo.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "CHEF\-SOLO" "8" "August 2011" "Chef 0.10.4" "Chef Manual"
+.TH "CHEF\-SOLO" "8" "October 2011" "Chef 0.10.6.beta.1" "Chef Manual"
 .
 .SH "NAME"
 \fBchef\-solo\fR \- Runs chef in solo mode against a specified cookbook location\.

data/distro/common/man/man8/chef-solr.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "CHEF\-SOLR" "8" "August 2011" "Chef 0.10.4" "Chef Manual"
+.TH "CHEF\-SOLR" "8" "October 2011" "Chef 0.10.6.beta.1" "Chef Manual"
 .
 .SH "NAME"
 \fBchef\-solr\fR \- Runs as Chef\'s search server
@@ -30,6 +30,10 @@ Set the log level (debug, info, warn, error, fatal)
 Set the log file location, defaults to STDOUT \- recommended for daemonizing
 .
 .TP
+\fB\-P\fR, \fB\-\-pid PIDFILE\fR
+Set the PID file location, defaults to /tmp/chef\-solr\.pid
+.
+.TP
 \fB\-D\fR, \fB\-\-solr\-data\-dir PATH\fR
 Where the Solr data lives
 .
@@ -46,6 +50,10 @@ Solr home directory
 Raw options passed to Java
 .
 .TP
+\fB\-x\fR, \fB\-\-solor\-heap\-size\fR
+Set the size of the Java Heap
+.
+.TP
 \fB\-W\fR, \fB\-\-solr\-jetty\-dir PATH\fR
 Where to place the Solr Jetty instance
 .

data/distro/common/markdown/man1/knife-bootstrap.mkd

@@ -1,4 +1,4 @@
-knife-bootrap(1) -- Install Chef Client on a remote host
+knife-bootstrap(1) -- Install Chef Client on a remote host
 ========================================
 
 ## SYNOPSIS
@@ -13,20 +13,24 @@ __knife__ __bootstrap__ _(options)_
     The ssh password
   * `-x`, `--ssh-user USERNAME`:
     The ssh username
+  * `-p`, `--ssh-port PORT`:
+    The ssh port
+  * `--bootstrap-version VERSION`:
+    The version of Chef to install
+  * `--bootstrap-proxy PROXY_URL`:
+    `The proxy server for the node being bootstrapped`
   * `--prerelease`:
     Install pre-release Chef gems
   * `-r`, `--run-list RUN_LIST`:
     Comma separated list of roles/recipes to apply
-  * `-P`, `--ssh-password PASSWORD`:
-    The ssh password
-  * `-x`, `--ssh-user USERNAME`:
-    The ssh username
   * `--template-file TEMPLATE`:
     Full path to location of template to use
   * `--sudo`:
     Execute the bootstrap via sudo
   * `-d`, `--distro DISTRO`:
     Bootstrap a distro using a template
+  * `--no-host-key-verify`:
+    Disable host key verification
 
 ## DESCRIPTION
 

data/distro/common/markdown/man1/knife-cookbook-site.mkd

@@ -13,6 +13,10 @@ __cookbook site install COOKBOOK [VERSION]__ _(options)_
 
   * `-D`, `--no-dependencies `:
     Do not install dependencies automatically
+  * `-o`, `--cookbook-path PATH`:
+    Install cookbooks to PATH
+  * `-B`, `--branch BRANCH`:
+    Default branch to work with [defaults to master]
 
 Uses git(1) version control in conjunction with the cookbook site to
 install community contributed cookbooks to your local cookbook
@@ -26,7 +30,7 @@ repository. Running `knife cookbook site install` does the following:
 5. The pristine copy branch is merged into the master branch.
 
 By installing cookbook with this process, you can locally modify the
-upstream cookbook in your master branch ant let git maintain your
+upstream cookbook in your master branch and let git maintain your
 changes as a separate patch.  When an updated upstream version becomes
 available, you will be able to merge the upstream changes while
 maintaining your local modifications.

data/distro/common/markdown/man1/knife-cookbook.mkd

@@ -27,6 +27,8 @@ __knife cookbook show cookbook [version] [part] [filename]__ _(options)_
     the platform to see the file for
   * `-v`, `--platform-version version`:
     the platform version to see the file for
+  * `-w`, `--with-uri`:
+    Show corresponding URIs
 
 show a particular part of a _cookbook_ for the specified _version_. _part_ can be one of:
 
@@ -114,7 +116,7 @@ __knife cookbook create cookbook__ _(options)_
   * `-o`, `--cookbook-path path`:
     the directory where the cookbook will be created
   * `-r`, `--readme-format format`:
-    format of the readme file
+    format of the readme file md, mkd, txt, rdoc
   * `-c`, `--copyright copyright`:
     name of copyright holder
   * `-i`, `--license license`:
@@ -132,12 +134,12 @@ named cookbook.
 * cookbook/libraries
 * cookbook/metadata.rb
 * cookbook/providers
-* cookbook/readme.rdoc
+* cookbook/readme.md
 * cookbook/recipes/default.rb
 * cookbook/resources
 * cookbook/templates/default
 
-supported readme formats are 'rdoc' (default), 'md', 'mkd', 'txt'. the
+supported readme formats are 'md' (default), 'mkd', 'txt', 'rdoc'. the
 readme file will be written with the specified extension and a set of
 helpful starting headers.
 
@@ -158,12 +160,13 @@ specify `-e` or `--email` with the email address of the cookbook's
 maintainer. if this value is not specified, an all-caps string
 `your_email` is used which can easily be changed with find/replace.
 
-the cookbook copyright, license and email settings can be filled in the
+the cookbook copyright, license, email and readme_format settings can be filled in the
 `knife.rb`, for example with default values:
 
     cookbook_copyright "your_company_name"
     cookbook_license "none"
     cookbook_email "your_email"
+    readme_format "md"
 
 
 ## METADATA

data/distro/common/markdown/man1/knife-node.mkd

@@ -100,25 +100,7 @@ __knife node show__ _node name_ _(options)_
     Display more, but not all, of the node's data when using the default
     _summary_ format
 
-Displays the node identified by _node name_ on stdout. The amount of
-content displayed and the output format are modified by the --format
-option. If no alternate format is selected, the default is summary. 
-Valid formats are:
-
-  * summary:
-    displays the node in a custom, summarized format (default)
-  * text
-    displays the node data in its entirety using the colorized tree
-display 
-  * json:
-    displays the node in JSON format
-  * yaml:
-    displays the node in YAML format
-  * pp
-    displays the node using Ruby's pretty printer.
-
-For brevity, only the first character of the format is required, for
-example, -Fj will produce JSON format output.
+Displays the node identified by _node name_ on stdout. 
 
 ## RUN LIST ITEM FORMAT
 Run list items may be either roles or recipes. When adding a role to a

data/distro/common/markdown/man1/knife-search.mkd

@@ -44,6 +44,7 @@ query syntax. The following data types are indexed for search:
   * _node_
   * _role_
   * _environment_
+  * _clients_
   * _data bag_
 
 Data bags are indexed by the data bag's name. For example, to search a
@@ -108,7 +109,7 @@ Fuzzy searches allows one to match values based on the Levenshtein
 Distance algorithm.  To perform a fuzzy match, append a tilda (~) to
 the search term:
 
-    knife search nodes 'field:term~'
+    knife search INDEX 'field:term~'
 
 This search would return nodes whose `field` was 'perm' or 'germ'.
 
@@ -146,15 +147,15 @@ The following characters must be escaped:
 Find the nodes with the fully-qualified domain name (FQDN)
 www.example.com:
 
-    knife search nodes 'fqdn:www.example.com'
+    knife search node 'fqdn:www.example.com'
 
 Find the nodes running a version of Ubuntu:
 
-    knife search nodes 'platform:ubuntu*'
+    knife search node 'platform:ubuntu*'
 
 Find all nodes running CentOS in the production environment:
 
-    knife search nodes 'chef_environment:production AND platform:centos'
+    knife search node 'chef_environment:production AND platform:centos'
 
 ## KNOWN BUGS
 

data/distro/common/markdown/man1/knife-ssh.mkd

@@ -17,6 +17,13 @@ __knife__ __ssh QUERY COMMAND__ _(options)_
     The ssh username
   * `-i`, `--identity-file IDENTITY_FILE`:
     The SSH identity file used for authentication
+  * `-p`, `--ssh-port PORT`:
+    The ssh port
+  * `-i`, `--identity-file IDENTITY_FILE`:
+    The SSH identity file used for authentication
+  * `--no-host-key-verify`:
+    Disable host key verification
+    
 
 ## DESCRIPTION
 
@@ -35,6 +42,7 @@ multiple interactive ssh sessions running locally in the terminal
 multiplexer instead of invoking the command on the remote host.
 
 The available multiplexers are:
+
   * `interactive`:
     A built-in multiplexer. `interactive` supports running commands on a
     subset of the connected hosts in parallel

data/distro/common/markdown/man1/knife.mkd

@@ -40,14 +40,14 @@ documentation using `knife help TOPIC`.
     API Client Key, corresponds to `Chef::Config` `client_key`.
   * `-c`, `--config` CONFIG:
     The configuration file to use
+  * `-E`, `--environment ENVIRONMENT`:
+    Set the Chef environment
   * `-e`, `--editor` EDITOR:
     Set the editor to use for interactive commands
   * `-F`, `--format` FORMAT:
-    Which format to use for output
-  * `-l`, `--log_level` LEVEL:
-    Set the log level (debug, info, warn, error, fatal), corresponds to `Chef::Config` `log_level`.
-  * `-L`, `--logfile` LOGLOCATION:
-    Set the log file location, defaults to STDOUT, corresponds to `Chef::Config` `log_location`.
+    Which format to use for output. See FORMATS for details.
+  * `-V`, `--verbose`:
+    More verbose output.  Use twice for max verbosity
   * `-n`, `--no-editor`:
     Do not open EDITOR, just accept the data as is
   * `-u`, `--user` USER:
@@ -58,6 +58,12 @@ documentation using `knife help TOPIC`.
     Show chef version
   * `-y`, `--yes`:
     Say yes to all prompts for confirmation
+  * `--defaults`:
+    Accept default values for all questions
+  * `--color`:
+    Use colored output
+  * `--no-color`:
+    Don't use colors in the output
   * `-h`, `--help`:
     Show the available options for a command.
 
@@ -108,9 +114,9 @@ If the config file exists, knife uses these settings for __GENERAL OPTIONS__ def
     Specifies the private key file to use when bootstrapping new hosts.
     See knife-client(1) for more information about the validation
     client.
-  * `cookbook_copyright`, `cookbook_email`, `cookbook_license`
+  * `cookbook_copyright`, `cookbook_email`, `cookbook_license`, `readme_format`
     Used by `knife cookbook create` sub-command to specify the copyright
-    holder, maintainer email and license (respectively) for new cookbooks.
+    holder, maintainer email, license and readme format (respectively) for new cookbooks.
     The copyright holder is listed as the maintainer in the cookbook's
     metadata and as the Copyright in the comments of the default recipe. The
     maintainer email is used in the cookbook metadata. The license
@@ -118,7 +124,9 @@ If the config file exists, knife uses these settings for __GENERAL OPTIONS__ def
     and is listed as the license in the cookbook metadata. Currently
     supported licenses are "apachev2" and "none". Any other values will
     result in an empty license in the metadata (needs to be filled in by the
-    author), and no comment preamble in the default recipe.
+    author), and no comment preamble in the default recipe. Currently supported 
+    readme formats are "md", "mkd", "txt", and "rdoc".  Any other value will
+    result in an unformatted README.
 
 ## FILES
 
@@ -126,6 +134,28 @@ _~/.chef/knife.rb_
 
 Ruby DSL configuration file for knife. See __CONFIGURATION__.
 
+## FORMATS 
+
+The amount of content displayed and the output format are
+modified by the `--format` option. If no alternate format is selected,
+the default is summary.
+
+Valid formats are:
+
+  * `summary`:
+    displays the node in a custom, summarized format (default)
+  * `text`:
+    displays the node data in its entirety using the colorized tree display 
+  * `json`:
+    displays the node in JSON format
+  * `yaml`:
+    displays the node in YAML format
+  * `pp`:
+    displays the node using Ruby's pretty printer.
+
+For brevity, only the first character of the format is required, for
+example, -Fj will produce JSON format output.
+
 ## CHEF WORKFLOW
 
 When working with Chef and Knife in the local repository, the recommended workflow outline looks like:
@@ -144,6 +174,7 @@ but it is not required, except in the case of the `cookbook site vendor`
 sub-command, as it uses git directly. Version control is strongly
 recommended though, and git fits with a lot of the workflow paradigms.
 
+
 ## EXAMPLES
 
 

data/distro/common/markdown/man8/chef-client.mkd

@@ -17,6 +17,8 @@ __chef-client__ _(options)_
     Run chef-client periodically, in seconds
   * `-j`, `--json-attributes JSON_ATTRIBS`:
     Load attributes from a JSON file or URL
+  * `-E`, `--environment ENVIRONMENT`:
+    Set the Chef Environment on the node
   * `-l`, `--log_level LEVEL`:
     Set the log level (debug, info, warn, error, fatal)
   * `-L`, `--logfile LOGLOCATION`:
@@ -27,10 +29,18 @@ __chef-client__ _(options)_
     log location(s).
   * `-N`, `--node-name NODE_NAME`:
     The node name for this client
+  * `-K`, `--validation_key KEY_FILE`:
+    Set the validation key file location, used for registering new clients
+  * `-k`, `--client_key KEY_FILE`:
+    Set the client key file location
   * `-s`, `--splay SECONDS`:
     The splay time for running at intervals, in seconds
   * `-u`, `--user USER`:
     User to set privilege to
+  * `-P`, `--pid PIDFILE`:
+    Set the PID file location, defaults to /tmp/chef-client.pid
+  * `--once`:
+    Cancel any interval or splay options, run chef once and exit
   * `-v`, `--version`:
     Show chef version
   * `-h`, `--help`:

data/distro/common/markdown/man8/chef-solr.mkd

@@ -15,6 +15,8 @@ __chef-solr__ _(options)_
     Set the log level (debug, info, warn, error, fatal)
   * `-L`, `--logfile LOGLOCATION`:
     Set the log file location, defaults to STDOUT - recommended for daemonizing
+  * `-P`, `--pid PIDFILE`:
+    Set the PID file location, defaults to /tmp/chef-solr.pid
   * `-D`, `--solr-data-dir PATH`:
     Where the Solr data lives
   * `-x`, `--solor-heap-size SIZE`:
@@ -23,6 +25,8 @@ __chef-solr__ _(options)_
     Solr home directory
   * `-j`, `--java-opts OPTS`:
     Raw options passed to Java
+  * `-x`, `--solor-heap-size`:
+    Set the size of the Java Heap
   * `-W`, `--solr-jetty-dir PATH`:
     Where to place the Solr Jetty instance
   * `-u`, `--user USER`:
@@ -82,4 +86,4 @@ help2man.  Permission  is  granted  to copy, distribute and / or modify
 this document under the terms of the Apache 2.0 License.
 
 On Debian systems, the complete text of the Apache 2.0 License  can  be
-found in /usr/share/common-licenses/Apache-2.0.
+found in /usr/share/common-licenses/Apache-2.0.