[
https://issues.apache.org/jira/browse/CASSANDRA-12748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952955#comment-15952955
]
Murukesh Mohanan commented on CASSANDRA-12748:
----------------------------------------------
{{env}} has an {{-i}} option which allows us to run a command with a clean
environment ([this is specified by
POSIX|http://pubs.opengroup.org/onlinepubs/9699919799/utilities/env.html], so
should be portable). Since we don't know what environment variables can affect
commands invoked in our scripts, should we consider re-executing the script
with {{env -i var1="$var1" var2="$var2" ...}} where {{var1}}, {{var2}}, etc.
are explicitly listed out as only those variables of interest to us?
As an example, [Ubuntu's {{service}}
command|http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/sysvinit/trusty/view/head:/debian/service/service#L102]
calls init scripts with a clean environment, retaining only the {{LANG}},
{{PATH}} and {{TERM}} variables. Of course, we would need to retain more.
> Cassandra fails to start up if GREP_COLOR is set
> ------------------------------------------------
>
> Key: CASSANDRA-12748
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12748
> Project: Cassandra
> Issue Type: Bug
> Reporter: Benjamin Roth
> Priority: Minor
>
> If env var GREP_COLOR is set, CS fails to start as startup command then
> contains ANSI codes.
> See cassandra-env.sh when JVM_OPTS_FILE is parsed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
