From bb19dea3912610c652d55c1de00c8e8e9f7698b5 Mon Sep 17 00:00:00 2001 From: Ben Hughes Date: Fri, 8 Apr 2011 11:33:45 +1000 Subject: (#7018) explain internals better in service provider documentation Add explicit reasoning for hasstatus in the documentation with certain "virtual" services. Just to clear up why notify => Service["something_virtual"] requires hasstatus defining for it to function. --- lib/puppet/type/service.rb | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/lib/puppet/type/service.rb b/lib/puppet/type/service.rb index 0d09c3d5d..8387dd52d 100644 --- a/lib/puppet/type/service.rb +++ b/lib/puppet/type/service.rb @@ -97,7 +97,10 @@ module Puppet `status` parameter). If you do not specify anything, then the service name will be - looked for in the process table." + looked for in the process table. Be aware that 'virtual' init + scripts such as networking, that don't have something in the + process table need this functionality to be used with + notify/require trigger actions." newvalues(:true, :false) end -- cgit