You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:47:09 UTC

[jira] [Commented] (OOZIE-180) GH-189: make ENV setting flexible to allow Unix standard layout for conf/logs/data/tmp

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

Hadoop QA commented on OOZIE-180:
---------------------------------

tucu00 remarked:
Closed by e4a5a398e451b5db595881466c7516b681589a43 make ENV setting flexible to allow Unix standard layout for conf/logs/data/tmp

making scripts more robust:

Adding check that the owner of the setup is the one doing start/stop/setup. this will avoid
permissions problems in log/working files as Oozie cannot be started with other user.

Configuring embedded tomcat to use/check PID file to avoid double starts.

Using oozie-env.sh files in bin/ and conf/ for sourcing environment settings that specify
location of conf/logs/data/tmp files. By default everything is self-contained in the
Oozie installation directory.

Simplifying loading of value to be just system properties (no ENV vars). Start up script seeds
all the ENV vars as system properties.

Normalizing then name/case of the Java system properties

> GH-189: make ENV setting flexible to allow Unix standard layout for conf/logs/data/tmp
> --------------------------------------------------------------------------------------
>
>                 Key: OOZIE-180
>                 URL: https://issues.apache.org/jira/browse/OOZIE-180
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> as part of this oozie logs should go to logs/ and tomcat logs to oozie-server/logs/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira