Jira (PUP-1370) when init scripts have been ported to upstart puppet does not detect service that are not working

[Adrien Thebo (JIRA)]

Title: Message Title

Adrien Thebo commented on an issue   Re: when init scripts have been ported to upstart puppet does not detect service that are not working The upstart provider was set as the default on Ubuntu in commit dc3bb9fb2546eba61d57f61994e453cd8780e5d1, which was released in 2.7.14. Since upstart can correctly handle this service and will be the default in Ubuntu I think this is solved. I'm going to mark this as needs information so that we can get additional verification of this. If this doesn't see any comments in a month or so I think we can assume this is resolved and close it. Add Comment   Puppet / PUP-1370 when init scripts have been ported to upstart puppet does not detect service that are not working I do not believe that this is a regresson and it was observed on 2.7.12 when a init script has been disabled, the following message is printed to stdout: <pre> root@db:~# /etc/init.d/mysql status Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service mysql status Since the script you are attempting to i... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.