On Jun 14, 2012, at 12:22 AM, Felix Frank wrote: > What you're suggesting is a differentiation that has never existed in > this context (afaik). I'm not sure I feel good about opening this door - > I can easily see it become a gateway for lots of unintended effects to > trip users up.
How so? The variable would allow the user to be explicit. As it stands now, I suspect most people would be surprised. I am also very disconcerted about the issues involved in setting up new files. You can never, ever, EVER change the mode of a newly installed file without restarting services on all existing machines. That doesn't make any sense. > As for your original problem, I don't see a good way of safeguarding > against this in puppet. Personally, I refrain from having puppet restart > services unless they are quite "safe", i.e. unlikely to stop working for That's good for you, not good for us. Having the variable would allow both of us to meet our needs, whereas not having the variable means that we must work your way. -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. -- 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.
