[
https://issues.apache.org/jira/browse/NIFI-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140437#comment-15140437
]
Andre edited comment on NIFI-1461 at 2/10/16 7:11 AM:
------------------------------------------------------
Hope the comments above make sense.
To solve it I think we should revisit the default nifi settings such as the
location of repositories and flows.xml.gz
The idea being to separate binaries, libraries and system level config (i.e.
what gets called during bootstrap and nifi initialisation) from files that get
generated and modified "intra nifi" (e.g. repositories, flows, etc)
What do you think?
was (Author: trixpan):
Hope the comments above make sense.
To solve it I think we should revisit the default nifi settings such as the
location of repositories and flows.xml.gz
What do you think?
> 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)
