You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Vaggelis Atlidakis (JIRA)" <ji...@apache.org> on 2013/03/11 11:07:12 UTC
[jira] [Updated] (APLO-305) Wrong exist status codes in the init
scripts!
[ https://issues.apache.org/jira/browse/APLO-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vaggelis Atlidakis updated APLO-305:
------------------------------------
Description:
Hello,
I would like to report that the init.d scripts for the apollo broker returns incorrect exit codes.
{noformat}
# service apollo-mcollect-broker status; echo $?
apollo-mcollect-broker is running (23403)
0
{noformat}
According to: http://fedoraproject.org/wiki/Packaging:SysVInitScript#Required_Actions
the return code when the service is not running should be: 3
Best Regards,
--
aV
was:
Hello,
Hello,
I would like to report that the init.d scripts for the apollo broker returns incorrect exit codes.
{code}
# service apollo-mcollect-broker status; echo $?
apollo-mcollect-broker is running (23403)
0
{code}
According to: http://fedoraproject.org/wiki/Packaging:SysVInitScript#Required_Actions
the return code when the service is not running should be: 3
Best Regards,
--
aV
> Wrong exist status codes in the init scripts!
> ---------------------------------------------
>
> Key: APLO-305
> URL: https://issues.apache.org/jira/browse/APLO-305
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Reporter: Vaggelis Atlidakis
>
> Hello,
> I would like to report that the init.d scripts for the apollo broker returns incorrect exit codes.
> {noformat}
> # service apollo-mcollect-broker status; echo $?
> apollo-mcollect-broker is running (23403)
> 0
> {noformat}
> According to: http://fedoraproject.org/wiki/Packaging:SysVInitScript#Required_Actions
> the return code when the service is not running should be: 3
> Best Regards,
> --
> aV
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira