cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Murukesh Mohanan"<>
Subject Re: Three scripts needed to run the server, Why?
Date Tue, 11 Jul 2017 14:24:40 GMT

The bin/cassandra script has an explanation (

# As a convenience, a fragment of shell is sourced in order to set one or
# more of these variables. This so-called `include' can be placed in a 
# number of locations and will be searched for in order. The lowest 
# priority search path is the same directory as the startup script, and
# since this is the location of the sample in the project tree, it should
# almost work Out Of The Box.
# Any serious use-case though will likely require customization of the
# include. For production installations, it is recommended that you copy
# the sample to one of /usr/share/cassandra/,
# /usr/local/share/cassandra/, or 
# /opt/cassandra/ and make your modifications there.
# If you would rather configure startup entirely from the environment, you
# can disable the include by exporting an empty CASSANDRA_INCLUDE, or by 
# ensuring that no include files exist in the aforementioned search list.
# Be aware that you will be entirely responsible for populating the needed
# environment variables.

You can use just a single environment file, if you so wish.

On 2017-07-11 23:08 (+0900), Tomas Repik <> wrote: 
> Greetings,
> I've been working with Cassandra for more than a year but I still wonder about one thing:
> To run the server there is a bash script (cassandra) which uses another script (
which uses yet another bash script (
> What is the reason behind this?
> Why there is not only a single file setting up the environment and running the server?

> Thanks for your answers
> Tomas
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message