Does anyone have a tip regarding this? How do I stop it? I know that the "audit=>all" is causing this. It recorded the MD5 sum of the file when the audit ran for the first time. But a newer file was created as a result of patching the client machine. Is there a command I could rerun on the client or the server to make puppet aware of the new MD5 sum?
Lun. On Wed, Jul 23, 2014 at 3:58 PM, Lunixer <[email protected]> wrote: > > I have an entry for a file in a puppet manifest that checks file > properties. One is the MD5 checksum. > > /etc/puppet/modules/Solaris/manifests/init.pp > file {"/etc/logadm.conf": mode=>"644", owner=>"root", group=>"sys", > checksum=>"md5", audit=>all; } > > Wed Jul 23 03:31:41 -0700 2014 > /Stage[main]/Solaris/File[/etc/logadm.conf]/content (notice): audit change: > previously recorded value {md5}4313e436be52ffe7a8296aec05612c0b has been > changed to {md5}fee96725c6872531af6e65b410f62a3d > > How do you make the message go away? > > -- > > thanks, > [ Lunixer ] > -- thanks, [ Lunixer ] -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CACZbbm6YkUdV9XiEq7tgKt%3Dj9zK2_K2A8G3yGH_6c3dU4-qSZQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
