Unfortunately I am unable to reproduce this except outside the target virtualized environment, currently unavailable due to resource concerns.
So far courier-imap and courier-pop restart as they should elsewhere. On Tue, Jan 17, 2012 at 05:34:06PM +0100, Felix Frank wrote: > On 01/13/2012 07:08 PM, Christopher Wood wrote: > > The courier-imap (and courier-pop) services on my lab VMs don't actually > > get refreshed after puppet drops in the config files. I suspect it's > > something about the lack of /etc/init.d/courier-pop status, coupled with > > that I have the wrong pattern. Could anybody offer any hints of what I'm > > doing wrong, or what would be the correct pattern for these processes? > > Are the services started via initscript at all? > > If not, have a look at the binary parameter to the service type: > http://docs.puppetlabs.com/references/stable/type.html#service > > Otherwise the hasrestart parameter may help you out. > > To test things, simply manipulate the config file on your agent node > (slightly) and run puppet (you may want to dry --verbose and --debug > when you do). Watch out for what the agent has to say about your service. > > HTH, > Felix > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@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. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
