There also could be mcollective logs on the end-points that would tell
you what command were run etc.
On Wed, Apr 18, 2012 at 6:10 AM, jcbollinger <john.bollin...@stjude.org> wrote:
>
>
> On Apr 18, 3:17 am, Luke Bigum <luke.bi...@lmax.com> wrote:
>> If you're really really lucky you can look in ${vardir}/clientbucket on
>> an Agent (usually /var/lib/puppet/clientbucket) and ${vardir}/bucket on
>> the Master. They are backup directories of files that Puppet replaces,
>> keyed on the MD5 sum of the file. Unfortunately I don't think the User
>> providers file bucket /etc/passwd and /etc/shadow though, but you can
>> always check.
>
>
> As far as I know, Puppet only filebuckets files managed by File
> resources. These are potentially irreplaceable otherwise, whereas
> file modifications performed indirectly via other resource types are
> -- at least in principle -- undoable by managing the affected resource
> back to the original state, as Bernd suggests.
>
>
> John
>
> --
> 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.
>
--
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.
