[
https://issues.apache.org/jira/browse/NIFI-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15575227#comment-15575227
]
ASF GitHub Bot commented on NIFI-1710:
--------------------------------------
Github user jfrazee commented on the issue:
https://github.com/apache/nifi/pull/1137
@trixpan Thanks for picking this up again! Since this is just about
variation in the arguments that readlink supports or the availability of
realpath, I would have thought it'd just be simpler to have a case statement
around the platform/uname. I don't see anything wrong with it at all, it's just
a little complicated.
> 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)
