You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/04/10 10:57:41 UTC
[jira] [Updated] (IGNITE-2839) Working paths are hard-coded in bin/
scripts and log4j xml
[ https://issues.apache.org/jira/browse/IGNITE-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-2839:
------------------------------------
Fix Version/s: (was: 2.0)
2.1
> 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
> Labels: community
> Fix For: 2.1
>
>
> 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.15#6346)