lobot 2.1.0 → 3.0.0

data/chef/travis-cookbooks/worker_host/apt/resources/repository.rb

@@ -1,30 +0,0 @@
-#
-# Cookbook Name:: apt
-# Resource:: repository
-#
-# Copyright 2010-2011, Opscode, Inc.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-
-actions :add, :remove
-
-#name of the repo, used for source.list filename
-attribute :repo_name, :kind_of => String, :name_attribute => true
-attribute :uri, :kind_of => String
-attribute :distribution, :kind_of => String
-attribute :components, :kind_of => Array, :default => []
-#whether or not to add the repository as a source repo as well
-attribute :deb_src, :default => false
-attribute :keyserver, :kind_of => String, :default => nil
-attribute :key, :kind_of => String, :default => nil

data/chef/travis-cookbooks/worker_host/build-essential/README.md

@@ -1,24 +0,0 @@
-DESCRIPTION
-===========
-
-Installs packages required for compiling C software from source.
-
-LICENSE AND AUTHOR
-==================
-
-Author:: Joshua Timberman (<joshua@opscode.com>)
-Author:: Seth Chisamore (<schisamo@opscode.com>)
-
-Copyright 2009-2011, Opscode, Inc.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.

data/chef/travis-cookbooks/worker_host/build-essential/metadata.rb

@@ -1,10 +0,0 @@
-maintainer        "Opscode, Inc."
-maintainer_email  "cookbooks@opscode.com"
-license           "Apache 2.0"
-description       "Installs C compiler / build tools"
-version           "1.0.0"
-recipe            "build-essential", "Installs C compiler and build tools on Linux"
-
-%w{ fedora redhat centos ubuntu debian }.each do |os|
-  supports os
-end

data/chef/travis-cookbooks/worker_host/build-essential/recipes/default.rb

@@ -1,45 +0,0 @@
-#
-# Cookbook Name:: build-essential
-# Recipe:: default
-#
-# Copyright 2008-2009, Opscode, Inc.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-
-case node['platform']
-when "ubuntu","debian"
-  %w{build-essential binutils-doc zsh}.each do |pkg|
-    package pkg do
-      action :install
-    end
-  end
-when "centos","redhat","fedora"
-  %w{gcc gcc-c++ kernel-devel make zsh}.each do |pkg|
-    package pkg do
-      action :install
-    end
-  end
-end
-
-package "autoconf" do
-  action :install
-end
-
-package "flex" do
-  action :install
-end
-
-package "bison" do
-  action :install
-end

data/chef/travis-cookbooks/worker_host/chef-client/CHANGELOG.md

@@ -1,29 +0,0 @@
-## v1.1.2:
-
-* [COOK-1039] - support mac_os_x_server
-
-## v1.1.0:
-
-* [COOK-909] - trigger upstart on correct event
-* [COOK-795] - add windows support with winsw
-* [COOK-798] - added recipe to run chef-client as a cron job
-* [COOK-986] - don't delete the validation.pem if chef-server recipe
-  is detected
-
-## v1.0.4:
-
-* [COOK-670] - Added Solaris service-installation support for chef-client cookbook.
-* [COOK-781] - chef-client service recipe fails with chef 0.9.x
-
-## v1.0.2:
-
-* [CHEF-2491] init scripts should implement reload
-
-## v1.0.0:
-
-* [COOK-204] chef::client pid template doesn't match package expectations
-* [COOK-491] service config/defaults should not be pulled from Chef gem
-* [COOK-525] Tell bluepill to daemonize chef-client command
-* [COOK-554] Typo in backup_path
-* [COOK-609] chef-client cookbook fails if init_type is set to upstart and chef is installed from deb
-* [COOK-635] Allow configuration of path to chef-client binary in init script

data/chef/travis-cookbooks/worker_host/chef-client/CONTRIBUTING

@@ -1,29 +0,0 @@
-If you would like to contribute, please open a ticket in JIRA:
-
-* http://tickets.opscode.com
-
-Create the ticket in the COOK project and use the cookbook name as the
-component.
-
-For all code contributions, we ask that contributors sign a
-contributor license agreement (CLA). Instructions may be found here:
-
-* http://wiki.opscode.com/display/chef/How+to+Contribute
-
-When contributing changes to individual cookbooks, please do not
-modify the version number in the metadata.rb. Also please do not
-update the CHANGELOG.md for a new version. Not all changes to a
-cookbook may be merged and released in the same versions. Opscode will
-handle the version updates during the release process. You are welcome
-to correct typos or otherwise make updates documentation in the
-README.
-
-If a contribution adds new platforms or platform versions, indicate
-such in the body of the commit message(s), and update the relevant
-COOK ticket. When writing commit messages, it is helpful for others if
-you indicate the COOK ticket. For example:
-
-    git commit -m '[COOK-1041] Updated pool resource to correctly delete.'
-
-In the ticket itself, it is also helpful if you include log output of
-a successful Chef run, but this is not absolutely required.

data/chef/travis-cookbooks/worker_host/chef-client/LICENSE

@@ -1,201 +0,0 @@
-                              Apache License
-                        Version 2.0, January 2004
-                     http://www.apache.org/licenses/
-
-TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-1. Definitions.
-
-   "License" shall mean the terms and conditions for use, reproduction,
-   and distribution as defined by Sections 1 through 9 of this document.
-
-   "Licensor" shall mean the copyright owner or entity authorized by
-   the copyright owner that is granting the License.
-
-   "Legal Entity" shall mean the union of the acting entity and all
-   other entities that control, are controlled by, or are under common
-   control with that entity. For the purposes of this definition,
-   "control" means (i) the power, direct or indirect, to cause the
-   direction or management of such entity, whether by contract or
-   otherwise, or (ii) ownership of fifty percent (50%) or more of the
-   outstanding shares, or (iii) beneficial ownership of such entity.
-
-   "You" (or "Your") shall mean an individual or Legal Entity
-   exercising permissions granted by this License.
-
-   "Source" form shall mean the preferred form for making modifications,
-   including but not limited to software source code, documentation
-   source, and configuration files.
-
-   "Object" form shall mean any form resulting from mechanical
-   transformation or translation of a Source form, including but
-   not limited to compiled object code, generated documentation,
-   and conversions to other media types.
-
-   "Work" shall mean the work of authorship, whether in Source or
-   Object form, made available under the License, as indicated by a
-   copyright notice that is included in or attached to the work
-   (an example is provided in the Appendix below).
-
-   "Derivative Works" shall mean any work, whether in Source or Object
-   form, that is based on (or derived from) the Work and for which the
-   editorial revisions, annotations, elaborations, or other modifications
-   represent, as a whole, an original work of authorship. For the purposes
-   of this License, Derivative Works shall not include works that remain
-   separable from, or merely link (or bind by name) to the interfaces of,
-   the Work and Derivative Works thereof.
-
-   "Contribution" shall mean any work of authorship, including
-   the original version of the Work and any modifications or additions
-   to that Work or Derivative Works thereof, that is intentionally
-   submitted to Licensor for inclusion in the Work by the copyright owner
-   or by an individual or Legal Entity authorized to submit on behalf of
-   the copyright owner. For the purposes of this definition, "submitted"
-   means any form of electronic, verbal, or written communication sent
-   to the Licensor or its representatives, including but not limited to
-   communication on electronic mailing lists, source code control systems,
-   and issue tracking systems that are managed by, or on behalf of, the
-   Licensor for the purpose of discussing and improving the Work, but
-   excluding communication that is conspicuously marked or otherwise
-   designated in writing by the copyright owner as "Not a Contribution."
-
-   "Contributor" shall mean Licensor and any individual or Legal Entity
-   on behalf of whom a Contribution has been received by Licensor and
-   subsequently incorporated within the Work.
-
-2. Grant of Copyright License. Subject to the terms and conditions of
-   this License, each Contributor hereby grants to You a perpetual,
-   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-   copyright license to reproduce, prepare Derivative Works of,
-   publicly display, publicly perform, sublicense, and distribute the
-   Work and such Derivative Works in Source or Object form.
-
-3. Grant of Patent License. Subject to the terms and conditions of
-   this License, each Contributor hereby grants to You a perpetual,
-   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-   (except as stated in this section) patent license to make, have made,
-   use, offer to sell, sell, import, and otherwise transfer the Work,
-   where such license applies only to those patent claims licensable
-   by such Contributor that are necessarily infringed by their
-   Contribution(s) alone or by combination of their Contribution(s)
-   with the Work to which such Contribution(s) was submitted. If You
-   institute patent litigation against any entity (including a
-   cross-claim or counterclaim in a lawsuit) alleging that the Work
-   or a Contribution incorporated within the Work constitutes direct
-   or contributory patent infringement, then any patent licenses
-   granted to You under this License for that Work shall terminate
-   as of the date such litigation is filed.
-
-4. Redistribution. You may reproduce and distribute copies of the
-   Work or Derivative Works thereof in any medium, with or without
-   modifications, and in Source or Object form, provided that You
-   meet the following conditions:
-
-   (a) You must give any other recipients of the Work or
-       Derivative Works a copy of this License; and
-
-   (b) You must cause any modified files to carry prominent notices
-       stating that You changed the files; and
-
-   (c) You must retain, in the Source form of any Derivative Works
-       that You distribute, all copyright, patent, trademark, and
-       attribution notices from the Source form of the Work,
-       excluding those notices that do not pertain to any part of
-       the Derivative Works; and
-
-   (d) If the Work includes a "NOTICE" text file as part of its
-       distribution, then any Derivative Works that You distribute must
-       include a readable copy of the attribution notices contained
-       within such NOTICE file, excluding those notices that do not
-       pertain to any part of the Derivative Works, in at least one
-       of the following places: within a NOTICE text file distributed
-       as part of the Derivative Works; within the Source form or
-       documentation, if provided along with the Derivative Works; or,
-       within a display generated by the Derivative Works, if and
-       wherever such third-party notices normally appear. The contents
-       of the NOTICE file are for informational purposes only and
-       do not modify the License. You may add Your own attribution
-       notices within Derivative Works that You distribute, alongside
-       or as an addendum to the NOTICE text from the Work, provided
-       that such additional attribution notices cannot be construed
-       as modifying the License.
-
-   You may add Your own copyright statement to Your modifications and
-   may provide additional or different license terms and conditions
-   for use, reproduction, or distribution of Your modifications, or
-   for any such Derivative Works as a whole, provided Your use,
-   reproduction, and distribution of the Work otherwise complies with
-   the conditions stated in this License.
-
-5. Submission of Contributions. Unless You explicitly state otherwise,
-   any Contribution intentionally submitted for inclusion in the Work
-   by You to the Licensor shall be under the terms and conditions of
-   this License, without any additional terms or conditions.
-   Notwithstanding the above, nothing herein shall supersede or modify
-   the terms of any separate license agreement you may have executed
-   with Licensor regarding such Contributions.
-
-6. Trademarks. This License does not grant permission to use the trade
-   names, trademarks, service marks, or product names of the Licensor,
-   except as required for reasonable and customary use in describing the
-   origin of the Work and reproducing the content of the NOTICE file.
-
-7. Disclaimer of Warranty. Unless required by applicable law or
-   agreed to in writing, Licensor provides the Work (and each
-   Contributor provides its Contributions) on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-   implied, including, without limitation, any warranties or conditions
-   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-   PARTICULAR PURPOSE. You are solely responsible for determining the
-   appropriateness of using or redistributing the Work and assume any
-   risks associated with Your exercise of permissions under this License.
-
-8. Limitation of Liability. In no event and under no legal theory,
-   whether in tort (including negligence), contract, or otherwise,
-   unless required by applicable law (such as deliberate and grossly
-   negligent acts) or agreed to in writing, shall any Contributor be
-   liable to You for damages, including any direct, indirect, special,
-   incidental, or consequential damages of any character arising as a
-   result of this License or out of the use or inability to use the
-   Work (including but not limited to damages for loss of goodwill,
-   work stoppage, computer failure or malfunction, or any and all
-   other commercial damages or losses), even if such Contributor
-   has been advised of the possibility of such damages.
-
-9. Accepting Warranty or Additional Liability. While redistributing
-   the Work or Derivative Works thereof, You may choose to offer,
-   and charge a fee for, acceptance of support, warranty, indemnity,
-   or other liability obligations and/or rights consistent with this
-   License. However, in accepting such obligations, You may act only
-   on Your own behalf and on Your sole responsibility, not on behalf
-   of any other Contributor, and only if You agree to indemnify,
-   defend, and hold each Contributor harmless for any liability
-   incurred by, or claims asserted against, such Contributor by reason
-   of your accepting any such warranty or additional liability.
-
-END OF TERMS AND CONDITIONS
-
-APPENDIX: How to apply the Apache License to your work.
-
-   To apply the Apache License to your work, attach the following
-   boilerplate notice, with the fields enclosed by brackets "[]"
-   replaced with your own identifying information. (Don't include
-   the brackets!)  The text should be enclosed in the appropriate
-   comment syntax for the file format. We also recommend that a
-   file or class name and description of purpose be included on the
-   same "printed page" as the copyright notice for easier
-   identification within third-party archives.
-
-Copyright [yyyy] [name of copyright owner]
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.

data/chef/travis-cookbooks/worker_host/chef-client/README.md

@@ -1,265 +0,0 @@
-Description
-===========
-
-This cookbook is used to configure a system as a Chef Client.
-
-Requirements
-============
-
-Chef 0.9.12 or higher is required.
-
-Platforms
----------
-
-The following platforms are supported by this cookbook, meaning that the recipes run on these platforms without error.
-
-* Debian
-* Ubuntu
-* Red Hat
-* CentOS
-* Fedora
-* ArchLinux
-* FreeBSD
-* Mac OS X
-* Mac OS X Server
-
-Opscode Cookbooks
------------------
-
-Other cookbooks can be used with this cookbook but they are not explicitly required. The default settings in this cookbook do not require their use. The other cookbooks (on community.opsocde.com) are:
-
-* bluepill
-* daemontools
-* runit
-
-See __USAGE__ below.
-
-Attributes
-==========
-
-* `node["chef_client"]["interval"]` - Sets `Chef::Config[:interval]` via command-line option for number of seconds between chef-client daemon runs. Default 1800.
-* `node["chef_client"]["splay"]` - Sets `Chef::Config[:splay]` via command-line option for a random amount of seconds to add to interval. Default 20.
-* `node["chef_client"]["log_dir"]` - Sets directory used in `Chef::Config[:log_location]` via command-line option to a location where chef-client should log output. Default "/var/log/chef".
-* `node["chef_client"]["conf_dir"]` - Sets directory used via command-line option to a location where chef-client search for the client config file . Default "/etc/chef".
-* `node["chef_client"]["bin"]` - Sets the full path to the `chef-client` binary.  Mainly used to set a specific path if multiple versions of chef-client exist on a system or the bin has been installed in a non-sane path. Default "/usr/bin/chef-client"
-* `node["chef_client"]["server_url"]` - Sets `Chef::Config[:chef_server_url]` in the config file to the Chef Server URI. Default "http://localhost:4000". See __USAGE__.
-* `node["chef_client"]["validation_client_name"]` - Sets `Chef::Config[:validation_client_name]` in the config file to the name of the validation client. Default "chef-validator". See __USAGE__.
-* `node["chef_client"]["init_style"]` - Sets up the client service based on the style of init system to use. Default is based on platform and falls back to "none". See __USAGE__.
-* `node["chef_client"]["run_path"]` - Directory location where chef-client should write the PID file. Default based on platform, falls back to "/var/run".
-* `node["chef_client"]["cache_path"]` - Directory location for `Chef::Config[:file_cache_path]` where chef-client will cache various files. Default is based on platform, falls back to "/var/chef/cache".
-* `node["chef_client"]["backup_path"]` - Directory location for `Chef::Config[:file_backup_path]` where chef-client will backup templates and cookbook files. Default is based on platform, falls back to "/var/chef/backup".
-* node["chef_client"]["cron"]["minute"] - The hour that chef-client will run as a cron task, only applicable if the you set "cron" as the "init_style"
-* node["chef_client"]["cron"]["hour"] - The hour that chef-client will run as a cron task, only applicable if the you set "cron" as the "init_style"
-
-
-
-Recipes
-=======
-
-This section describes the recipes in the cookbook and how to use them in your environment.
-
-config
-------
-
-Sets up the `/etc/chef/client.rb` config file from a template and reloads the configuration for the current chef-client run.
-
-service
--------
-
-Use this recipe on systems that should have a `chef-client` daemon running, such as when Knife bootstrap was used to install Chef on a new system.
-
-This recipe sets up the `chef-client` service depending on the `init_style` attribute (see above). The following init styles are supported:
-
-* init - uses the init script included in the chef gem, supported on debian and redhat family distributions.
-* upstart - uses the upstart job included in the chef gem, supported on ubuntu.
-* arch - uses the init script included in this cookbook for ArchLinux, supported on arch.
-* runit - sets up the service under runit, supported on ubuntu, debian and gentoo.
-* bluepill - sets up the service under bluepill. As bluepill is a pure ruby process monitor, this should work on any platform.
-* daemontools -sets up the service under daemontools, supported on debian, ubuntu and arch
-* bsd - prints a message about how to update BSD systems to enable the chef-client service, supported on Free/OpenBSD and OSX.
-
-default
--------
-
-Includes the `chef-client::service` recipe by default.
-
-delete_validation
------------------
-
-Use this recipe to delete the validation certificate (default `/etc/chef/validation.pem`) when using a `chef-client` after the client has been validated and authorized to connect to the server.
-
-Beware if using this on your Chef Server. First copy the validation.pem certificate file to another location, such as your knife configuration directory (`~/.chef`) or [Chef Repository](http://wiki.opscode.com/display/chef/Chef+Repository).
-
-cron
-----
-
-Use this recipe to run chef-client as a cron job rather than as a
-service. The cron job runs after random delay that is between 0 and 90
-seconds to ensure that the chef-clients don't attempt to connect to
-the chef-server at the exact same time. You should set
-node["chef_client"]["init_style"] = "none" when you use this mode but
-it is not required.
-
-
-
-USAGE
-=====
-
-Create a `base` role that will represent the base configuration for any system that includes managing aspects of the chef-client. Add recipes to the run list of the role, customize the attributes, and apply the role to nodes. For example, the following role (Ruby DSL) will set the init style to `init`, delete the validation certificate (as the client would already be authenticated) and set up the chef-client as a service using the init style.
-
-    name "base"
-    description "Base role applied to all nodes"
-    override_attributes(
-      "chef_client" => {
-        "init_style" => "init"
-      }
-    )
-    run_list(
-      "recipe[chef-client::delete_validation]",
-      "recipe[chef-client::config]",
-      "recipe[chef-client::service]"
-    )
-
-The `chef-client::config` recipe is only required with init style `init` (default setting for the attribute on debian/redhat family platforms, because the init script doesn't include the `pid_file` option which is set in the config.
-
-The default Chef Server will be `http://localhost:4000` which is the `Chef::Config[:chef_server_url]` default value. To use the config recipe with the Opscode Platform, for example, add the following to the `override_attributes`
-
-    override_attributes(
-      "chef_client" => {
-        "server_url" => "https://api.opscode.com/organizations/ORGNAME",
-        "validation_client_name" => "ORGNAME-validator"
-      }
-    )
-
-Where ORGNAME is your Opscode Platform organization name. Be sure to add these attributes to the role if modifying per the section below.
-
-You can also set all of the `Chef::Config` http proxy related settings.  By default Chef will not use a proxy.
-
-    override_attributes(
-      "chef_client" => {
-        "http_proxy" => "http://proxy.vmware.com:3128",
-        "https_proxy" => "http://proxy.vmware.com:3128",
-        "http_proxy_user" => "my_username",
-        "http_proxy_pass" => "Awe_some_Pass_Word!",
-        "no_proxy" => "*.vmware.com,10.*"
-      }
-    )
-
-Alternate Init Styles
----------------------
-
-The alternate init styles available are:
-
-* runit
-* bluepill
-* daemontools
-* none -- should be specified if you are running chef-client as cron job
-
-For usage, see below.
-
-# Runit
-
-To use runit, download the cookbook from the cookbook site.
-
-    knife cookbook site vendor runit -d
-
-Change the `init_style` to runit in the base role and add the runit recipe to the role's run list:
-
-    name "base"
-    description "Base role applied to all nodes"
-    override_attributes(
-      "chef_client" => {
-        "init_style" => "runit"
-      }
-    )
-    run_list(
-      "recipe[chef-client::delete_validation]",
-      "recipe[runit]",
-      "recipe[chef-client]"
-    )
-
-The `chef-client` recipe will create the chef-client service configured with runit. The runit run script will be located in `/etc/sv/chef-client/run`. The output log will be in the runit service directory, `/etc/sv/chef-client/log/main/current`.
-
-# Bluepill
-
-To use bluepill, download the cookbook from the cookbook site.
-
-    knife cookbook site vendor bluepill -d
-
-Change the `init_style` to runit in the base role and add the bluepill recipe to the role's run list:
-
-    name "base"
-    description "Base role applied to all nodes"
-    override_attributes(
-      "chef_client" => {
-        "init_style" => "bluepill"
-      }
-    )
-    run_list(
-      "recipe[chef-client::delete_validation]",
-      "recipe[bluepill]",
-      "recipe[chef-client]"
-    )
-
-The `chef-client` recipe will create the chef-client service configured with bluepill. The bluepill "pill" will be located in `/etc/bluepill/chef-client.pill`. The output log will be to client.log file in the `node["chef_client"]["log_dir"]` location, `/var/log/chef/client` by default.
-
-# Daemontools
-
-To use daemontools, download the cookbook from the cookbook site.
-
-    knife cookbook site vendor daemontools -d
-
-Change the `init_style` to runit in the base role and add the daemontools recipe to the role's run list:
-
-    name "base"
-    description "Base role applied to all nodes"
-    override_attributes(
-      "chef_client" => {
-        "init_style" => "daemontools"
-      }
-    )
-    run_list(
-      "recipe[chef-client::delete_validation]",
-      "recipe[daemontools]",
-      "recipe[chef-client]"
-    )
-
-The `chef-client` recipe will create the chef-cilent service configured under daemontools. It uses the same sv run scripts as the runit recipe. The run script will be located in `/etc/sv/chef-client/run`. The output log will be in the daemontools service directory, `/etc/sv/chef-client/log/main/current`.
-
-Templates
-=========
-
-chef-client.pill.erb
---------------------
-
-Bluepill configuration for the chef-client service.
-
-client.rb.erb
--------------
-
-Configuration for the client, lands in directory specified by `node["chef_client"]["conf_dir"]` (`/etc/chef/client.rb` by default).
-
-`sv-chef-client-*run.erb`
--------------------------
-
-Runit and Daemontools run script for chef-client service and logs.
-
-Logs will be located in the `node["chef_client"]["log_dir"]`.
-
-License and Author
-==================
-
-Author:: Joshua Timberman (<joshua@opscode.com>)
-Author:: Seth Chisamore (<schisamo@opscode.com>)
-Copyright:: 2010-2011, Opscode, Inc.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and