[ 
https://issues.apache.org/jira/browse/NIFI-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574686#comment-15574686
 ] 

ASF GitHub Bot commented on NIFI-1710:
--------------------------------------

Github user trixpan commented on the issue:

    https://github.com/apache/nifi/pull/1137
  
    From my tests, path finding seems to work well:
    
    ```
    [trixpan@development init.d]$ ls -l nifi
    lrwxrwxrwx 1 root root 34 Oct 14 15:02 nifi -> 
/home/trixpan/development/nifi.sh
    [trixpan@development init.d]$ ls -l /home/trixpan/development/nifi.sh
    lrwxrwxrwx 1 trixpan trixpan 108 Oct 14 15:01 
/home/trixpan/development/nifi.sh -> 
/home/trixpan/development/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT/bin/nifi.sh
    [trixpan@development init.d]$ ./nifi status
    
    Java home: /etc/alternatives/java_sdk_1.8.0/
    NiFi home: 
/home/trixpan/development/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT
    
    Bootstrap Config File: 
/home/trixpan/development/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT/conf/bootstrap.conf
    
    2016-10-14 15:03:02,399 INFO [main] org.apache.nifi.bootstrap.Command 
Apache NiFi is currently running, listening to Bootstrap on port 35711, 
PID=16000
    
    [trixpan@development init.d]$
    ```


> 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)

Reply via email to