[jira] [Updated] (NIFI-1710) Resolve path name to nifi.sh in start script

2016-10-18 Thread Andy LoPresto (JIRA)

 [ 
https://issues.apache.org/jira/browse/NIFI-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy LoPresto updated NIFI-1710:

Assignee: Andre

> 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
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Joey Frazee
>Assignee: Andre
>Priority: Trivial
> Fix For: 1.1.0
>
>
> 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)


[jira] [Updated] (NIFI-1710) Resolve path name to nifi.sh in start script

2016-10-18 Thread Andy LoPresto (JIRA)

 [ 
https://issues.apache.org/jira/browse/NIFI-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy LoPresto updated NIFI-1710:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Fixed via PR 1137. 

> 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
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Joey Frazee
>Assignee: Andre
>Priority: Trivial
> Fix For: 1.1.0
>
>
> 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)


[jira] [Updated] (NIFI-1710) Resolve path name to nifi.sh in start script

2016-10-18 Thread Andy LoPresto (JIRA)

 [ 
https://issues.apache.org/jira/browse/NIFI-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy LoPresto updated NIFI-1710:

Affects Version/s: 1.0.0

> 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
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Joey Frazee
>Priority: Trivial
> Fix For: 1.1.0
>
>
> 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)


[jira] [Updated] (NIFI-1710) Resolve path name to nifi.sh in start script

2016-10-18 Thread Andy LoPresto (JIRA)

 [ 
https://issues.apache.org/jira/browse/NIFI-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy LoPresto updated NIFI-1710:

Component/s: Tools and Build

> 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
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Joey Frazee
>Priority: Trivial
> Fix For: 1.1.0
>
>
> 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)


[jira] [Updated] (NIFI-1710) Resolve path name to nifi.sh in start script

2016-10-18 Thread Andy LoPresto (JIRA)

 [ 
https://issues.apache.org/jira/browse/NIFI-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy LoPresto updated NIFI-1710:

Fix Version/s: 1.1.0

> 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
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Joey Frazee
>Priority: Trivial
> Fix For: 1.1.0
>
>
> 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)