Issue #3670 has been updated by Alan Barrett.
Luke Kanies wrote: > Is this a general thing we should do? Always send log output to stderr, > rather than stdout? In cases where stdout is supposed to contain useful output, it's clearly wrong to mess up the output by mixing it with log messages. In cases where stdout is otherwise unused, then it may be debatable whether log messages should go to stdout or stderr, but I prefer stderr, for consistency with the other case. ---------------------------------------- Bug #3670: "puppetmasterd --compile" sends extraneous messages to stdout http://projects.puppetlabs.com/issues/3670 Author: Alan Barrett Status: Needs design decision Priority: Normal Assigned to: Luke Kanies Category: Target version: Rowlf Affected version: 0.25.4 Keywords: Branch: When I run <pre> puppetmasterd --compile myclient.example.net >myclient.yaml </pre> then the output file contains <pre> ESC[0;36mnotice: Compiled catalog for myclient.example.net in 40.23 secondsESC[0m {"data":{"edges":[... (one very long line of data) ... </pre> The "notice:" line should have been sent to stderr, not to stdout, so that it does not get mixed in with the YAML data. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
