Issue #2359 has been updated by Luke Kanies. Status changed from Needs design decision to Accepted
---------------------------------------- Bug #2359: stderr output from exec resource is lost http://projects.reductivelabs.com/issues/2359 Author: Alan Harder Status: Accepted Priority: Normal Assigned to: Category: exec Target version: Complexity: Unknown Affected version: 0.24.8 Keywords: stderr output may be important to help determine why a puppet run failed. With this simple script I do not see the exec output: <pre> node '...' { exec { 'stderr_test': command => '/usr/bin/echo test 1>&2', logoutput => true } } </pre> If I remove the "1>&2" then "test" does appear in the puppet output. Using Puppet 0.24.8 on Solaris 10. I saw the comment in the docs regarding the user parameter: "Note that if you use this then any error output is not currently captured. This is because of a bug within Ruby." But note above I am not using the user parameter. Also, does this "bug within Ruby" still exist? -- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
