in reply to Surprising behavior of Cwd module on Unix with symlinks
I've had exactly the same problem on a Solaris 10 system. It was essential that I get the path including the symlink, not the real path to the current working directory.
I found that even though pwd on the command line gave this, when used in a script it did not.
After much trial and error and Google searching I found that just using the value of $ENV{PWD} gave me what I needed.