Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-2839

Working paths are hard-coded in bin/ scripts and log4j xml

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.5.0.final
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Some working paths are hard-coded, for example

      1. bin/ignite.sh:
        RESTART_SUCCESS_FILE="${IGNITE_HOME}/work/ignite_success_${RANDOM_NUMBER}"
        
      2. config/ignite-log4j.xml, config/ignite-log4j2.xml
        <param name="File" value="${IGNITE_HOME}/work/log/ignite.log"/>
        

        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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              knivit knivit
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: