Description of problem: Running "/sbin/service jabberd status" returns 0 whether jabberd is running or not, which breaks automated admin scripts. Version-Release number of selected component (if applicable): jabberd-2.0-0.s11.9.fc5 How reproducible: Always. Steps to Reproduce: [root@host ~]# service jabberd status router (pid 25257) is running... resolver (pid 25287) is running... sm (pid 25317) is running... c2s (pid 25347) is running... s2s (pid 25378) is running... [root@host ~]# echo $? 0 [root@host ~]# service jabberd stop Terminating jabberd processes ... Stopping router: [ OK ] Stopping resolver: [ OK ] Stopping sm: [ OK ] Stopping c2s: [ OK ] Stopping s2s: [ OK ] [root@host ~]# service jabberd status router is stopped resolver is stopped sm is stopped c2s is stopped s2s is stopped [root@host ~]# echo $? 0 Actual results: The return status of "/sbin/status jabberd status" is 0 even when jabberd is stopped. Expected results: The return status should be 3 if jabberd is not running. Additional info: The rhstatus() function in /etc/init.d/jabberd should store and return $? just as does the preceding reload() function. This is the same problem as described for openldap in bug 63241.
Fixed for FC5 and FC6 branches.