On Wed, Feb 8, 2012 at 15:34, Aaron Grewell <aaron.grew...@gmail.com> wrote:
> I've got a bit of a head-scratcher here, though I'm sure it must be > something small. I'm trying to enable a service for next boot without > starting it. That usually "just works" but for some reason this time > around it isn't. The node keeps trying to start the service which > will always fail because it requires a reboot in order to enable the > necessary kernel parameters. How do I make Puppet stop trying to > start the service? You can't: if you tell Puppet to ensure the service is running, it will try to start it every time it finds it "out of compliance". There is no standard way for the service to communicate that "a reboot is required" either. Your best bet might be one of: 1. Don't ensure that is running with Puppet, use something else that is more tolerant or silent. 2. Have an exec that checks those kernel parameters for kdump and automatically reboots. Obviously 2 has ... some risks. :) -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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.
