- From: Phil Dibowitz <
>
- To:
- Subject: [chef] Re: Re: Re: 10.14.4 broken output formatters?
- Date: Wed, 03 Oct 2012 02:02:51 -0700
On 10/02/2012 09:28 AM, Daniel DeLeo wrote:
>
To reply to Bryan's comment about logging vs. formatter output, the reason
>
why
>
it works this way now is simply that output formatters are a new feature
>
that
>
we'd like to have people test in the real world (before they become the
>
default in Chef 11.0). When the formatter output does become the default, we
>
need to decide what we do about the logger output.
>
>
Presently, my opinion is that the logger output should go to a logfile[0]
>
(though I'm open to being convinced otherwise, if there are good arguments),
>
but for a subset of users running Chef as a non-root user additional changes
>
are required to make chef log to a location writable by non-root users.
>
Rather
>
than tackle these issues up-front, we decided to leave the choice up to
>
users
>
who are opting-in to using the formatter feature for now.
>
>
1. e.g., chef-client -L/var/log/chef_client.log -Fmin (or -Fdoc, etc.)
Well, the thing here that I missed and that I think most people will miss
until they look closely is that you're always getting *both* because they are
two independent logging systems. So setting -lfatal just minimizes the logger
output so your formatter output isn't trampled over.
Once I realized that, it all made more sense. :)
--
Phil Dibowitz
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"Be who you are and say what you feel, because those who mind don't matter
and those who matter don't mind."
- Dr. Seuss
Attachment:
signature.asc
Description: OpenPGP digital signature
Archive powered by MHonArc 2.6.16.