[ http://issues.apache.org/jira/browse/HADOOP-566?page=comments#action_12439050 ] Lee commented on HADOOP-566: ----------------------------
An earlier issue was fixed with the hadoop-config.sh to convert a relative HADOOP_HOME path into an absolute one. However the code in the hadoop-config.sh that follows symlinks can still return a relative path after following the symlinks. The attached patch just moves the relative to absolute path conversion code to after the symlink following code. > CLONE -the hadoop-daemons.sh fails with "no such file or directory" when used > from a relative symlinked path > ------------------------------------------------------------------------------------------------------------ > > Key: HADOOP-566 > URL: http://issues.apache.org/jira/browse/HADOOP-566 > Project: Hadoop > Issue Type: Bug > Affects Versions: 0.5.0 > Reporter: Lee > Assigned To: Owen O'Malley > Fix For: 0.5.0 > > Attachments: config.patch > > > The new shell scripts fail with a relative directory: > % current/bin/hadoop-daemons.sh start datanode > node1: current/bin/..: No such file or directory > node2: current/bin/..: No such file or directory > The problem is that HADOOP_HOME is set to a relative directory and > hadoop-daemons does a cd, breaking the other scripts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
