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/14 17:24:14 UTC

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=13602391#comment-13602391 ] 

Vaggelis Atlidakis edited comment on APLO-305 at 3/14/13 4:24 PM:
------------------------------------------------------------------

Thanks for fixing this!
Can you also add to the init script a commented line to support chkconfig?
It would be nice for as to enable the broker came up running following a reboot!

Best Regards,
--
aV
                
      was (Author: vatlidak):
    Thanks for fixing this!
Can you also add to the init script a commented line to support chkconfig! 
It would be nice for as to enable the broker came up running following a reboot!

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-cli, apollo-distro
>    Affects Versions: 1.6
>            Reporter: Vaggelis Atlidakis
>            Assignee: Hiram Chirino
>             Fix For: 1.7
>
>
> Hello,
> I would like to report that the init.d scripts for the apollo broker returns incorrect exit codes.
> # service apollo-mcollect-broker status; echo $?
> apollo-mcollect-broker is running (23403)
> 0
> 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