runa-chef 0.8.0.1

data/distro/README

@@ -0,0 +1,2 @@
+Init scripts meant to be used with a gem installation via the bootstrap
+cookbook.

data/distro/common/man/man1/chef-indexer.1

@@ -0,0 +1,42 @@
+.\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.36.
+.TH CHEF-INDEXER: "1" "August 2009" "chef-indexer 0.7.8" "User Commands"
+.SH NAME
+chef-indexer: \- Runs the search index process.
+.SH SYNOPSIS
+.B chef-indexer
+\fI(options)\fR
+.SH DESCRIPTION
+.TP
+chef-indexer requires that the stompserver be started but at this time the stompserver package does not install a startup script, let alone start the daemon. I am working with the package maintainer for stompserver to include a startup script.
+\fB\-c\fR, \fB\-\-config\fR CONFIG
+The configuration file to use
+.TP
+\fB\-d\fR, \fB\-\-daemonize\fR
+Daemonize the process
+.TP
+\fB\-g\fR, \fB\-\-group\fR GROUP
+Group to change gid to before daemonizing
+.TP
+\fB\-l\fR, \fB\-\-log_level\fR LEVEL
+Set the log level (debug, info, warn, error, fatal)
+.TP
+\fB\-L\fR, \fB\-\-logfile\fR LOGLOCATION
+Set the log file location, defaults to STDOUT \- recommended for daemonizing
+.TP
+\fB\-u\fR, \fB\-\-user\fR USER
+User to change uid to before daemonizing
+.TP
+\fB\-v\fR, \fB\-\-version\fR
+Show chef version
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Show this message
+.SH "SEE ALSO"
+Full documentation for Chef and chef-indexer is located on the Chef wiki, http://wiki.opscode.com/display/chef/Home.
+.SH AUTHOR
+Chef was written by Adam Jacob <adam@ospcode.com> of Opscode (http://www.opscode.com), with contributions from the community.
+This manual page was written by Joshua Timberman <joshua@opscode.com> with 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.

data/distro/common/man/man1/chef-server.1

@@ -0,0 +1,108 @@
+.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
+.TH CHEF-SERVER "1" "August 2009" "chef-server" "User Commands"
+.SH NAME
+chef-server \- Start the Chef Server merb application slice.
+.SH SYNOPSIS
+.B chef-server
+[\fIuGdcIpPhmailLerkKX\fR] [\fIargument\fR]
+.SH DESCRIPTION
+The Chef Server is a Merb application slice. Both chef-server and chef-server-slice packages should be installed. This man page was generated for merb and generated for chef-server.
+The default listen port is 4000. At a minimum, chef-server should be started with \-c2 so one process starts for the webui (4000) and one process starts for openid (4001).
+.TP
+\fB\-u\fR, \fB\-\-user\fR USER
+This flag is for having chef-server run as a user other than the one currently logged in. Note: if you set this you must also provide a \fB\-\-group\fR option for it to take effect.
+.TP
+\fB\-G\fR, \fB\-\-group\fR GROUP
+This flag is for having chef-server run as a group other than the one currently logged in. Note: if you set this you must also provide a \fB\-\-user\fR option for it to take effect.
+.TP
+\fB\-d\fR, \fB\-\-daemonize\fR
+This will run a single chef-server in the background.
+.TP
+\fB\-N\fR, \fB\-\-no\-daemonize\fR
+This will allow you to run a cluster in console mode
+.TP
+\fB\-c\fR, \fB\-\-cluster\-nodes\fR NUM_MERBS
+Number of merb daemons to run for chef-server. At least 2 are required to run, the second is for openid (runs on port 4001).
+.TP
+\fB\-I\fR, \fB\-\-init\-file\fR FILE
+File to use for initialization on load, defaults to config/init.rb
+.TP
+\fB\-p\fR, \fB\-\-port\fR PORTNUM
+Port to run chef-server on, defaults to 4000. Additional nodes (\-c) listen on incrementing port numbers.
+.TP
+\fB\-o\fR, \fB\-\-socket\-file\fR FILE
+Socket file to run chef-server on, defaults to [Merb.root]/log/merb.sock. This is for web servers, like thin, that use sockets.Specify this *only* if you *must*.
+.TP
+\fB\-s\fR, \fB\-\-socket\fR SOCKNUM
+Socket number to run chef-server on, defaults to 0.
+.TP
+\fB\-n\fR, \fB\-\-name\fR NAME
+Set the name of the application. This is used in the process title and log file names.
+.TP
+\fB\-P\fR, \fB\-\-pid\fR PIDFILE
+PID file, defaults to [Merb.root]/log/merb.main.pid for the master process and[Merb.root]/log/merb.[port number].pid for worker processes. For clusters, use %s to specify where in the file chef-server should place the port number. For instance: \fB\-P\fR myapp.%s.pid
+.TP
+\fB\-h\fR, \fB\-\-host\fR HOSTNAME
+Host to bind to (default is 0.0.0.0).
+.HP
+\fB\-m\fR, \fB\-\-merb\-root\fR /path/to/approot The path to the Merb.root for the app you want to run (default is current working directory).
+.TP
+\fB\-a\fR, \fB\-\-adapter\fR ADAPTER
+The rack adapter to use to run chef-server (default is mongrel)[mongrel, emongrel, thin, ebb, fastcgi, webrick]
+.TP
+\fB\-R\fR, \fB\-\-rackup\fR FILE
+Load an alternate Rack config file (default is config/rack.rb)
+.TP
+\fB\-i\fR, \fB\-\-irb\-console\fR
+This flag will start chef-server in irb console mode. All your models and other classes will be available for you in an irb session.
+.TP
+\fB\-S\fR, \fB\-\-sandbox\fR
+This flag will enable a sandboxed irb console. If your ORM supports transactions, all edits will be rolled back on exit.
+.TP
+\fB\-l\fR, \fB\-\-log\-level\fR LEVEL
+Log levels can be set to any of these options: debug < info < warn < error < fatal (default is info)
+.TP
+\fB\-L\fR, \fB\-\-log\fR LOGFILE
+A string representing the logfile to use. Defaults to [Merb.root]/log/merb.[main].log for the master process and [Merb.root]/log/merb[port number].logfor worker processes
+.TP
+\fB\-e\fR, \fB\-\-environment\fR STRING
+Environment to run Merb under [development, production, testing] (default is development)
+.HP
+\fB\-r\fR ['RUBY CODE'| FULL_SCRIPT_PATH]
+.TP
+\fB\-\-script\-runner\fR
+Command\-line option to run scripts and/or code in the chef-server app.
+.TP
+\fB\-K\fR, \fB\-\-graceful\fR PORT or all
+Gracefully kill chef-server proceses by port number.  Use chef-server \fB\-K\fR all to gracefully kill all merbs.
+.TP
+\fB\-k\fR, \fB\-\-kill\fR PORT
+Force kill one merb worker by port number. This will cause the worker tobe respawned.
+.TP
+\fB\-\-fast\-deploy\fR
+Reload the code, but not yourinit.rb or gems
+.TP
+\fB\-X\fR, \fB\-\-mutex\fR on/off
+This flag is for turning the mutex lock on and off.
+.TP
+\fB\-D\fR, \fB\-\-debugger\fR
+Run chef-server using rDebug.
+.TP
+\fB\-V\fR, \fB\-\-verbose\fR
+Print extra information
+.TP
+\fB\-C\fR, \fB\-\-console\-trap\fR
+Enter an irb console on ^C
+.TP
+\-?, \fB\-H\fR, \fB\-\-help\fR
+Show this help message
+.SH "SEE ALSO"
+Full documentation for Chef and chef-server is located on the Chef wiki, http://wiki.opscode.com/display/chef/Home.
+.SH AUTHOR
+Chef was written by Adam Jacob <adam@ospcode.com> of Opscode (http://www.opscode.com), with contributions from the community.
+This manual page was written by Joshua Timberman <joshua@opscode.com> with help2man
+for the Debian project (but may be used by others).. 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.

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

@@ -0,0 +1,61 @@
+.\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.36.
+.TH CHEF-CLIENT: "8" "August 2009" "chef-client 0.7.8" "System Administration Utilities"
+.SH NAME
+chef-client: \- Runs a client node connecting to a chef-server.
+.SH SYNOPSIS
+.B chef-client
+\fI(options)\fR
+.SH DESCRIPTION
+.TP
+\fB\-S\fR, \fB\-\-server\fR CHEFSERVERURL
+The chef server URL
+.TP
+\fB\-c\fR, \fB\-\-config\fR CONFIG
+The configuration file to use
+.TP
+\fB\-d\fR, \fB\-\-daemonize\fR
+Daemonize the process
+.TP
+\fB\-g\fR, \fB\-\-group\fR GROUP
+Group to set privilege to
+.TP
+\fB\-i\fR, \fB\-\-interval\fR SECONDS
+Run chef\-client periodically, in seconds
+.TP
+\fB\-j\fR JSON_ATTRIBS
+Load attributes from a JSON file or URL
+.HP
+\fB\-\-json\-attributes\fR
+.TP
+\fB\-l\fR, \fB\-\-log_level\fR LEVEL
+Set the log level (debug, info, warn, error, fatal)
+.TP
+\fB\-L\fR, \fB\-\-logfile\fR LOGLOCATION
+Set the log file location, defaults to STDOUT \- recommended for daemonizing
+.TP
+\fB\-N\fR, \fB\-\-node\-name\fR NODE_NAME
+The node name for this client
+.TP
+\fB\-s\fR, \fB\-\-splay\fR SECONDS
+The splay time for running at intervals, in seconds
+.TP
+\fB\-u\fR, \fB\-\-user\fR USER
+User to set privilege to
+.TP
+\fB\-t\fR, \fB\-\-token\fR TOKEN
+Set the openid validation token
+.TP
+\fB\-v\fR, \fB\-\-version\fR
+Show chef version
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Show this message
+.SH "SEE ALSO"
+Full documentation for Chef and chef-client is located on the Chef wiki, http://wiki.opscode.com/display/chef/Home.
+.SH AUTHOR
+Chef was written by Adam Jacob <adam@ospcode.com> of Opscode (http://www.opscode.com), with contributions from the community.
+This manual page was written by Joshua Timberman <joshua@opscode.com> with 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.

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

@@ -0,0 +1,58 @@
+.\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.36.
+.TH CHEF-SOLO: "8" "August 2009" "chef-solo 0.7.8" "System Administration Utilities"
+.SH NAME
+chef-solo: \- Runs chef in solo mode against a specified cookbook location.
+.SH SYNOPSIS
+.B chef-solo
+\fI(options)\fR
+.SH DESCRIPTION
+.TP
+\fB\-c\fR, \fB\-\-config\fR CONFIG
+The configuration file to use
+.TP
+\fB\-d\fR, \fB\-\-daemonize\fR
+Daemonize the process
+.TP
+\fB\-g\fR, \fB\-\-group\fR GROUP
+Group to set privilege to
+.TP
+\fB\-i\fR, \fB\-\-interval\fR SECONDS
+Run chef\-client periodically, in seconds
+.TP
+\fB\-j\fR JSON_ATTRIBS
+Load attributes from a JSON file or URL
+.HP
+\fB\-\-json\-attributes\fR
+.TP
+\fB\-l\fR, \fB\-\-log_level\fR LEVEL
+Set the log level (debug, info, warn, error, fatal)
+.TP
+\fB\-L\fR, \fB\-\-logfile\fR LOGLOCATION
+Set the log file location, defaults to STDOUT
+.TP
+\fB\-N\fR, \fB\-\-node\-name\fR NODE_NAME
+The node name for this client
+.TP
+\fB\-r\fR, \fB\-\-recipe\-url\fR RECIPE_URL
+Pull down a remote gzipped tarball of recipes and untar it to the cookbook cache.
+.TP
+\fB\-s\fR, \fB\-\-splay\fR SECONDS
+The splay time for running at intervals, in seconds
+.TP
+\fB\-u\fR, \fB\-\-user\fR USER
+User to set privilege to
+.TP
+\fB\-v\fR, \fB\-\-version\fR
+Show chef version
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Show this message
+.SH "SEE ALSO"
+Full documentation for Chef and chef-solo is located on the Chef wiki, http://wiki.opscode.com/display/chef/Home.
+.SH AUTHOR
+Chef was written by Adam Jacob <adam@ospcode.com> of Opscode (http://www.opscode.com), with contributions from the community.
+This manual page was written by Joshua Timberman <joshua@opscode.com> with 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.

data/distro/common/man/man8/knife.8

@@ -0,0 +1,359 @@
+.TH CHEF: "1" "December 2009" "knife: 0.8.0" "System Administration Utilities"
+.SH NAME
+knife: \- Chef server REST API utility
+.SH SYNOPSIS
+.B knife
+\fIsub-command (options)\fR
+.SH DESCRIPTION
+.TP
+This manual page documents knife, a command-line utility used to interact with a Chef server directly through the RESTful API. Knife uses sub-commands to take various actions on different types of Chef objects. Some sub-commands take additional options. General options follow sub-commands and their options. A configuration file can be created for common defaults.
+.TP
+Unless otherwise specified, output is in JSON format, and input files are also JSON format.
+.SH GENERAL OPTIONS
+.TP
+\fB\-s\fR, \fB\-\-server\-url\fR URL
+Chef Server URL
+.TP
+\fB\-k\fR, \fB\-\-key\fR KEY
+API Client Key
+.TP
+\fB\-c\fR, \fB\-\-config\fR CONFIG
+The configuration file to use
+.TP
+\fB\-e\fR, \fB\-\-editor\fR EDITOR
+Set the editor to use for interactive commands
+.TP
+\fB\-l\fR, \fB\-\-log_level\fR LEVEL
+Set the log level (debug, info, warn, error, fatal)
+.TP
+\fB\-L\fR, \fB\-\-logfile\fR LOGLOCATION
+Set the log file location, defaults to STDOUT
+.TP
+\fB\-u\fR, \fB\-\-user\fR USER
+API Client Username
+.TP
+\fB\-p\fR, \fB\-\-print\-after\fR
+Show the data after a destructive operation
+.TP
+\fB\-v\fR, \fB\-\-version\fR
+Show chef version
+.TP
+\fB\-y\fR, \fB\-\-yes\fR
+Say yes to all prompts for confirmation
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Show usage information.
+.SH SUB-COMMANDS
+Knife sub-commands are structured as "NOUN verb NOUN (options)". The sub-commands are meant to be intuitively named.
+.SH CLIENT SUB-COMMANDS
+.TP
+Sub-commands related to working with clients, which are registered entities that access the Chef server.
+.TP
+.B client bulk delete \fI(options)\fR
+.TP
+\fB\-r\fR, \fB\-\-regex\fR [REGEX]
+Narrow the operation via regular expression
+.PP
+Delete all the clients on the Chef server, or only certain clients based on a regular expression.
+.PP
+.B client create CLIENT (options)
+.TP
+\fB\-f\fR, \fB\-\-file\fR FILE
+Write the key to a file
+.PP
+Create a new client.
+.PP
+.B client delete CLIENT (options)
+.PP
+Deletes a registered client.
+.PP
+.B client edit CLIENT (options)
+.PP
+Edit a registered client.
+.PP
+.B client list (options)
+.TP
+\fB\-w\fR, \fB\-\-with\-uri\fR
+Show corresponding URIs
+.PP
+List all registered clients.
+.PP
+.B client reregister CLIENT (options)
+.TP
+\fB\-f\fR, \fB\-\-file\fR FILE
+Write the key to a file
+.PP
+Regenerate the private key for a client.
+.PP
+.B client show CLIENT (options)
+.TP
+\fB\-a\fR, \fB\-\-attribute\fR [ATTR]
+Show only one attribute
+.PP
+Show a client.
+.SH COOKBOOK SUB-COMMANDS
+.TP
+Cookbooks are the fundamental unit of distribution in Chef. They encapsulate all the recipes of resources and the assets used to configure a particular aspect of the infrastructure.
+.PP
+.B cookbook bulk delete COOKBOOK (options)
+.TP
+\fB\-r\fR, \fB\-\-regex\fR [REGEX]
+Narrow the operation via regular expression
+.PP
+Delete all the cookbooks on the Chef server, or use a regular expression to only delete certain cookbooks.
+.PP
+.B cookbook delete COOKBOOK (options)
+.PP
+Delete a single named COOKBOOK.
+.PP
+.B cookbook download COOKBOOK (options)
+.TP
+\fB\-f\fR, \fB\-\-file\fR FILE
+The filename to write to
+.PP
+Download a cookbook from the server as a gzip(1)'ed, tar(1) archive.
+.PP
+.B cookbook list (options)
+.TP
+\fB\-w\fR, \fB\-\-with\-uri\fR
+Show corresponding URIs
+.PP
+List all cookbooks.
+.PP
+.B cookbook metadata COOKBOOK (options)
+.TP
+\fB\-a\fR, \fB\-\-all\fR
+Generate metadata for all cookbooks, rather than just a single cookbook
+.PP
+Generate cookbook metadata for the named COOKBOOK.
+.TP
+\fB\-o\fR, \fB\-\-cookbook\-path\fR PATH:PATH
+A colon\-separated path to look for cookbooks in
+.PP
+.B cookbook show COOKBOOK [PART] [FILENAME] (options)
+.TP
+\fB\-f\fR, \fB\-\-fqdn\fR FQDN
+The FQDN of the host to see the file for
+.TP
+\fB\-p\fR, \fB\-\-platform\fR PLATFORM
+The platform to see the file for
+.TP
+\fB\-V\fR, \fB\-\-platform\-version\fR VERSION
+The platform version to see the file for
+.PP
+Show the particular part of a COOKBOOK. PART can be one of:
+.TP
+\fIattribute definition file provider recipe resource template\fR
+.PP
+.B cookbook upload COOKBOOK (options)
+.TP
+\fB\-a\fR, \fB\-\-all\fR
+Upload all cookbooks, rather than just a single cookbook
+.TP
+\fB\-o\fR, \fB\-\-cookbook\-path\fR PATH:PATH
+A colon\-separated path to look for cookbooks in
+.PP
+Upload a cookbook to the server.
+.SH DATA BAG SUB-COMMANDS
+.PP
+Data bags are stores of JSON blobs. These blobs are called items. They are free form and indexed by the search mechanism on the Chef server.
+.PP
+.B data bag create BAG [ITEM] (options)
+.PP
+Create a new data bag, or item in a data bag.
+.PP
+.B data bag delete BAG [ITEM] (options)
+.PP
+Delete a data bag, or item from a data bag.
+.PP
+.B data bag edit BAG ITEM (options)
+.PP
+Edit an item in a data bag.
+.PP
+.B data bag list (options)
+.TP
+\fB\-w\fR, \fB\-\-with\-uri\fR
+Show corresponding URIs
+.PP
+List the available data bags.
+.PP
+.B data bag show BAG [ITEM] (options)
+.PP
+Show a specific data bag or an item in a data bag.
+.SH NODE SUB-COMMANDS
+.PP
+Nodes are the entities which are configured with Chef, typically servers or workstations. Nodes are registered as a client, typcially of the same name, but a single client might represent one or more nodes.
+.PP
+.B node bulk delete (options)
+.TP
+\fB\-r\fR, \fB\-\-regex\fR [REGEX]
+Narrow the operation via regular expression
+.PP
+Delete all nodes, or only certain nodes based on a regular expression.
+.PP
+.B node create NODE (options)
+.PP
+Create a new node.
+.PP
+.B node delete NODE (options)
+.PP
+Delete a single node.
+.PP
+.B node edit NODE (options)
+.PP
+Edit a node.
+.PP
+.B node from file FILE (options)
+.PP
+Create a node from a JSON file.
+.PP
+.B node list (options)
+.TP
+\fB\-w\fR, \fB\-\-with\-uri\fR
+Show corresponding URIs
+.PP
+List all nodes.
+.PP
+.B node run_list add [NODE] [ENTRY] (options)
+.TP
+\fB\-a\fR, \fB\-\-after\fR [ITEM]
+Place the ENTRY in the run list after ITEM
+.PP
+Add a recipe or role to the node's run_list.
+.PP
+.B node run_list remove [NODE] [ENTRY] (options)
+.PP
+Remove a recipe or role from the node's run_list.
+.PP
+.B node show NODE (options)
+.TP
+\fB\-a\fR, \fB\-\-attribute\fR [ATTR]
+Show only one attribute
+.TP
+\fB\-r\fR, \fB\-\-run\-list\fR
+Show only the run list
+.PP
+Show a node.
+.SH ROLE SUB-COMMANDS
+.PP
+Roles provide a mechanism to apply a set of recipes and attributes to nodes. For example, the 'webserver' role might instruct Chef to add a recipe for Apache, and specify a default domain to use.
+.PP
+.B role bulk delete (options)
+.TP
+\fB\-r\fR, \fB\-\-regex\fR [REGEX]
+Narrow the operation via regular expression
+.PP
+Delete all roles, or only certain roles based on a regular expression.
+.PP
+.B role create ROLE (options)
+.TP
+\fB\-d\fR, \fB\-\-description\fR
+The role description
+.PP
+Create a new role.
+.PP
+.B role delete ROLE (options)
+.PP
+Delete a role.
+.PP
+.B role edit ROLE (options)
+Edit a role.
+.PP
+.B role from file FILE (options)
+.PP
+Update a role from a file.
+.PP
+.B role list (options)
+.TP
+\fB\-w\fR, \fB\-\-with\-uri\fR
+Show corresponding URIs
+.PP
+List roles.
+.PP
+.B role show ROLE (options)
+.TP
+\fB\-a\fR, \fB\-\-attribute\fR [ATTR]
+Show only one attribute
+.PP
+Show a specific role.
+.SH GENERAL SUB-COMMANDS
+.PP
+The following are general sub-commands that do not fit within the other object types used in Chef.
+.PP
+.B configure (options)
+.TP
+\fB\-r\fR, \fB\-\-repository\fR REPO
+The path to your chef\-repo
+.PP
+Create a configuration file for knife. This will prompt for values to enter into the file. See "\fBCONFIGURATION\fR" below for available options.
+.PP
+.B ec2 instance data [RUN LIST...] (options)
+.TP
+\fB\-e\fR, \fB\-\-edit\fR
+Edit the instance data
+.PP
+Chef is commonly used with Amazon AWS EC2 nodes. This command will generate instance metadata that can be used to automatically configure an EC2 instance with Chef.
+.PP
+.B search INDEX QUERY (options)
+.TP
+\fB\-a\fR, \fB\-\-attribute\fR [ATTR]
+Show only one attribute
+.TP
+\fB\-i\fR, \fB\-\-id\-only\fR
+Show only the ID of matching objects
+.TP
+\fB\-R\fR, \fB\-\-rows\fR INT
+The number of rows to return
+.TP
+\fB\-r\fR, \fB\-\-run\-list\fR
+Show only the run list
+.TP
+\fB\-o\fR, \fB\-\-sort\fR SORT
+The order to sort the results in
+.TP
+\fB\-b\fR, \fB\-\-start\fR ROW
+The row to start returning results at
+.PP
+Search indexes are a powerful feature of the Chef server and the search subcommand allows searching any of the available indexes using the SOLR query syntax.
+.SH CONFIGURATION
+The knife configuration file is a Ruby DSL. If it exists, knife uses the settings for \fBGENERAL OPTIONS\fR defaults.
+.TP
+.B log_level
+A Ruby symbol specifying the log level. Corresponds to the \-l or \-\-log_level option. Default is :info.
+.TP
+.B log_location
+Corresponds to the \-L or \-\-logfile option. Default is STDOUT.
+.TP
+.B node_name
+User to authenticate to the Chef server. Corresponds to the \-u or \-\-user option. This is requested from the user when running this sub-command.
+.TP
+.B client_key
+Private key file to authenticate to the Chef server. Corresponds to the \-k or \-\-key option. This is requested from the user when running this sub-command.
+.TP
+.B chef_server_url
+URL of the Chef server. Corresponds to the \-s or \-\-server\-url option. This is requested from the user when running this sub-command.
+.TP
+.B cache_type
+The type of cache to use. Default is \fIBasicFile\fR. This can be any type of Cache that moneta supports: BasicFile, Berkeley, Couch, DataMapper, File, LMC, Memcache, Memory, MongoDB, Redis, Rufus, S3, SDBM, Tyrant, Xattr, YAML.
+.TP
+.B cache_options
+Specifies various options to use for caching. Default reads the Chef client configuration (/etc/chef/checksums).
+.SH FILES
+.PP
+\fI~/.chef/knife.rb\fR
+.TP
+Ruby DSL configuration file for Knife. See "\fBCONFIGURATION\fR".
+.SH SEE ALSO
+.PP
+Full documentation for Chef and Knife is located on the Chef wiki, http://wiki.opscode.com/display/chef/Home.
+.PP
+JSON is JavaScript Object Notation and more information can be found at http://json.org/.
+.PP
+SOLR is an open source search engine. The Chef Server includes a SOLR installation. More information about SOLR, including search query syntax, can be found at http://lucene.apache.org/solr/.
+.SH AUTHOR
+Chef was written by Adam Jacob <adam@ospcode.com> of Opscode (http://www.opscode.com), with contributions from the community.
+This manual page was written by Joshua Timberman <joshua@opscode.com> with help2man. Permission is granted
+to copy, distribute and / or modify this document under the terms of the Apache 2.0 License.
+.PP
+On Debian systems, the complete text of the Apache 2.0 License can be found in
+/usr/share/common-licenses/Apache-2.0.