As per my knowledge, to determine the current shell we use echo $0
in the shell. Rather I want my script to check in which shell it is running. So, I tried to print $0
in the script and it returns the name of the script as it should. So, my question is how can I find which shell is my script running in during runtime?
8 Answers
Maybe not what you're asking for, but this should work to some extent to identify the interpreter currently interpreting it for a few like
- Thompson shell (
osh
), - Bourne shell,
- Bourne-again shell (
bash
), - Korn shell (
ksh88
,ksh93
,pdksh
,mksh
), zsh
,- Policy-compliant Ordinary shell (
posh
), - Yet Another shell (
yash
), rc
shell,akanga
shell,- es shell,
wish
TCL interpreter,tclsh
TCL interpreter,expect
TCL interpreter,- Perl,
- Python,
- Ruby,
- PHP,
- JavaScript (nodejs, SpiderMonkey shell and JSPL at least)
- MS/Wine
cmd.exe
,command.com
(MSDOS, FreeDOS...).
'echo' +"'[{<?php echo chr(13)?>php <?php echo PHP_VERSION.chr(10);exit;?>}\
@GOTO DOS [exit[set 1 [[set 2 package] names];set 3 Tcl\ [info patchlevel];\
if {[lsearch -exact $1 Expect]>=0} {puts expect\ [$2 require Expect]\ ($3)} \
elseif {[lsearch -exact $1 Tk]>=0} {puts wish\ ($3,\ Tk\ [$2 require Tk])} \
else {puts $3}]]]' >/dev/null ' {\">/dev/null \
">"/dev/null" +"\'";q="#{",1//2,"}";a=+1;q='''=.q,';q=%{\"
'echo' /*>/dev/null
echo ">/dev/null;status=0;@ {status=1};*=(" '$' ");~ $status 1&&{e='"\
"';eval catch $2 ^'&version {eval ''echo <='^ $2 ^'&version''}';exit};e='"\
"';if (eval '{let ''a^~a''} >[2] /dev/null'){e='"\
"';exec echo akanga};eval exec echo rc $2 ^ version;\" > /dev/null
: #;echo possibly pre-Bourne UNIX V1-6 shell;exit
if (! $?version) set version=csh;exec echo $version
:DOS
@CLS
@IF NOT "%DOSEMU_VERSION%"=="" ECHO DOSEMU %DOSEMU_VERSION%
@ECHO %OS% %COMSPEC%
@VER
@GOTO FIN
", unless eval 'printf "perl %vd\n",$^V;exit;'> "/dev/null";eval ': "\'';
=S"';f=false e=exec\ echo n=/dev/null v=SH_VERSION;`(eval "f() { echo :
};f")2>$n` $f||$e Bourne-like shell without function
case `(: ${_z_?1}) 2>&1` in 1) $e ash/BSD sh;;esac;t(){
eval "\${$1$v+:} $f &&exec echo ${2}sh \$$1$v";};t BA ba;t Z z;t PO po;t YA ya
case `(typeset -Z2 b=0;$e $b)2>$n` in 00) (eval ':${.}')2>$n&&eval '
$e ksh93 ${.sh.version}';t K pdk;$e ksh88;;esac;case `(eval '$e ${f#*s}$($e 1
)$((1+1))')2>$n` in e12)$e POSIX shell;;esac;$e Bourne-like shell;: }
print "ruby ",RUBY_VERSION,"\n";exit;' ''';import sys
print("python "+sys.version);z='''*/;
s="";j="JavaScript";if(typeof process=="object"){p=console.log;p(process.title
,process.version)}else{p=print;p((f="function")==(t=typeof version)?"string"==
typeof(v=version())?v:(typeof build!=f?"":s= "SpiderMonkey ")+j+" "+v:(t==
"undefined"?j+"?":version)+"\n");if(s)build()}/*
:FIN } *///'''
I posted the initial version of that which_interpreter script circa 2004 on usenet. Sven Mascheck has a (probably more useful to you) script called whatshell that focuses on identifying Bourne-like shells. You can also find a merged version of our two scripts there.
-
54This is the biggest WTF moment of the year so far. +1 for taking portability past sanity.– l0b0Commented Apr 4, 2013 at 11:35
-
4
-
2@xfix, I remember trying even before adding php and javascript but couldn't find a solution then. The complexity grows exponentially with the number of languages to support (as everything you add must be valid (or at least have unnoticeable side-effects) in all the supported languages) so it would be even more difficult now. I'm not saying it's impossible but that would probably mean dropping support for some other languages. Commented Mar 23, 2014 at 20:45
-
2@iconoclast, you mean you ran
zsh ./that-script
and it returnedbash 3.2.53(1)-release
? More likely you ran it as./that-script
from withinzsh
which got it interpreted by yoursh
, and yoursh
happens to bebash
. Commented Aug 9, 2015 at 20:37 -
4@iconoclast, so it correctly identifies
bash 3.2.53(1)-release
as the interpreter interpreting it. Commented Aug 10, 2015 at 8:53
On linux you can use /proc/PID/exe
.
Example:
# readlink /proc/$$/exe
/bin/zsh
-
3That's a bit too specific for me (e.g. on Debian it prints zsh4 or ksh93).
/bin/sed -r -e 's/\x0.*//' /proc/$$/cmdline
gives zsh or ksh instead. (That'd be $0 if shells didn't magically fix this to give the scripts name instead). Commented Apr 12, 2013 at 23:17 -
Not really. It depends on what the OP really wants. Not reading the link also causes
#!/bin/sh
to return justsh
even if it's really bash, dash, etc. Can't follow links and not follow links at the same time. Unless you check if it'ssh
and follow then or something, but that solution is plain weird. Commented Apr 14, 2013 at 17:00 -
This is what I use in my .profile to check for various shells on the systems I work on. It doesn't make fine distinctions between ksh88 and ksh93, but it has never failed me.
Note that it doesn't require a single fork or pipe.
# Determine what (Bourne compatible) shell we are running under. Put the result
# in $PROFILE_SHELL (not $SHELL) so further code can depend on the shell type.
if test -n "$ZSH_VERSION"; then
PROFILE_SHELL=zsh
elif test -n "$BASH_VERSION"; then
PROFILE_SHELL=bash
elif test -n "$KSH_VERSION"; then
PROFILE_SHELL=ksh
elif test -n "$FCEDIT"; then
PROFILE_SHELL=ksh
elif test -n "$PS3"; then
PROFILE_SHELL=unknown
else
PROFILE_SHELL=sh
fi
-
1Note that only very recent versions of
ksh93
have$KSH_VERSION
. That variable comes frompdksh
and never made it to AT&T ksh88. Commented Apr 15, 2013 at 21:28 -
-
2Right. Note that
posh
(pdksh with most non-POSIX features removed so you would probably want to call it "sh") has no FCEDIT nor KSH_VERSION but has PS3 (maybe not for long), though it's unlikely for one to have it as a login shell. Also note that the code above wouldn't reflect whetherbash
orzsh
are insh
emulation mode, which may be a problem if you're using$PROFILE_SHELL
to decide whether or not to enable this or that feature. See also Sven Mascheck's whatshell for more you may (or may not) want to check. Commented Apr 16, 2013 at 6:25 -
1This is the cleanest approach if readability matters.– user223600Commented Jan 21, 2020 at 13:07
You could try
ps -o args= -p "$$"
which will give you the name of the command associated with the script's pid.
If there is the lsof
command available on your system, you can get the full path of the parent shell executable by getting the parent PID via ps
and parsing the ouput of lsof -p $ppid
(see How to determine the current shell i'm working on?).
#!/bin/sh
ppid="`ps -p "$$" -o ppid=`"
lsof -nP -p "$ppid" | awk 'NR==3 {print $NF; exit}'
-
On my system this returns
/
, if I useNR==4
I get the path to the shells parent.– ThorCommented Apr 15, 2013 at 7:10 -
1Note that POSIX
sh
s have the$PPID
variable. OnLinux
, you can usereadlink -f "/proc/$PPID/exe"
. Commented Sep 9, 2014 at 12:48 -
1Please, stop using backticks in shell scripts. It's rarely the right tool for the job. Commented Jan 13, 2023 at 22:17
Portable solution (tested in Linux and MacOS):
ps -o args= -p $$ | egrep -m 1 -o '\w{0,5}sh'
where:
ps -o args=
retrieves the command line arguments$$
gives you the current PID-m 1
to finish searching after the first match-o
to only display matching portion\w{0,5}sh
regular expression to find things likebash
in/bin/bash
orksh
in-ksh
orsh
insh
(Maximum 5 characters+sh
)
-
egrep
is not universal.grep -E
would be more "portable", but still non-standard. The\w
thing is a GNU-ism supported by somegrep
implementation. This returnssh
when I'm inzsh
on OpenBSD if I run it as-is (probably because\w
is only matching a literalw
).– Kusalananda ♦Commented Jan 3, 2020 at 15:17
Outside of Linux land or lacking access to the /proc filesystem or equivelent, you can make use of pstree:
Assuming you have the pid of
On a Mac:
./test.sh
16012
-+= 00001 root /sbin/launchd
\-+= 00245 wingwong /sbin/launchd
\-+= 04670 wingwong /Applications/Utilities/Terminal.app/Contents/MacOS/Terminal -psn_0_2052597
\-+= 11816 root login -pf wingwong
\-+= 11817 wingwong -bash
\-+= 16012 wingwong ksh ./test.sh
\-+- 16013 wingwong pstree -p 16012
On a Linux box:
./test.sh
14981
bash(14981)---pstree(14982)
The format and style of the output from pstree differs, depending on your environment, but you can enforce ASCII output and then sed/tr/awk/etc. filter the output to get the shell that is running the script.
So a cleaned up output version(works for Mac or Linux OS runs):
#!/usr/bin/env sh
pstree -p $$ | tr ' ()' '\012\012\012' | grep -i "sh$" | grep -v "$0" | tail -1
On run yields:
./test.sh
sh
And when run with a different shell:
#!/usr/bin/env ksh
pstree -p $$ | tr ' ()' '\012\012\012' | grep -i "sh$" | grep -v "$0" | tail -1
Yields:
./test.sh
ksh
No root or special filesystem required. Note, my filtering assumes that the shell binary name ends with sh and that there are no intermediate entries which end with sh. Also assumes that you didn't name your script "sh" or some unfortunate grep pattern that will obliterate information. :) Will require some customization for your own environment to ensure a higher degree of foolproofing.
You can use the command:
$ echo $SHELL
to find out the shell from within the script.
-
24No.
$SHELL
is the shell of choice of the user. Initialised from the login shell of the user. Nothing to do with the currently running shell. Commented Apr 4, 2013 at 6:55
echo $0
is not an option here ,as the script will run on many different machines where first thing I'll need to check is the shell.#! /bin/sh -
at the top, it will run insh
. Do you mean what variant ofsh
is it?