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

Marc Bush commented on KAFKA-4566:
----------------------------------

on REL, at least, I found the issue to be with the calling of a path with 
$base_dir/../etc/etc/etc 
it's the .. that kept on causing the OS to evaluate the path as the "real" path 
instead of the symlink version of the path.

I'm my case I use one source location of the kafka files then tor run a number 
of zookeepers and brokers I have directories that inside symlink back to the 
/bin and /lib directories of the source allowing me to have unique config 
directories in each other instance. 

Until I recoded the /../ parts upon startup everythign would redirect and try 
to use everything from the source binaries and configs, after I modified them I 
was able to properly use the source binaries and my own unique config location. 

I'll pull my changes from my code and post them tomorrow when I have a spare 
moment. 

This "fix" only involved updating 3 files 

> Can't Symlink to Kafka bins
> ---------------------------
>
>                 Key: KAFKA-4566
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4566
>             Project: Kafka
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 0.10.1.1
>            Reporter: Stephane Maarek
>            Assignee: Akhilesh Naidu
>              Labels: newbie
>
> in the kafka consumer for example, the last line is :
> https://github.com/apache/kafka/blob/trunk/bin/kafka-console-consumer.sh#L21
> {code}
> exec $(dirname $0)/kafka-run-class.sh kafka.tools.ConsoleConsumer "$@"
> {code}
> if I create a symlink using 
> {code}
> ln -s
> {code}
> it doesn't resolve the right directory name because of $(dirname $0) 
> I believe the right way is to do:
> {code}
> "$(dirname "$(readlink -e "$0")")"
> {code}
>  
> Any thoughts on that before I do a PR?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to