knife(8) [linux man page]

KNIFE(8)						      System Manager's Manual							  KNIFE(8)

NAME

       knife, axe, cutter, chainsaw - tools to improve network performance via SNIP

SYNOPSIS

       knife is used to control the network via Sysadmin Network Interrupt Protocol [SNIP].

DESCRIPTION

       Experience  has shown that suitable application of these tools on the network can lead to improved network performance, as busy segments of
       useless traffic can be isolated from the important stuff (and the rest of the world, for that matter).  However, care must be taken, other-
       wise lusers will be complaining about "network downtime".

   knife vs LART
       While  knife can be used as a replacement for LART, the reverse is not generally true; while blunt trauma works wonders on lusers, it tends
       to be ineffective on cables.  Also, note that using knife or one of it's associates as a LART will probably lead to  higher  level  assault
       charges than one would get with a standard LART.

   chainsaw, the power SNIP tool
       chainsaw  is  a	version  of knife that makes quick work of almost any problem.	It also has a correspondingly higher potential for causing
       unintentional damage.  Handle with care.

FILES

       In its normal application to cables, knife uses no files.  If applied to a disk, many files may be affected; see mkfs(8).

SEE ALSO

       lart(8)

BUGS

       You may be required to fix things eventually.

RESTRICTIONS

       Bosses and the legal system may take a dim view of overenthusiastic application of these tools.

AUTHOR

       While the origin of the first knife remains a mystery, this man page was written by Kurt  Hockenbury  <kurt@something.com>.   He  disclaims
       responsibility for any actions inspired by this man page.

HISTORY

       SNIP  was  first  described  on	alt.sysadmin.recovery  by J.D. Falk <jdfalk@cais.cais.com> as a followup to a post by <martin@angela.ctrl-
       c.liu.se>.

																	  KNIFE(8)

KNIFE-CONFIGURE(1)						    Chef Manual 						KNIFE-CONFIGURE(1)

NAME

       knife-configure - Generate configuration files for knife or Chef Client

SYNOPSIS

       knife configure [client] (options)

DESCRIPTION

       Generates a knife.rb configuration file interactively. When given the --initial option, also creates a new administrative user.

CONFIGURE SUBCOMMANDS

       knife configure (options)

       -i, --initial
	      Create an initial API Client

       -r, --repository REPO
	      The path to your chef-repo

       Create  a configuration file for knife. This will prompt for values to enter into the file. Default values are listed in square brackets if
       no other entry is typed. See knife(1) for a description of configuration options.

       knife configure client directory

       Read the knife.rb config file and generate a config file suitable for use in /etc/chef/client.rb and copy the validation  certificate  into
       the specified directory.

EXAMPLES

       o   On  a  freshly  installed  Chef Server, use knife configure -i to create an administrator and knife configuration file. Leave the field
	   blank to accept the default value. On most systems, the default values are acceptable.

	   user@host$ knife configure -i
	   Please enter the chef server URL: [http://localhost:4000]
	   Please enter a clientname for the new client: [username]
	   Please enter the existing admin clientname: [chef-webui]
	   Please enter the location of the existing admin client's private key: [/etc/chef/webui.pem]
	   Please enter the validation clientname: [chef-validator]
	   Please enter the location of the validation key: [/etc/chef/validation.pem]
	   Please enter the path to a chef repository (or leave blank):
	   Creating initial API user...
	   Created (or updated) client[username]
	   Configuration file written to /home/username/.chef/knife.rb

	   This creates a new administrator client named username, writes a configuration file to /home/username/.chef/knife.rb, and  the  private
	   key to /home/username/.chef/username.pem. The configuration file and private key may be copied to another system to facilitate adminis-
	   tration of the Chef Server from a remote system. Depending on the value given for the Chef Server URL, you may need to modify that set-
	   ting after copying to a remote host.

SEE ALSO

       knife(1) knife-client(1)

AUTHOR

       Chef was written by Adam Jacob adam@opscode.com with many contributions from the community.

DOCUMENTATION

       This  manual  page was written by Joshua Timberman joshua@opscode.com. Permission is granted to copy, distribute and / or modify this docu-
       ment under the terms of the Apache 2.0 License.

CHEF

       Knife is distributed with Chef. http://wiki.opscode.com/display/chef/Home

Chef 10.12.0							     June 2012							KNIFE-CONFIGURE(1)