[
https://issues.apache.org/jira/browse/NIFI-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824659#comment-15824659
]
ASF GitHub Bot commented on NIFI-3015:
--------------------------------------
Github user jfrazee commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1422#discussion_r96313139
--- Diff: nifi-assembly/pom.xml ---
@@ -19,6 +19,10 @@ language governing permissions and limitations under the
License. -->
<artifactId>nifi-assembly</artifactId>
<packaging>pom</packaging>
<description>This is the assembly Apache NiFi</description>
+ <!--Add a blank run.as in case RPM isn't being used -->
+ <properties>
+ <nifi.run.as />
--- End diff --
@trixpan I guess what I'm saying is that with this change I think -Prpm
makes a good rpm but not a good .tar.gz or .zip since the user will now need to
edit bootstrap.conf if they're using the archive package; install.sh doesn't
create the nifi user, right? I think somehow or other it needs to use the
defaultUsername that the maven-rpm-plugin is using but I'm not sure how without
digging further.
> 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)
