falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandeep samudrala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1649) 777 permission issue on staging directory and on subdirectory
Date Tue, 08 Dec 2015 19:09:11 GMT

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

sandeep samudrala commented on FALCON-1649:
-------------------------------------------

Just to add to my pervious comment, Have all the directories owned by falcon and only the
logs where the log mover stores the logs can be made 777 so as to let the user who scheduled
the entity can write the logs to the respective directory in the staging.


>  777 permission issue on staging directory and on subdirectory
> --------------------------------------------------------------
>
>                 Key: FALCON-1649
>                 URL: https://issues.apache.org/jira/browse/FALCON-1649
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: sandeep samudrala
>
> The conversation from https://issues.apache.org/jira/browse/FALCON-1647 have been copied
to the below comments.
> This jira will capture the details regarding how the staging directory should be presented
as having 777 as permission is a security issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message