Re: question about cassandra.in.sh

2011-08-25 Thread Koert Kuipers
hey eric, the one thing i do not agree that it is the element of least surprise. i would argue that the default behavior for *nix appplications is that they find out what their home directory is and operate relative to that. something like: script_dir=$(dirname $(readlink -f ${BASH_SOURCE[0]}))

Re: question about cassandra.in.sh

2011-08-25 Thread Eric Evans
On Thu, Aug 25, 2011 at 10:13 AM, Koert Kuipers ko...@tresata.com wrote: hey eric, the one thing i do not agree that it is the element of least surprise. i would argue that the default behavior for *nix appplications is that they find out what their home directory is and operate relative to

question about cassandra.in.sh

2011-08-24 Thread Koert Kuipers
i have an existing cassandra instance on my machine, it came with brisk and lives in /usr/share/brisk/cassandra. it also created /usr/share/cassandra/ cassandra.in.sh now i wanted to run another instance of cassandra (i needed a 0.7 version for compatibility reasons), so i downloaded it from

Re: question about cassandra.in.sh

2011-08-24 Thread Eric Evans
On Wed, Aug 24, 2011 at 1:28 PM, Koert Kuipers ko...@tresata.com wrote: my problem is that the scripts for my cassandra 0.7 instance don't work properly. the problem lies in the code snippets below. when i run the scripts they source /usr/share/cassandra/cassandra.in.sh, which has the wrong