Hi,
good question. The module's documentation does not readily offer a
way to cleanly restart a service.
However, looking at the source, it quickly becomes clear that
tomcat::service does in fact wrap a service resource.
https://github.com/puppetlabs/puppetlabs-tomcat/blob/master/manifests/service.pp#L126-134
The nature of this resource depends on the parameters, apparently.
But most (if not all) service providers will initiate a restart of
the service if the resource receives a signal. You can enforce
this by adding, say, a notify resource to your manifest.
notify { 'restarting tomcat': notify =>
Tomcat::Service['default'] }
A little confusing I guess - the notify type is not designed to
enforce events. It actually notifies you with the given message
('restarting tomcat'). But since this is a sync action, it will
also send an event to the service, thanks to the notify parameter.
HTH,
Felix
On 10/15/2014 09:07 AM, Richard wrote: