[
https://issues.apache.org/jira/browse/NIFI-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136175#comment-15136175
]
Puspendu Banerjee commented on NIFI-1461:
-----------------------------------------
[~jameswing] lib and /opt/nifi Directories are not explicitly included in
package, so they were getting ownership & permission attributes from the user [
read root user here] who runs installation.
[~trixpan] ./conf/flow.xml.gz can be edited after you do a sudo[su -s
/bin/bash nifi] . I mean, group access can be given to modify , but that may
not be a good idea to do that from rpm install. Probably it will break
nonrepudiation capabilily. may be [~joewitt] can shed some more light.
Please find updated rpm spec attached & PR updated[ if Git permits :D)
[~tkurc] Going forward we should be looking at other packaging plugins[ex:
gradle-ospackage-plugin] to enjoy more features [ say .deb build] .
> 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
> Attachments: 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)
