Hey All, I can see in the type reference under service it has restart, stop, start etc. But is there a way to issue a /etc/init.d/daemon reload ? but still have the restart available if needed Cheers Brendan Brendan Beveridge Managed Services Consultant Direct | 02 8235 9593 Mobile | 0434 077 934 Email | Brendan.Beveridge@brennanit.com.au "Brennan IT lands major IT&T Outsourcing Deals." Click here to find out more. Sydney - Melbourne - Brisbane - Adelaide - Perth - Canberra | Phone | 02 8235 9595 | Fax | 02 8235 9594 | Web : http://www.brennanit.com.au _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Dec 20, 2006, at 9:54 PM, Brendan Beveridge wrote:> Hey All, > > I can see in the type reference under service it has restart, stop, > start etc. > > But is there a way to issue a /etc/init.d/daemon reload ? but still > have the restart available if neededPuppet services don''t currently differentiate between restart and reload, but it would be trivial to add it. Please add it as a feature request if it''s something that you want. It will have to include selectivity so that you can choose which method will be used to restart a service in respose to changes in dependencies. -- The Roman Rule The one who says it cannot be done should never interrupt the one who is doing it. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
After looking into it further, i dont think its really needed in the
service type (because your ensuring its running not reloading it for
config change.
The way i am now doing daemon reloads for config updates is as follows:
# syslog-ng for central logging
package { syslog-ng: ensure => latest }
service { syslog-ng: ensure => true, provider =>
$operatingsystem, enable => true }
configfile { "/etc/syslog-ng/syslog-ng.conf": source =>
"/syslog-ng/syslog-ng.conf", mode => 644 }
exec { "/etc/init.d/syslog-ng reload": subscribe =>
file["/etc/syslog-ng/syslog-ng.conf"], refreshonly => true }
Cheers
B
Luke Kanies wrote:> On Dec 20, 2006, at 9:54 PM, Brendan Beveridge wrote:
>
>
>> Hey All,
>>
>> I can see in the type reference under service it has restart, stop,
>> start etc.
>>
>> But is there a way to issue a /etc/init.d/daemon reload ? but still
>> have the restart available if needed
>>
>
> Puppet services don''t currently differentiate between restart and
> reload, but it would be trivial to add it. Please add it as a
> feature request if it''s something that you want. It will have to
> include selectivity so that you can choose which method will be used
> to restart a service in respose to changes in dependencies.
>
> --
> The Roman Rule
> The one who says it cannot be done should never interrupt the
> one who is doing it.
> ---------------------------------------------------------------------
> Luke Kanies | http://reductivelabs.com | http://madstop.com
>
>
> _______________________________________________
> Puppet-users mailing list
> Puppet-users@madstop.com
> https://mail.madstop.com/mailman/listinfo/puppet-users
>
On Dec 21, 2006, at 3:47 PM, Brendan Beveridge wrote:> After looking into it further, i dont think its really needed in the > service type (because your ensuring its running not reloading it for > config change.If a service resource is subscribed to another resource (such as a package or file) and that other resource changes, then Puppet will restart the service for you. This is the difference between subscribe and require -- subscribe results in a restart, require just handles ordering. You should not need to have the extra exec. At the least, I know you don''t need it if you want to restart; if you wanted to reload instead, then at this point you would need the exec but the service type should be extended to support either.> The way i am now doing daemon reloads for config updates is as > follows: > # syslog-ng for central logging > package { syslog-ng: ensure => latest } > service { syslog-ng: ensure => true, provider => > $operatingsystem, enable => true }The service type should generally automatically choose the appropriate provider, btw; you shouldn''t need to specify it. -- Some people are afraid of heights. I''m afraid of widths. -- Stephen Wright --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com