nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aldrin Piri (JIRA)" <>
Subject [jira] [Commented] (NIFI-1461) RPM should create nifi user and give it access to the /opt/nifi and subdirectories
Date Wed, 10 Feb 2016 06:31:18 GMT


Aldrin Piri commented on NIFI-1461:

Did a build on a relic of the glory days of Thinkpads running CentOS 7.2

Linux brick 3.18.17-13.el7.x86_64 #1 SMP Wed Jul 22 14:20:15 UTC 2015 x86_64 x86_64 x86_64
CentOS Linux release 7.2.1511 (Core)
Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c; 2015-03-13T16:10:27-04:00)
Maven home: /usr/local/maven
Java version: 1.7.0_95, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.7.0-openjdk-
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.18.17-13.el7.x86_64", arch: "amd64", family: "unix"

Performed a mvn clean install -T2C -Pgroovy-unit-test,rpm to fully harness the sheer power
that is the Core2Duo processor. Sure, it's a mobile processor, but that's only because it
is mobilizing bits with unbridled tenacity and stunning efficiency.

Build completed successfully and was able to install.  Verified that the anticipated directory
structure is present, user was created, and the appropriate configuration was established
to have NiFi run as nifi.

Overall, looks good to me, but am interested to hear more from Andre's perspective.

As a follow on task, would like to see the associated service get installed and to branch
out with support for dpkg (had used jdeb a while ago and remember it being quite good).

> RPM should create nifi user and give it access to the /opt/nifi and subdirectories
> ----------------------------------------------------------------------------------
>                 Key: NIFI-1461
>                 URL:
>             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,, 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

This message was sent by Atlassian JIRA

View raw message