Support Chef Client on FreeBSD 10

[anandsuresh]

Running on Vagrant 1.6.3, the chef-solo run finishes, but then segfaults.

==> freebsd-01:
==> freebsd-01:
==> freebsd-01: chef client finished. 624 resources updated, took 982.441548297 seconds
==> freebsd-01: /usr/local/lib/ruby/gems/1.9/gems/chef-11.12.8/lib/chef/client.rb:222:
==> freebsd-01: [BUG]
==> freebsd-01: Segmentation fault
==> freebsd-01:
==> freebsd-01: ruby 1.9.3p484 (2013-11-22 revision 43786) [amd64-freebsd10]
==> freebsd-01: -- Control frame information -----------------------------------------------
==> freebsd-01: bash: line 2:  1187 Segmentation fault      (core dumped) chef-solo -c /vagrant/solo.rb -j /vagrant/dna.json

[btm]

Line 222 of lib/chef/client.rb in Chef 11.12.8 calls Process.waitpid2(pid)

peab92691 chef/lib/chef/client.rb (Chris Roberts                  2012-05-11 14:51:06 -0700 222)         result = Process.waitpid2(pid)

[sersut]

Hrmmm we don't have FreeBSD 10 in our CI test matrix. Seems like 10 is released on Jan 2014. We should get this platform into our matrix and make sure things are working as expected.

Thanks for reporting this @anandsuresh

[anandsuresh]

@sersut Let me know if I can provide any more information/testing. Interestingly, I have not seen this bug since I reported it. It seems to happen once in a blue moon.

[sersut]

Thanks for the note @anandsuresh. I've changed the title to reflect the issue in a slightly better way.

[hirenp]

Is this still an issue? I can help test this.

[sersut]

Closing this issue since this doesn't seem to be a consistently reproing issue.

Let's reopen and investigate if we get another repro of this.

[hirenp]

Hi,
http://www.getchef.com/chef/install/ doesn't list client for FreeBSD10. Are there any known problems with it? I'd like to know and help get them fixed if possible.

[btm]

Last I knew we didn't have internal FreeBSD 10 test machines, which has been the bar for listing newer releases in the past.

It should work though, and install.sh should install on FreeBSD 10, so I think it's up to people testing and reporting specific issues right now.