Issue #3936 has been updated by Steven Lumos.
Would that mean ensure => running would silently fail? Won't this break people who use policy-rc.d to prevent starting daemons during package install (before they've been configured), but want puppet to start them (after their config is installed)? ---------------------------------------- Feature #3936: Puppet should start/stop services using invoke-rc.d for debian https://projects.puppetlabs.com/issues/3936 Author: Darin Tay Status: Accepted Priority: Normal Assignee: Category: service Target version: Affected Puppet version: 0.25.4 Keywords: Branch: Though puppet uses invoke-rc.d for debian services to determine whether a service is enabled, it starts/stops services by invoking the init scripts directly. It should instead use invoke-rc.d for starting/stopping, so as to support policy enforcement. We ran into an issue where a system was using policy-rc.d to prevent services from starting up. This worked fine, until we started having services that Puppet was trying to restart; since Puppet invokes the init scripts directly, policy-rc.d is ignored. On systems with Upstart-based init, you may also want to consider using Upstart-specific methods for starting/stopping services, though I'm not very familiar with it and I'm not sure what benefits/drawbacks that may have. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
