[
https://issues.apache.org/jira/browse/NIFI-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141838#comment-15141838
]
Puspendu Banerjee commented on NIFI-1461:
-----------------------------------------
[~trixpan]I have the same understanding. We should not delete User-Group from
rpm.
If ever we are out of UID/GID, rpm install should fail & admin should do a
manual clean-up, after handling any residue of files created by non-existent
user, so that UID/GID can be allocated.
At the same point of time, I could not understand **Scenario 2.b - Folders are
writeable by nifi** that you are concerned about. It will be really helpful to
me to get enlightened on that matter as I am not seeing any files with
different ownership than nifi:nifi.
> 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)
