I found that. And I was royally peeved, as nowhere in the logs was there
any indication there was an issue. The developers of Passenger pointed
out that I can set options in the httpd.conf to specify a user and group --
but these products should be logging better data.
I literally spent days
Sam,
You should setup MCollective. You can implement a simple plugin that
changes the global noop setting in puppet.conf and restarts the
daemon.
That will give you the best scalability, and you have fine-grained
control in MCollective on which hosts run using metadata in your
Puppet classes and
Sam,
You could make some changes to you site.pp and set some defaults like this
Exec {
schedule => $::globalvars_schedule,
noop => $::globalvars_noop,
}
File {
schedule => $::globalvars_schedule,
noop => $::globalvars_noop,
}
Group {
schedule => $::globalvars_schedule,
noop => $::glo
I am using Puppet 2.7.21 open source version, and running on my mac. I
On Friday, July 26, 2013 8:34:13 AM UTC-7, GregC wrote:
>
> What puppet master version are you running? I also seem to see this
> bizarre behavior in 2.6.11 and no one at puppet labs has responded to this
> hiera issue it j
