[jira] [Issue Comment Deleted] (CASSANDRA-6399) debian init script removes PID despite the return status

["Peter Halliday (JIRA)" <ji...@apache.org>]

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

Peter Halliday updated CASSANDRA-6399:
--------------------------------------

    Comment: was deleted

(was: Also, start-stop-daemon doesn't block until it's stopped.  With the current command line.  So it returns success as soon as the signal was sent.  This could lead to situations if the signal was ignored for some reason that it was read as a success.  I suggest adding the --retry flag, which can have a timeout added as well if desired.)

> debian init script removes PID despite the return status
> --------------------------------------------------------
>
>                 Key: CASSANDRA-6399
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6399
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Peter Halliday
>
> If there's an error in running service cassandra stop it can return a non-successful code, but the do_stop() removes the PID file anyway.  This shows then via service cassandra status, that Cassandra is stopped, even though it's still running in the process list.



--
This message was sent by Atlassian JIRA
(v6.1#6144)