On Sep 2, 2009, at 3:55 AM, Dan Bode wrote:
> Hi all,
>
> I have encountered some that I dont quite understand.
>
> I am trying to parse log messages to create summaries, and I have
> seen an event that I do not understand.
>
> (//Node[default]/base/syslog/syslog::base/File[syslog.conf]/content)
> is {md5}549c6de7a94e882b19f98ec953c8604a, should be
> {md5}ddf8df9575b220bea7ad07d1ebce64e9 (noop)
> (//Node[default]/base/syslog/syslog::base/File[syslog.conf])
> Scheduling refresh of Service[syslog]
> (//Node[default]/base/syslog/syslog::base/Service[syslog]) Would
> have triggered refresh from 1 dependencies
> (//Node[default]/base/autofs/Service[autofs]) Would have triggered
> refresh from 1 dependencies
>
> Should it ever be possible for a file content change on noop to
> Schedule a refresh of a service? This error just occurs once and was
> not reproduced in a subsequent run. Any ideas?
>
> (yes I will open a ticket, but first I would like to understand the
> expected behavior)
This was specifically requested - people wanted to know if a service
*would* restart, so our noop non-changes result in a noop event that
doesn't actually refresh, but just logs that it would refresh.
--
A diplomat is a man who can convince his wife she'd look stout in a fur
coat.
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
