On Feb 20, 2011, at 12:44 AM, donavan wrote:
> Is there a specific reason for forcing the log destination to :console
> in the agent application? If the log level is set with verbose/debug
> then :console is always added to any logdest the user specifies. I see
> bits of this in the application tests and patches for #1886 & #5952.
>
> The apply and master applications, for example, don't behave this way.
> The user is able to set the log level with verbose/debug options
> independently of the logdest. This leads to inconsistent behavior
> across applications when trying to use an alternate destination[1].
>
> Ideally I'd like to set log level to any of the supported levels,
> independent of destination. I could also see the argument for 'format'
> of color/html/json/text being split out of logdest as well.
Hmm, that's probably a bug. I know the behavior has changed a bit over the
years, but I didn't think either of those modes still required console access.
Is that true even when the agent goes into the background? Or do you want a
foreground process with no console logging?
--
Experience is the name everyone gives to their mistakes.
-- Oscar Wilde
---------------------------------------------------------------------
Luke Kanies -|- http://puppetlabs.com -|- +1(615)594-8199
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
