[
https://issues.apache.org/jira/browse/NIFI-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220049#comment-15220049
]
ASF GitHub Bot commented on NIFI-1710:
--------------------------------------
GitHub user jfrazee opened a pull request:
https://github.com/apache/nifi/pull/315
NIFI-1710 Resolve path name to nifi.sh in start script
This adds `realpath` to nifi.sh to resolve location of nifi.sh when its
symlinked (instead of installed using the `install` command). Recent versions
of Linux and BSD make `realpath` available.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jfrazee/nifi NIFI-1710
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/315.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #315
----
commit dbad7f41d6177f38f3736e539e77bb05433c2773
Author: Joey Frazee <[email protected]>
Date: 2016-03-31T15:33:29Z
Added realpath to nifi.sh to resolve its location when symlinked
----
> Resolve path name to nifi.sh in start script
> --------------------------------------------
>
> Key: NIFI-1710
> URL: https://issues.apache.org/jira/browse/NIFI-1710
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joey Frazee
> Priority: Trivial
>
> Currently if you symlink to nifi.sh the start script will not work because $0
> doesn't evaluate to the physical location and the script assumes
> bootstrap.conf is relative to the script.
> This means you can't, for example, symlink nifi.sh to /etc/init.d and use the
> respective service commands to control NiFi.
> Adding realpath or readlink to the script should fix this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
