Mine worked.
On Fri, Mar 1, 2013 at 5:09 PM, Dylan Northrup < "> > wrote:
> To slip into pedantry, it should be 'chef-client 2>&1 | grep -v WARN' and
> that also doesn't show any of the INFO messages.
>
>
> On Fri, Mar 1, 2013 at 6:06 PM, Mike < "> > wrote:
>>
>> I thought you wanted only WARN.
>>
>> How about this?
>>
>> chef-client 2>1 | grep -v WARN
>>
>> On Fri, Mar 1, 2013 at 4:59 PM, Dylan Northrup < "> > wrote:
>> > That would filter out the INFO messsages (which I actually still want to
>> > see) and only show me the WARN messages (which I do not want to see).
>> > Because WARN is higher priority than INFO, there's not an easy way I can
>> > see
>> > to filter out that specific level of message that I can see.
>> >
>> > On Fri, Mar 1, 2013 at 2:39 PM, Mike < "> > wrote:
>> >>
>> >> Change log_level :info
>> >> to
>> >> log_level :warn
>> >>
>> >> for one run?
>> >>
>> >> That's an easy way. :)
>> >>
>> >> On Fri, Mar 1, 2013 at 1:37 PM, Dylan Northrup < "> > wrote:
>> >> > Running chef-client 10.24.0 on some hosts I get a veritable deluge of
>> >> > WARN
>> >> > messages about things that aren't being done quite right and should
>> >> > be
>> >> > changed (many things, I'll add, that had not issued WARN messages in
>> >> > prior
>> >> > versions of chef-client). I'd like to be able to grep out those WARN
>> >> > messages, but when I do it kills all chef-client output. Trying to
>> >> > redirect
>> >> > STDERR doesn't make a difference.
>> >> >
>> >> > Is there a best practice way of filtering chef-client output?
>> >> >
>> >> > --
>> >> > Dylan Northrup
>> >
>> >
>
>
Archive powered by MHonArc 2.6.16.