Jira (PUP-2771) service status field behaves exactly other way than documentation

[Stefan Schulte (JIRA)]

Title: Message Title

Stefan Schulte commented on an issue   Re: service status field behaves exactly other way than documentation I cannot reproduce the issue here The following snippet will not start the service (/bin/true returns 0) service { 'my-service': ensure => running, hasstatus => false, status => "/bin/true" } The following snippet will start the service (/bin/false always returns 1) service { 'my-service': ensure => running, hasstatus => false, status => "/bin/false" } Is it possible that your status command does always return the grep output so you will always end up with at least one line? % ps fax | grep my-service 2530 pts/0 S+ 0:00 \_ grep --colour=auto my-service Add Comment   Puppet / PUP-2771 service status field behaves exactly other way than documentation The documentation states at http://docs.puppetlabs.com/references/latest/type.html#service-attribute-status {quote} status Specify a status command manually. This command must return 0 if the service is running and a nonzero value otherwise. {quote} But in fact it is *exactly the other way round*. For a non running service to be started the stat... 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.