[ https://issues.apache.org/jira/browse/CASSANDRA-13148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085526#comment-16085526 ]
Murukesh Mohanan commented on CASSANDRA-13148: ---------------------------------------------- [~hoall] Carrying over the discussion from CASSANDRA-13436, if you want to start services when Cassandra starts *listening*, you need a slightly more complex setup. See [this thread on the systemd-devel mailing list|https://lists.freedesktop.org/archives/systemd-devel/2015-May/032278.html] or this [Unix & Linux Stack Exchange post|https://unix.stackexchange.com/q/241962/70524] (both of which coincidentally happen to be about Cassandra!), for example. The consensus seems to be essentially: 1. Use an {{ExecStartPost}} command which waits for the relevant port to start listening, or 2. Use an additional service which waits for the relevant port to start listening and depend on it The latter is more flexible, since you can start services dependent on the various ports (JMX, CQL, etc.) independently. > Systemd support for RPM > ----------------------- > > Key: CASSANDRA-13148 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13148 > Project: Cassandra > Issue Type: New Feature > Components: Packaging > Reporter: Spiros Ioannou > > Since CASSANDRA-12967 will provide an RPM file, it would be greatly > beneficial if this package included systemd startup unit configuration > instead of the current traditional init-based, which misbehaves on > RHEL7/CentOS7. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org