ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-2839) Working paths are hard-coded in bin/ scripts and log4j xml
Date Mon, 10 Jul 2017 07:08:07 GMT

     [ 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.1)
                   2.2

> 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.2
>
>
> 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.4.14#64029)

Mime
View raw message