cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4271) Exit status of bin/cassandra without -f is wrong
Date Mon, 23 Jul 2012 15:09:35 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-4271:
--------------------------------------

    Reviewer: brandon.williams  (was: thobbs)
    
> Exit status of bin/cassandra without -f is wrong
> ------------------------------------------------
>
>                 Key: CASSANDRA-4271
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4271
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: paul cannon
>            Priority: Minor
>             Fix For: 1.1.3
>
>         Attachments: 0001-startup-script-returns-0-after-backgrounding.patch
>
>
> The launch_service() function returns {{$?}} after exec'ing java, and the script then
exits with that same status.
> The problem is that we do a {{[ ! -z "$pidpath"] && ...}} conditional statment
after exec'ing when the foreground flag isn't set.  The value of {{$?}} then depends on that
conditional and the statement, typically returning 1, because {{$pidpath}} isn't set.  So,
even if everything appears to execute normally, you will get an exit status of 1 for the whole
script.
> I suspect the right thing to do is just return 0 when backgrounding.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message