On Thu, Jun 21, 2012 at 6:20 AM, trey85stang trey85st...@gmail.com wrote:
Now in each case I have files where httpd is notified to refresh...
Is there a way to work around this without creating a custom module
just for this one case? As you can see from the below error message I
tried changing
Sounds good, not the way I was hoping to have to do it.. but that will
work.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/Ld0sFBSIFnwJ.
To post to this
Actually, one more question to spawn off this... Is there a way in my
nagios/repo class to say if you have this class go ahead and assign
yourself to my new services:httpd class? Can that be done with
inheritance? I have never used inheritance so I am not sure.
On Thursday, June 21, 2012
On Thursday, June 21, 2012 7:24:59 AM UTC-7, trey85stang wrote:
Actually, one more question to spawn off this... Is there a way in my
nagios/repo class to say if you have this class go ahead and assign
yourself to my new services:httpd class? Can that be done with
inheritance? I
Hey All,
Im running into a road block with a server that is going to to be
multi role.
Example:
I want to run a nagios server and a repo server on one box.
My nagios manifest has two services defined:
class nagios::server {
...
service { nagios:
ensure = running,
...
}
service