Information Technology Reference
In-Depth Information
* directory[/var/cache/chef] action create (up to date)
* directory[/var/lib/chef] action create (up to date)
* directory[/var/log/chef] action create (up to date)
* directory[/etc/chef] action create (up to date)
* template[/etc/init.d/chef-client] action create (up to date)
* template[/etc/sysconfig/chef-client] action create (up to date)
* service[chef-client] action enable (up to date)
* service[chef-client] action start (up to date)
Recipe: chef-client::config
* directory[/var/run/chef] action create (up to date)
* directory[/var/cache/chef] action create (up to date)
* directory[/var/lib/chef] action create (up to date)
* directory[/var/log/chef] action create (up to date)
* directory[/etc/chef] action create (up to date)
* template[/etc/chef/client.rb] action create (up to date)
* directory[/etc/chef/client.d] action create (up to date)
* ruby_block[reload_client_config] action nothing (skipped due to
action :nothing)
Running handlers:
Running handlers complete
Chef Client finished, 0/17 resources updated in 2.72449843 seconds
Go ahead and
exit
back out to the host prompt now:
[vagrant@node-centos65 ~]$
exit
logout
Connection to 127.0.0.1 closed.
Your tour of the
chef-client
cookbook is now complete. We are now done with both our
Chef Server and node. Go ahead and
kitchen destroy
both of them.
Linux/Mac OS X:
$
cd $HOME/chef-repo/cookbooks/enterprise-chef
$
kitchen destroy
$
cd $HOME/chef-repo/cookbooks/node
$
kitchen destroy
Windows Command Prompt:
