You'll want to have one inherit the parent (named) and use the overide
syntax on the resources.
class named::hpc inherits named {
Service['named'] { enabled => false }
}
Regards,
Aj
On 23/09/2008, at 3:25 AM, "Chad Huneycutt" <[EMAIL PROTECTED]>
wrote:
>
> Are you actually including both "named" and "hpc::named" on a single
> host? If not, then there will not be a conflict.
>
> - Chad
>
> On Wed, Sep 17, 2008 at 12:41 PM, Evan Hisey <[EMAIL PROTECTED]> wrote:
>>
>> As understand puppet I should not be able to have two service[named]
>> entries in the same compiled manifest. To me this means the following
>> should not work:
>>
>> In module named/manifest/init.pp I have:
>> class named{
>> package{"bind":
>> ensure => present,
>> }
>> service{"named":
>> ensure => running,
>> enable => true,
>> hasstatus => true,
>> hasrestart => true,
>> }
>>
>> }
>>
>> And then in in module hpc/manifest/init.pp I have:
>> class hpc::named{
>> include named
>> service{"named":
>> ensure => running,
>> }
>> file{"named.conf.cluster":
>> path => "/etc/named.conf",
>> source=> "puppet:///hpc/named.conf",
>> notify => Service["named"],
>> }
>> }
>>
>> I randomly tried this expecting it to explode, while waiting for a
>> reply to notifying resources across modules, as I need HPC
>> File["named.conf.cluster"] to tell Service[named] to reload. I am
>> very
>> suprised this is working. can some explain why to me.
>>
>> Evan
>>
>>>
>>
>
>
>
> --
> Chad M. Huneycutt
>
> >
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
