Description of problem:

When checking the status of a service the init script of shinken components uses the status function in a way that returns wrong results.

Version-Release number of selected component (if applicable):

shinken-1.4.1-1.el6.noarch
shinken-arbiter-1.4.1-1.el6.noarch
shinken-reactionner-1.4.1-1.el6.noarch
shinken-scheduler-1.4.1-1.el6.noarch
shinken-broker-1.4.1-1.el6.noarch
shinken-poller-1.4.1-1.el6.noarch
shinken-receiver-1.4.1-1.el6.noarch

How reproducible:

Install shinken and run service <component> status

Steps to Reproduce:

1. yum install shinken shinken-{arbiter,broker,poller,reactionner,receiver,scheduler}
2. service shinken-poller status

Actual results:

# service shinken-poller status
shinken-poller dead but subsys locked

Expected results:

[root shinken]# service shinken-poller status
shinken-poller (pid  1360) is running...


The process is running so I expected to see the parent.

# ps xaf | grep poller
 1360 ?        S      0:00 python /usr/sbin/shinken-poller -d -c /etc/shinken/pollerd.ini
 1365 ?        S      0:00  \_ python /usr/sbin/shinken-poller -d -c /etc/shinken/pollerd.ini

Additional info:

Patching this problem is trivial. The only action needed is using the -p flag in the status function. If we take /etc/init.d/shinken-poller as an example:

85c85
<         status $prog
---
>         status -p $pidfile $prog