cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6101) Debian init script broken
Date Mon, 30 Sep 2013 16:18:26 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781978#comment-13781978
] 

Eric Evans commented on CASSANDRA-6101:
---------------------------------------

Good catch Anton.

I've applied the fix to ensure that the PID directory is created, but I think we can go a
bit further with the classpath.

That function is a throwback to {{jsvc}} and duplicates the classpath construction we do elsewhere.
 I've attached [6101-classpath.patch|https://issues.apache.org/jira/secure/attachment/12605920/6101-classpath.patch]
which eliminates that function and uses {{EXTRA_CLASSPATH}} instead.

Can you give this a whirl and see if it (still) fixes the issues you were seeing?

> Debian init script broken
> -------------------------
>
>                 Key: CASSANDRA-6101
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6101
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Anton Winter
>            Assignee: Eric Evans
>            Priority: Minor
>         Attachments: 6101-classpath.patch, 6101.txt
>
>
> The debian init script released in 2.0.1 contains 2 issues:
> # The pidfile directory is not created if it doesn't already exist.
> # Classpath not exported to the start-stop-daemon.
> These lead to the init script not picking up jna.jar, or anything from the debian EXTRA_CLASSPATH
environment variable, and the init script not being able to stop/restart Cassandra.



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

Mime
View raw message