On Dec 14, 4:37 pm, Jo Rhett <jrh...@netconsonance.com> wrote: > Try > notify => Service['autofs']
Right. As far as I know, classes do not forward signals to resources they contain. Furthermore, you should consider whether it would be appropriate to combine your two classes. That a resource belonging to one wants to signal a resource belonging to the other is a hint in that direction (but no more than that). I'm not seeing what you gain by defining such fine-grained classes, especially with the implicit dependencies among them (see next). Also, if you do not combine classes, then be sure each class 'include's the other classes whose resources it references. For instance, class zmfs::service should contain "include 'zmfs::config'" at the beginning of its body. Class zmfs::service should 'include' whatever class(es) declares the the 'zmfs' and 'zmfs-init-scripts' packages. On the practical side, this protects you from catalog compilation failures arising from varying parse order. On the conceptual side, it's the Right Thing for classes to formally declare their dependencies. John -- 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.
