Yes. I understand that. I posted the portion of the strace from the second run. On the first run, my result code is this:
26971 write(1, "\33[0;37mdebug: Augeas[memlock](provider=augeas): Files changed, should execute\33[0m", 81) = 81 26971 write(1, "\n", 1) = 1 ... 26971 sendto(5, "<31>Jun 4 09:32:46 puppetd[26971]: (Augeas[memlock] (provider=augeas)) Files changed, should execute", 100, MSG_NOSIGNAL, NULL, 0) = 100 So Augeas recognizes that it's supposed to do something, but on the second run, it doesn't actually do it and returns a fail code. On Jun 4, 8:54 am, Bryan Kearney <bkear...@redhat.com> wrote: > Gajillion wrote: > > So, a quick question then. I ran a very verbose strace on puppet > > while it was going through this change. What I see is this. > > <SNIP LOTS OF LOW LEVEL TRACEY STUFF> > > You need to differentiate the plugin and augeas. Augeas writes a temp > file and then copies it to the final location. > > Now.. the plugin. The first augeas plugin always ran augeas, which > caused the task to fire even if no change was made to the file. We > changed this by adding a no-op mode to augeas, and having the plugin do > a "test run" of the changes to determine if it needs to run. > > So.. you are seeing first he test run, and then the actual run. > > -- bk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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 -~----------~----~----~----~------~----~------~--~---
