Sometimes you want a shell script to have different behavior depending upon how it was invoked. One trick I've used in that situation is to walk the process tree backwards and see what invoked the script. You can do that using ps or by looking in /proc. PPID is probably in your environment already, so it can be as simple as
ps -p $PPID -o cmd or ps -p $PPID -o comm
Of course that may not be far enough up the tree to find out whatever it is you need to know. For example, see http://aplawrence.com/SCOFAQ/FAQ_scotec1haltcatch.html.
In some cases, it's not so much what invoked the script as what it is running under: is it reading from a pipe, for example. The "tty" command can tell you that:
$ cat t.sh tty || exit 1 echo "OK" $ ./t.sh /dev/pts/0 OK $ date | ./t.sh not a tty
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
Sun Jun 5 06:17:34 2005: Subject: anonymous
You can also use this:
if [ -t 0 ] then echo "Reading from a terminal!" fi if [ -t 1 ] then echo "Writing to a terminal! fiArvind
PS: Why does "pre" tag not work very well here?
Sun Jun 5 09:52:24 2005: Subject: TonyLawrence
PRE doesn't work well simply because I haven't taken the time to fix the code.
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar