You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "knivit (JIRA)" <ji...@apache.org> on 2016/03/15 21:05:33 UTC

[jira] [Created] (IGNITE-2839) Working paths are hard-coded in bin/ scripts and log4j xml

knivit created IGNITE-2839:
------------------------------

             Summary: Working paths are hard-coded in bin/ scripts and log4j xml
                 Key: IGNITE-2839
                 URL: https://issues.apache.org/jira/browse/IGNITE-2839
             Project: Ignite
          Issue Type: Bug
    Affects Versions: 1.5.0.final
            Reporter: knivit
            Priority: Minor


Some working paths are hard-coded, for example
# bin/ignite.sh:
{code}
RESTART_SUCCESS_FILE="${IGNITE_HOME}/work/ignite_success_${RANDOM_NUMBER}"
{code}
# config/ignite-log4j.xml, config/ignite-log4j2.xml
{code}
<param name="File" value="${IGNITE_HOME}/work/log/ignite.log"/>
{code}
Usually an installation (i.e. $IGNITE_HOME) folder is read-only for non-root users so Ignite won't start.
Need to introduce IGNITE_WORK_DIR, IGNITE_LOG_DIR variables.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)