Hello all,
Based on this post from July :
http://www.mailinglistarchive.com/html/puppet-users@googlegroups.com/2010-07/msg00124.html
The OP has this snippet running on an RHEL system :
file { "network":
...
notify => Service[network]
}
service { network:
ensure => "running",
hasstatus => "true",
hasrestart => "true",
restart => "/etc/init.d/network restart",
}
Clearly the idea is to trigger a network restart if the given file
changes ; however, "network" isn't really a service, it's an init
script, which means that it's not generally "running".
On a given CentOS machine, ralsh says :
$ ralsh service network
service { 'network':
enable => 'true',
ensure => 'running'
}
Which is what we want, but i'm curious as to _why_ this is so, given
(again) that we're talking about an init script, and not a particular
service that sits in memory. Granted, the effects of the script can be
known - is puppet smart enough to figure out what effect "service
network *" ultimately has on the system, or is this sort of a happy
accident, or yet something else entirely ?
Thank you.
--
Daniel Maher <dma 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.
