Just for being sure. Do you have selinux in enforcing mode ? What tell
you the sestatus command ? And ausearch -m avc ? Regards
2011/9/2, Chris Doherty :
> Hi, all. I'm having a problem that I'm virtually certain is a perms
> issue, but I can't figure out where it's going wrong.
>
> The puppetmas
Hi, all. I'm having a problem that I'm virtually certain is a perms
issue, but I can't figure out where it's going wrong.
The puppetmaster server is a CentOS6 x64 minimal install.
Puppet was installed from the epel-testing repository (2.6.6-1) and an
updated SELinux policy loaded to allow it to
Hi,
I have read various threads about ordering things in puppet, using
stages, before and after etc... but unfortunately it didn't answer my
question.
I have multiple parametrised function definitions like that:
define function1($param) {
exec { "do-$param-something":
subscribe =>
- Original Message -
> Btw, Rip or anyone, any suggestion on how to sort alphabetically the
> scope variables so that the generated yaml doesn't change at (almost)
> every puppet run?
>
> content => inline_template("<%= scope.to_hash.reject { |k,v| k.to_s
> =~ /(uptime_seconds|timestamp
Btw, Rip or anyone, any suggestion on how to sort alphabetically the
scope variables so that the generated yaml doesn't change at (almost)
every puppet run?
content => inline_template("<%= scope.to_hash.reject { |k,v| k.to_s
=~ /(uptime_seconds|timestamp|free)/ }.to_yaml %>")
On 2 Set, 20:26, "R
