[ 
https://issues.apache.org/jira/browse/TRAFODION-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056151#comment-16056151
 ] 

ASF GitHub Bot commented on TRAFODION-2626:
-------------------------------------------

GitHub user svarnau opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/1129

    [TRAFODION-2626] Make conf directory location configurable

    For user configuration files, use TRAF_CONF variable instead of
    TRAF_HOME/conf.
    
    In cases where we want to install config files to an alternate location
    (say TRAF_CONF=/etc/trafodion), we would copy all the default files from
    TRAF_HOME/conf to TRAF_CONF and make modifications in the TRAF_CONF 
location.
    
    In development workspace, both locations can be one in the same.
    
    One case where I left the original path is for the install_features file.
    This file identifies version features and is not a user-configurable file.
    Hence it should be read from the TRAF_HOME/conf location.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/svarnau/incubator-trafodion traf2626_conf

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/1129.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1129
    
----
commit b0dcf05aa2b2580700b214dfb12543ff0a1102df
Author: Steve Varnau <[email protected]>
Date:   2017-06-20T16:27:44Z

    [TRAFODION-2626] Make conf directory location configurable
    
    For user configuration files, use TRAF_CONF variable instead of
    TRAF_HOME/conf.
    
    In cases where we want to install config files to an alternate location
    (say TRAF_CONF=/etc/trafodion), we would copy all the default files from
    TRAF_HOME/conf to TRAF_CONF and make modifications in the TRAF_CONF 
location.
    
    In development workspace, both locations can be one in the same.
    
    One case where I left the original path is for the install_features file.
    This file identifies version features and is not a user-configurable file.
    Hence it should be read from the TRAF_HOME/conf location.

----


> Log/Conf seperation from TRAF_HOME
> ----------------------------------
>
>                 Key: TRAFODION-2626
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2626
>             Project: Apache Trafodion
>          Issue Type: Improvement
>            Reporter: Steve Varnau
>            Assignee: Steve Varnau
>
> Dynamic files (configuration and log files) should be separated from 
> delivered software.  It should be possible to have config files in /etc, log 
> files in /var/log, and runtime software in /usr or /opt.
> First step is to have conf and log variables separate from TRAF_HOME.
> Proposal is to add following variables which can be used either in 
> development or production environments to specify locations:
> TRAF_HOME - executable / read-only locations
> TRAF_CONF - configuration files location
> TRAF_LOG - ouput logging location
> TRAF_VAR - temporary / status files (node-local pid files, lock files, etc)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to