On Fri, Feb 15, 2013 at 10:12 AM, Felix Frank
<felix.fr...@alumni.tu-berlin.de> wrote:
> Hi,
>
> it's paramount that you generate a unique $name for each invocation of
> your defined type, e.g.
>
> pam::header { "limits-$name": }
>
> You can take advantage of the fact that the "calling" defines have
> unique names of their own.Right, that was my dump mistake. It still doesn't take away from the fact that the header will be added multiple times. > HTH, > Felix > > On 02/15/2013 03:31 PM, Darin Perusich wrote: >>> > I believe what you want is another defined type that represents "the >>> > header snippet for a specific pam config file" and declares a >>> > concat::fragment "$name-header" or somesuch. Each of the other defined >>> > types then contains an instance of this new type, probably not passing >>> > more than the name. >> I've tried this approach and the problem you run into is when defining >> multiple pam::limits you create a duplicate declaration caused by >> pam::header being called for each instance. It attempts to create >> multiple headers. > > -- > 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 puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
