[
https://issues.apache.org/jira/browse/NIFI-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576301#comment-14576301
]
Aldrin Piri commented on NIFI-472:
----------------------------------
The current thought process is to avoid the handling of applying sudo via
RunNiFi and prefer instead to manage this via nifi.sh, providing the associated
checks.
This requires a bit of a shift on permissions of the released distribution
artifacts where it seems best to favor a shared owner/group permission base and
have the user of the system.
This dictates that the owner and run as user are both in the same group and
further that the owner has sudo privileges. This seems inline with how a lot
of *nix software packages handle this behavior.
> When running NiFi with the "run.as" property specified in the bootstrap.conf
> file, the run.as user should own the nifi.pid file
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-472
> URL: https://issues.apache.org/jira/browse/NIFI-472
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Aldrin Piri
> Fix For: 0.2.0
>
> Attachments:
> 0001-Providing-ownership-of-the-nifi.pid-file-in-the-case.patch
>
>
> Currently, if I set the "run.as" user to something like "nifi" and then I run
> "bin/nifi.sh start", a file named "nifi.pid" is created in the bin/
> directory, but it is owned by me. It should instead be owned by the "run.as"
> user (nifi).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
