On Thu, Sep 18, 2008 at 11:14 AM, Evan Hisey <[EMAIL PROTECTED]> wrote:
>> Modules most certainly can be called from within other modules. Most
>> of the time when I have had problems is has been because the names of
>> the module didn't match the class name in the init.pp. Double check
>> your names and try again.
>>
> Okay this is what I thought, but here is what I have in module named
> and module hpc
>
> named/manifest/init.pp:
>
> class named{
> package{"bind":
> ensure => present,
> }
> service{"named":
> ensure => running,
> enable => true,
> hasstatus => true,
> hasrestart => true,
> }
>
>
> hpc/manifests/init.pp:
> class hpc::master{
> include hpc::named
> }
>
> class hpc::named{
> include named #<<< does not seem to be working
> service{"named": #<<< added to get the notify to work
> ensure => running,
> }
> file{"named.conf.cluster":
> path => "/etc/named.conf",
> source=> "puppet:///hpc/named.conf",
> notify => Service["named"],
> }
>
> Am I missing something in this setup. I would expect the
> Service[named] to complain about being specified twice, but it does
> not.
>
On the otherhand if I use the:
class named::chroot{
include named
package{"bind-chroot":
ensure => present,
require => Package["bind"],
}
class from named/manifests/init.pp in hpc/manifests/init.pp:
class hpc::named{
include named::chroot
service{"named": #<<< added to get the notify to work
ensure => running,
}
,Then the Service[named] in hpc::named breaks as expected. I think
this may be a bug in the autoload magic for modules.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
