You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Alejandro Abdelnur (Created) (JIRA)" <ji...@apache.org> on 2012/03/14 21:38:42 UTC

[jira] [Created] (BIGTOP-451) ooziedb.sh script should run as the unix user that runs oozie server

ooziedb.sh script should run as the unix user that runs oozie server
--------------------------------------------------------------------

                 Key: BIGTOP-451
                 URL: https://issues.apache.org/jira/browse/BIGTOP-451
             Project: Bigtop
          Issue Type: Improvement
          Components: General
    Affects Versions: 0.3.0
            Reporter: Alejandro Abdelnur
             Fix For: 0.3.0


Currently the ooziedb.sh script runs as the user that invokes it.

If this user is root, this creates file permission issues with the log files and (if the db used is derby) with the derby DB files. These files will be owned by root and the oozie user running the server won't have write permissions to them.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (BIGTOP-451) ooziedb.sh script should run as the unix user that runs oozie server

Posted by "Alejandro Abdelnur (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229594#comment-13229594 ] 

Alejandro Abdelnur commented on BIGTOP-451:
-------------------------------------------

one option is to modify the the ooziedb.sh script to do a 'sudo -u oozie' when invoking java
                
> ooziedb.sh script should run as the unix user that runs oozie server
> --------------------------------------------------------------------
>
>                 Key: BIGTOP-451
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-451
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: General
>    Affects Versions: 0.3.0
>            Reporter: Alejandro Abdelnur
>             Fix For: 0.3.0
>
>
> Currently the ooziedb.sh script runs as the user that invokes it.
> If this user is root, this creates file permission issues with the log files and (if the db used is derby) with the derby DB files. These files will be owned by root and the oozie user running the server won't have write permissions to them.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (BIGTOP-451) ooziedb.sh script should run as the unix user that runs oozie server

Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik updated BIGTOP-451:
------------------------------------

    Fix Version/s:     (was: 0.3.0)
                   0.4.0
    
> ooziedb.sh script should run as the unix user that runs oozie server
> --------------------------------------------------------------------
>
>                 Key: BIGTOP-451
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-451
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: General
>    Affects Versions: 0.3.0
>            Reporter: Alejandro Abdelnur
>             Fix For: 0.4.0
>
>
> Currently the ooziedb.sh script runs as the user that invokes it.
> If this user is root, this creates file permission issues with the log files and (if the db used is derby) with the derby DB files. These files will be owned by root and the oozie user running the server won't have write permissions to them.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira