Shell Programming and Scripting

Found one interesting thing... Please check...

Code:

#Script - 

$ cat Test_27_8.sh
echo "pwd-`pwd`"
echo "dir--`dirname $0`"  
echo "$(readlink -f $0)"
cd jobs/QA

echo "pwd-`pwd`"
echo "dir--`dirname $0`"
echo "$(readlink -f $0)"
cd QA

echo "pwd-`pwd`"
echo "dir--`dirname $0`"
echo "$(readlink -f $0)"


$ sh Test_27_8.sh
pwd-jobs
dir--.
jobs/Test_27_8.sh
pwd-jobs/QA
dir--.
jobs/QA/Test_27_8.sh
jobs/QA/QA
dir--.
jobs/QA/QA/Test_27_8.sh


#Run with the full path - Here we get the correct path....:)
sh /jobs/Test_27_8.sh
pwd-/jobs
dir--/jobs
/jobs/Test_27_8.sh
pwd-/jobs/QA
dre--/jobs
/jobs/Test_27_8.sh
pwd-/jobs/QA/QA
dir--/jobs
/jobs/Test_27_8.sh

@JC_1 - If you are using fix path for the script that you want it to use you can simply save it in a variable...

I still don't understand how readlink -f $0 is supposed to produce a full (or absolute) pathname for a shell script that was invoked as ./script or as bin/script. First, the readlink utility on openBSD and OS X systems doesn't have a -f option. Second, the man pages for systems I've seen that have a man page for readlink(1) that do have a -f option don't say anything about being able to turn a relative pathname into an absolute pathname (unless there is a symbolic link in the path being processed that expands to an absolute pathname). And, third, many systems (including Solaris 10 and 11) don't have a readlink utility at all.