[
https://issues.apache.org/jira/browse/NIFI-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683875#comment-15683875
]
ASF GitHub Bot commented on NIFI-3015:
--------------------------------------
Github user jfrazee commented on the issue:
https://github.com/apache/nifi/pull/1198
@fidget83 I think the right thing is to find some way to update the run.as
setting, as @trixpan mentions, from the rpm since we know the nifi user exists
then and fold that into the rpm spec. Right now, `nifi.sh install` can and does
get used on non-RedHat derived platforms without rpms and in tarball installs
so there's no guarantee the user exists. It's a good change if done right
though.
> NiFi service starts from root user after installation
> -----------------------------------------------------
>
> Key: NIFI-3015
> URL: https://issues.apache.org/jira/browse/NIFI-3015
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 1.1.0
> Environment: Centos 7.2
> Reporter: Artem Yermakov
> Assignee: Andre
> Priority: Critical
>
> When install NiFi using command nifi.sh install, and then start NiFi by
> command service nifi start, NiFi will start from user root.
> I suggest to run it from user nifi which is created during rpm installation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
