On Fri, Sep 24, 2010 at 11:29 AM, Tim Lank <timl...@timlank.com> wrote: > It would be great to have it configurable, so that it could be off by > default for those that don't want it. > > I may be in the minority here, but having a surety of exactly what was > executed and a knowledge of the output would be a good thing to me. Seems > that the ability to turn this on would be a very desirable thing.
I understand wanting to know why an exec failed, but what are some actual use cases where you care about the stdout of an exec resource in Puppet? > > Please provide the patch# you are referring to for the on_failure stderr. http://projects.puppetlabs.com/issues/2359 covers it. > > > > On Fri, Sep 24, 2010 at 2:10 PM, Nigel Kersten <nig...@google.com> wrote: >> >> On Fri, Sep 24, 2010 at 10:08 AM, Tim Lank <timl...@timlank.com> wrote: >> > Thanks. Can you elaborate on the puppet's reports? All I see are here: >> > http://docs.puppetlabs.com/references/latest/report.html >> > >> > Is there one that reports on the stdout&stderr of the tasks the client >> > performs? (and not in YAML) >> >> I believe we have a patch that should show the stderr output when an >> exec task fails, but I'm curious as to why you want the stdout? >> >> > >> > The remote syslog would take some coding to cull together in a coherent >> > and >> > readable manner for each individual client. >> > >> > >> > On Fri, Sep 24, 2010 at 12:55 PM, Patrick <kc7...@gmail.com> wrote: >> >> >> >> On Sep 24, 2010, at 3:52 AM, Tim Lank wrote: >> >> >> >> puppet-users: >> >> >> >> I'm trying to find a way to obtain the stdout (and stderr) output from >> >> individual puppet client configuration runs. I'd like a central >> >> storage of >> >> this information if possible. >> >> >> >> In short, I'd like to know what the client exactly did with the >> >> configuration that it was sent. Ideally I'd like for this to be in one >> >> location so that I can write scripts to report on the results. >> >> >> >> Thanks in advance for your assistance. >> >> >> >> Why not use puppet's reports or a remote syslog? >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups >> >> "Puppet Users" group. >> >> To post to this group, send email to puppet-us...@googlegroups.com. >> >> To unsubscribe from this group, send email to >> >> puppet-users+unsubscr...@googlegroups.com. >> >> For more options, visit this group at >> >> http://groups.google.com/group/puppet-users?hl=en. >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Puppet Users" group. >> > To post to this group, send email to puppet-us...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > puppet-users+unsubscr...@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/puppet-users?hl=en. >> > >> >> >> >> -- >> nigel >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-us...@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
