[
https://issues.apache.org/jira/browse/NIFI-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220200#comment-15220200
]
ASF GitHub Bot commented on NIFI-1710:
--------------------------------------
Github user jfrazee commented on the pull request:
https://github.com/apache/nifi/pull/315#issuecomment-204017042
@arpitgupta Ok, yeah, older versions of coreutils don't have it. I was
doing this with `readlink` but BSD readlink doesn't have the same options as
GNU. Looks like it might be necessary to push this down into detectOS(), if
people want this sort of change at all.
> 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)
