Bill Proud: > I would have thought that the simplest solution would be to not use a > service at all but instead notify an exec from the file resource for > the configuration. The exec could run a simple script that checks if > the application is running and restarts it if it is.
The trouble with execs is that they're so open-ended that a "puppet agent -t --noop" can't predict what will happen after one occurs. With a service it can at least assume that the refresh happened successfully and any notifications can trickle onward from there. With an exec it just says "um, except now we're noop. You're on your own from here, mate." It's like that old usenet rant about "given what you just did, it's perfectly within spec for the compiler to make demons fly out your nose!" Anything at all could happen! I feel like execs are something of a misfeature, but I'd be hard pressed to figure out how to live completely without them. I'm glad I have them available to do things like generate quick unique ssl snakeoil certificates or ssh keys, but I would hate to rely on them for something as central as the service resource. -- Though the great song return no more There's keen delight in what we have: The rattle of pebbles on the shore Under the receding wave. -- W. B. Yeats -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
