On Fri, 2012-08-17 at 15:41 -0700, Sean Carolan wrote:
> > You don't say what version of puppet you're using, whether you're using
> > an ENC, or whether you're already using either extlookup() or hiera(),
> > so it's really difficult to suggest something that integrates well with
> > your current environment.
>
> Sorry I didn't provide more detail. We're using puppet 2.6.13. We
> have a single *.pp config file for each and every host, so specifying
> additional classes is not hard to do on a host-per-host basis. Here's
> the limits.conf config from the class that has been applied to these
> hosts:
<snip>
> Basically I just want this "file" type to not be active on three
> hosts. I don't need to be able to detect the hosts, as I can specify
> the config manually in each of their config files.
It's not really the cleanest-looking thing, but the easiest option for
your particular case is to wrap the file resource in an if statement
like this:
if (! $::security_limits_disabled) {
file { '/etc/security/limits.conf':
...
}
}
then, on each of the nodes where you don't want to use the limits.conf
file, you can just set the variable to true:
node special_box {
include some_classes
$security_limits_disabled = true
}
--
Calvin Walton <calvin.wal...@kepstin.ca>
--
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.
