On Sun, Feb 20, 2011 at 10:47 PM, Daniel Pittman <[email protected]> wrote: > On Sun, Feb 20, 2011 at 18:44, Tim Connors <[email protected]> wrote: >> On Jan 23, 5:48 pm, martin f krafft <[email protected]> wrote: >>> also sprach Daniel Pittman <[email protected]> [2011.01.20.0420 +0100]: >>> >>> > Is the enable/disable feature available in lenny, and etch? I didn't >>> > think it was present before sid, and I don't know we want to break >>> > older Debian platforms in newer puppet releases. Perhaps we can probe >>> > update-rc.d for a version number and use this mode when possible? >>> >>> It was introduced with sysv-rc 2.86.ds1-62, after the lenny release. >>> >>> Since a newer puppet release will not be packaged for older Debian >>> versions, I do not see the danger of it breaking, really. >> >> Unless I'm misunderstanding this, the problem is relevant to those of >> us who may have squeeze on the puppetmaster and hence have up-to-date >> rules on whether to run "update-rc.d stop" or "update-rc.d >> disable"[1], but some of the clients are squeeze and some are still >> lenny. Puppet needs to know whether to run stop or disable based on >> the version of update-rc.d installed on the client. > > No, this decision is made entirely on the client side; the server just > sends instructions at the level of "service X should be enabled", and > trusts the agent to work out the details. The problem is that we need > to use the right method based on the client configuration and all.
We should have enough information from the base facts about the OS point release versions to make this decision within the provider. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
