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

Puspendu Banerjee edited comment on NIFI-1461 at 2/10/16 7:40 AM:
------------------------------------------------------------------

I could not follow:
How bootstrap.conf [root_owns] become owned by root:root?

Here is what I am seeing:

[root@node00 ~]# ll /opt/nifi/nifi-0.4.2-SNAPSHOT/conf/
total 40
-rw-r-----. 1 nifi nifi 2129 Feb  7 02:32 authority-providers.xml
-rw-r-----. 1 nifi nifi 2530 Feb  7 02:32 authorized-users.xml
-rw-r-----. 1 nifi nifi 3241 Feb  7 02:32 bootstrap.conf
-rw-r-----. 1 nifi nifi 2119 Feb  7 02:32 bootstrap-notification-services.xml
-rw-r-----. 1 nifi nifi 7226 Feb  7 02:32 logback.xml
-rw-r-----. 1 nifi nifi 5073 Feb  7 02:32 login-identity-providers.xml
-rw-r-----. 1 nifi nifi 7565 Feb  7 02:32 nifi.properties


was (Author: [email protected]):
I could not follow:
How bootstrap.conf [root_owns] become owned by root:root?


> RPM should create nifi user and give it access to the /opt/nifi and 
> subdirectories
> ----------------------------------------------------------------------------------
>
>                 Key: NIFI-1461
>                 URL: https://issues.apache.org/jira/browse/NIFI-1461
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 0.4.1
>            Reporter: Andre
>            Assignee: Tony Kurc
>              Labels: rpm
>             Fix For: 0.5.0
>
>         Attachments: 
> 0001-NIFI-1461-This-closes-204.-Implemented-RPM-before-af.patch, 
> 0002-NIFI-1461-added-run.as-filtered-property-for-RPM-and.patch, nifi.spec, 
> nifi.spec
>
>
> currently when installing from RPM the resulting permissions result on admins 
> having to complete the installation by adding a user and correcting 
> filesystem permissions.
> Ideally the RPM packages should result in installed files ready to be 
> utilised as a non-root user 



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

Reply via email to