Community and the Chef-Client Cookbook - Learning Chef - page 239

$ kitchen login
Last login: Sat Jul 26 01:17:10 2014 from 192.168.33.1
Welcome to your Packer-built virtual machine.
[vagrant@node-centos65 ~]$ sudo chef-client
...
* service[chef-client] action enable
- enable service service[chef-client]
* service[chef-client] action start
- start service service[chef-client]
* service[chef-client] action restart
- restart service service[chef-client]
Running handlers:
Running handlers complete
Chef Client finished, 10/11 resources updated in 8.137774709 seconds
While you are still on the node, verify that the validation.pem was deleted and that the chef-
client is now running as a daemon:
[vagrant@node-centos65 ~]$ ls /etc/chef
client.pem client.rb first-boot.json
[vagrant@node-centos65 ~]$ ps awux | grep chef-client
root 2184 0.0 7.9 217180 40152 ? Sl 21:52
0:00 /opt/chef/embedded/bin/ruby /usr/bin/chef-client -d -c
/etc/chef/client.rb -L /var/log/chef/client.log -P /var/run/chef/client.pid
-i 1800 -s 300
Return back to the host prompt now:
[vagrant@node-centos65 ~]$ exit
Configure Knife to Use a Production SSL Setup
In Chapter 6 , we mentioned the SSL warning you get running chef-client on the node
when HTTPS connections are not validated. Before we end this chapter, let's go over how
you would configure SSL in a production environment.