How to tell what (parent) directory a script is running from

Yup,

Mr. Blake is on to the right solution here using a positional parameter. $0 is the full path of the script. That is why you will see things like `srm $0` at the end of a postflight script so the script removes itself after running.

Here is a proof of concept I whipped up really fast:

#!/bin/bash

# test to find full path of script

echo "$0 is the full path"

exit 0

Here is the output:

$ bash -x /Users/tlarkin/Documents/scripts/test_pwd.sh 
+ echo '/Users/tlarkin/Documents/scripts/test_pwd.sh is the full path'
/Users/tlarkin/Documents/scripts/test_pwd.sh is the full path
+ exit 0

Hope that helps you.

Thanks,
Tom

Thanks! Your answers set me on the right path. It's amazing what you can think of when you aren't completely losing your mind at work. It's as simple as 'cd ..' since it's a script being run from Casper, i already know it's location - CasperShare/Scripts, so if i just issue a

cd ..
Parent=`pwd`

that gives me the parent directory of the Scripts directory.... and then I just remembered that scripts don't run from the CasperShare unless you call them with the jamf binary. Is there a way to trace the running script back to the share it came from?

lsof is your friend. While a script is running, something like

lsof /usr/sbin/jamf

Should get you a list of open files that the jamf binary has called. That will give you the full file path and you should see a /Volumes/CasperShare or /Volumes/CasperShare 1 depending on the state of your machine (e.g. if Casper Admin is open)