On 07/20/2010 02:10 PM, Tore wrote:
You could also do: class httpd { ... file { '/etc/monit.d/httpd.conf': ... notify => Service['monit'] }} But I would rather do it on the service, since then you can with ease read one line to find out what that service response to.
I suppose it comes down to where the perceived responsibility for the configuration file lies :
Since it's a Monit configuration file, one could make the argument that should it be part of the monit class (or a sub-class thereof). On the other hand, since the configuration snippet in question relates solely to the HTTPd service, and wouldn't exist on a system that didn't have said service, then it could easily be part of the httpd class.
User preference, ultimately. -- Daniel Maher <dma PLUS puppet AT witbe DOT net> "The Internet is completely over." -- Prince -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
