[chef] Re: Re: chef-client cookbook problem: log_location not set properly?

["Julian C. Dunn" < >]

Presumably... should I file a bug?

- Julian

On Sun, Jun 3, 2012 at 4:44 PM, Adam Jacob 
<
 >
 wrote:
> Hrm - that's odd. One imagines that's an artifact of having the STDOUT
> constant turned in to a string?
>
> Adam
>
> On Sat, Jun 2, 2012 at 8:22 PM, Julian C. Dunn 
> <
 >
>  wrote:
>> I'm in the midst of migrating to Opscode's chef-client cookbook.
>> Before I roll it out across ~70 systems I thought it prudent to test
>> it with chef-solo in a VM first. I have the following as JSON
>> attributes:
>>
>> {
>>  "run_list": [ "recipe[chef-client::config]", "recipe[chef-client]" ],
>>  "chef_client": {
>>        "server_url": "http://bogus.example.com:4000";,
>>        "environment": "dev",
>>        "init_style": "init"
>>  }
>> }
>>
>> The generated client.rb is sensible except for one line:
>>
>> log_location     #<IO:0x2b06082b0ac8>
>>
>> I don't know enough Ruby to understand the case statement in the
>> recipe involving testing to see if this attribute is a String, IO,
>> etc. Can someone help me out and let me know how to fix this?
>>
>> - Julian
>>
>> --
>> Julian C. Dunn 
>> <
 >
>> Systems Engineer, Project Leader, Writer
>> WWW: www.juliandunn.net
>> Phone: (347) 986-0308
>> LinkedIn: linkedin.com/in/julian
>
>
>
> --
> Opscode, Inc.
> Adam Jacob, Chief Customer Officer
> T: (206) 619-7151 E: 
>