How to write a shell script
Introduction
A shell is a command line interpretor. It takes commands and executes them. As such, it implements a programming language. The Bourne shell is used to create shell scripts — ie. programs that are interpreted\/executed by the shell. You can write shell scripts with the C-shell; however, this is not covered here. <\/P>
\n
Creating a Script
Suppose you often type the command
find . -name file -print<\/P>
\n
and you’d rather type a simple command, say
sfind file<\/P>
\n
Create a shell script
% cd ~\/bin
% emacs sfind
% page sfind
find . -name $1 -print
% chmod a+x sfind
% rehash
% cd \/usr\/local\/bin
% sfind tcsh
.\/shells\/tcsh<\/P>
\n
Observations
This quick example is far from adequate but some observations:
Shell scripts are simple text files created with an editor.
Shell scripts are marked as executeable
%chmod a+x sfind<\/P>
\n
Should be located in your search path and ~\/bin should be in your search path.
You likely need to rehash if you’re a Csh (tcsh) user (but not again when you login).
Arguments are passed from the command line and referenced. For example, as $1.
#!\/bin\/sh
All Bourne Shell scripts should begin with the sequence
#!\/bin\/sh<\/P>
\n
From the man page for exec(2):
“On the first line of an interpreter script, following the “#!”, is the name of a program which should be used to interpret the contents of the file. For instance, if the first line contains “#! \/bin\/sh”, then the con- tents of the file are executed as a shell script.” <\/P>
\n
You can get away without this, but you shouldn’t. All good scripts state the interpretor explicitly. Long ago there was just one (the Bourne Shell) but these days there are many interpretors — Csh, Ksh, Bash, and others. <\/P>
\n
Comments
Comments are any text beginning with the pound (#) sign. A comment can start anywhere on a line and continue until the end of the line.
Search Path
All shell scripts should include a search path specifica- tion:
PATH=\/usr\/ucb:\/usr\/bin:\/bin; export PATH<\/P>
\n
A PATH specification is recommended — often times a script will fail for some people because they have a different or incomplete search path.
The Bourne Shell does not export environment variables to children unless explicitly instructed to do so by using the export command. <\/P>
\n
Argument Checking
A good shell script should verify that the arguments sup- plied (if any) are correct. <\/P>
\n
if [ $# -ne 3 ]; then
echo 1>&2 Usage: $0 19 Oct 91
exit 127
fi<\/P>
\n
This script requires three arguments and gripes accordingly. <\/P>
\n
Exit status
All Unix utilities should return an exit status.
# is the year out of range for me?<\/P>
\n
if [ $year -lt 1901 -o $year -gt 2099 ]; then
echo 1>&2 Year \\”$year\\” out of range
exit 127
fi<\/P>
\n
etc…<\/P>
\n
# All done, exit ok<\/P>
\n
exit 0<\/P>
\n
A non-zero exit status indicates an error condition of some sort while a zero exit status indicates things worked as expected.
On BSD systems there’s been an attempt to categorize some of the more common exit status codes. See \/usr\/include\/sysexits.h. <\/P>
\n
Using exit status
Exit codes are important for those who use your code. Many constructs test on the exit status of a command.
The conditional construct is: <\/P>
\n
if command; then
command
fi<\/P>
\n
For example,
if tty -s; then
echo Enter text end with \\^D
fi<\/P>
\n
Your code should be written with the expectation that others will use it. Making sure you return a meaningful exit status will help.
Stdin, Stdout, Stderr
Standard input, output, and error are file descriptors 0, 1, and 2. Each has a particular role and should be used accordingly:
# is the year out of range for me?<\/P>
\n
if [ $year -lt 1901 -o $year -gt 2099 ]; then
echo 1>&2 Year \\”$year\\” out of my range
exit 127
fi<\/P>
\n
etc…<\/P>
\n
# ok, you have the number of days since Jan 1, …<\/P>
\n
case `expr $days % 7` in
0)
echo Mon$$
1)
echo Tue$$<\/P>
\n
etc…<\/P>
\n
Error messages should appear on stderr not on stdout! Output should appear on stdout. As for input\/output dialogue:
# give the fellow a chance to quit<\/P>
\n
if tty -s ; then
echo This will remove all files in $* since …
echo $n Ok to procede? $c; read ans
case “$ans” in
n*|N*)
echo File purge abandoned;
exit 0 $$
esac
RM=”rm -rfi”
else
RM=”rm -rf”
fi<\/P>
\n
Note: this code behaves differently if there’s a user to communicate with (ie. if the standard input is a tty rather than a pipe, or file, or etc. See tty(1)).
Language Constructs
For loop iteration
Substitute values for variable and perform task: <\/P>
\n
for variable in word …
do
command
done<\/P>
\n
For example:
for i in `cat $LOGS`
do
mv $i $i.$TODAY
cp \/dev\/null $i
chmod 664 $i
done<\/P>
\n
Alternatively you may see:
for variable in word …; do command; done<\/P>
\n
Case
Switch to statements depending on pattern match <\/P>
\n
case word in
[ pattern [ | pattern … ] )
command $$ ] …
esac<\/P>
\n
For example: <\/P>
\n
case “$year” in<\/P>
\n
[0-9][0-9])
year=19${year}
years=`expr $year – 1901`
$$
[0-9][0-9][0-9][0-9])
years=`expr $year – 1901`
$$
*)
echo 1>&2 Year \\”$year\\” out of range …
exit 127
$$
esac<\/P>
\n
Conditional Execution
Test exit status of command and branch <\/P>
\n
if command
then
command
[ else
command ]
fi<\/P>
\n
For example:
if [ $# -ne 3 ]; then
echo 1>&2 Usage: $0 19 Oct 91
exit 127
fi<\/P>
\n
Alternatively you may see:
if command; then command; [ else command; ] fi<\/P>
\n
While\/Until Iteration
Repeat task while command returns good exit status. <\/P>
\n
{while | until} command
do
command
done<\/P>
\n
For example:
# for each argument mentioned, purge that directory<\/P>
\n
while [ $# -ge 1 ]; do
_purge $1
shift
done<\/P>
\n
Alternatively you may see:
while command; do command; done<\/P>
\n
Variables
Variables are sequences of letters, digits, or underscores beginning with a letter or underscore. To get the contents of a variable you must prepend the name with a $. <\/P>
\n
Numeric variables (eg. like $1, etc.) are positional vari- ables for argument communication. <\/P>
\n
Variable Assignment
Assign a value to a variable by variable=value. For example: <\/P>
\n
PATH=\/usr\/ucb:\/usr\/bin:\/bin; export PATH<\/P>
\n
or
TODAY=`(set \\`date\\`; echo $1)`<\/P>
\n
Exporting Variables
Variables are not exported to children unless explicitly marked. <\/P>
\n
# We MUST have a DISPLAY environment variable<\/P>
\n
if [ “$DISPLAY” = “” ]; then
if tty -s ; then
echo “DISPLAY (`hostname`:0.0)? \\c”;
read DISPLAY
fi
if [ “$DISPLAY” = “” ]; then
DISPLAY=`hostname`:0.0
fi
export DISPLAY
fi<\/P>
\n
Likewise, for variables like the PRINTER which you want hon- ored by lpr(1). From a user’s .profile:
PRINTER=PostScript; export PRINTER<\/P>
\n
Note: that the Cshell exports all environment variables. <\/P>
\n
Referencing Variables
Use $variable (or, if necessary, ${variable}) to reference the value. <\/P>
\n
# Most user’s have a \/bin of their own<\/P>
\n
if [ “$USER” != “root” ]; then
PATH=$HOME\/bin:$PATH
else
PATH=\/etc:\/usr\/etc:$PATH
fi<\/P>
\n
The braces are required for concatenation constructs.
$p_01<\/P>
\n
The value of the variable “p_01”.
${p}_01<\/P>
\n
The value of the variable “p” with “_01” pasted onto the end. <\/P>
\n
Conditional Reference<\/P>
\n
${variable-word}<\/P>
\n
If the variable has been set, use it’s value, else use word.
POSTSCRIPT=${POSTSCRIPT-PostScript};
export POSTSCRIPT<\/P>
\n
${variable:-word}<\/P>
\n
If the variable has been set and is not null, use it’s value, else use word.
These are useful constructions for honoring the user envi- ronment. Ie. the user of the script can override variable assignments. Cf. programs like lpr(1) honor the PRINTER environment variable, you can do the same trick with your shell scripts. <\/P>
\n
${variable:?word}<\/P>
\n
If variable is set use it’s value, else print out word and exit. Useful for bailing out. <\/P>
\n
Arguments
Command line arguments to shell scripts are positional vari- ables: <\/P>
\n
$0, $1, …<\/P>
\n
The command and arguments. With $0 the command and the rest the arguments.
$#<\/P>
\n
The number of arguments.
$*, $@<\/P>
\n
All the arguments as a blank separated string. Watch out for “$*” vs. “$@”.
And, some commands:
shift<\/P>
\n
Shift the postional variables down one and decrement number of arguments.
set arg arg …<\/P>
\n
Set the positional variables to the argument list.
Command line parsing uses shift: <\/P>
\n
# parse argument list<\/P>
\n
while [ $# -ge 1 ]; do
case $1 in
process arguments…
esac
shift
done<\/P>
\n
A use of the set command:
# figure out what day it is<\/P>
\n
TODAY=`(set \\`date\\`; echo $1)`<\/P>
\n
cd $SPOOL<\/P>
\n
for i in `cat $LOGS`
do
mv $i $i.$TODAY
cp \/dev\/null $i
chmod 664 $i
done<\/P>
\n
Special Variables
$$<\/P>
\n
Current process id. This is very useful for constructing temporary files.
tmp=\/tmp\/cal0$$
trap “rm -f $tmp \/tmp\/cal1$$ \/tmp\/cal2$$”
trap exit 1 2 13 15
\/usr\/lib\/calprog >$tmp<\/P>
\n
$?<\/P>
\n
The exit status of the last command.
$command
# Run target file if no errors and …<\/P>
\n
if [ $? -eq 0 ]
then
etc…
fi<\/P>
\n
Quotes\/Special Characters
Special characters to terminate words: <\/P>
\n
; & ( ) | ^ < > new-line space tab<\/P>
\n
These are for command sequences, background jobs, etc. To quote any of these use a backslash (\\) or bracket with quote marks (“” or ”).
Single Quotes<\/P>
\n
Within single quotes all characters are quoted — including the backslash. The result is one word. <\/P>
\n
grep :${gid}: \/etc\/group | awk -F: ‘{print $1}’<\/P>
\n
Double Quotes
Within double quotes you have variable subsitution (ie. the dollar sign is interpreted) but no file name generation (ie. * and ? are quoted). The result is one word. <\/P>
\n
if [ ! “${parent}” ]; then
parent=${people}\/${group}\/${user}
fi<\/P>
\n
Back Quotes
Back quotes mean run the command and substitute the output. <\/P>
\n
if [ “`echo -n`” = “-n” ]; then
n=””
c=”\\c”
else
n=”-n”
c=””
fi<\/P>
\n
and
TODAY=`(set \\`date\\`; echo $1)`<\/P>
\n
Functions
Functions are a powerful feature that aren’t used often enough. Syntax is <\/P>
\n
name ()
{
commands
}<\/P>
\n
For example: <\/P>
\n
# Purge a directory<\/P>
\n
_purge()
{
# there had better be a directory<\/P>
\n
if [ ! -d $1 ]; then
echo $1: No such directory 1>&2
return
fi<\/P>
\n
etc…
}<\/P>
\n
Within a function the positional parmeters $0, $1, etc. are the arguments to the function (not the arguments to the script).
Within a function use return instead of exit. <\/P>
\n
Functions are good for encapsulations. You can pipe, redi- rect input, etc. to functions. For example: <\/P>
\n
# deal with a file, add people one at a time<\/P>
\n
do_file()
{
while parse_one<\/P>
\n
etc…
}<\/P>
\n
etc…<\/P>
\n
# take standard input (or a specified file) and do it.<\/P>
\n
if [ “$1” != “” ]; then
cat $1 | do_file
else
do_file
fi<\/P>
\n
Sourcing commands
You can execute shell scripts from within shell scripts. A couple of choices: <\/P>
\n
sh command<\/P>
\n
This runs the shell script as a separate shell. For example, on Sun machines in \/etc\/rc: <\/P>
\n
sh \/etc\/rc.local<\/P>
\n
. command
This runs the shell script from within the current shell script. For example: <\/P>
\n
# Read in configuration information
. \/etc\/hostconfig<\/P>
\n
What are the virtues of each? What’s the difference? The second form is useful for configuration files where environment variable are set for the script. For example:
for HOST in $HOSTS; do<\/P>
\n
# is there a config file for this host?<\/P>
\n
if [ -r ${BACKUPHOME}\/${HOST} ]; then
. ${BACKUPHOME}\/${HOST}
fi
etc…<\/P>
\n
Using configuration files in this manner makes it possible to write scripts that are automatically tailored for differ- ent situations.
Some Tricks
Test
The most powerful command is test(1). <\/P>
\n
if test expression; then<\/P>
\n
etc…<\/P>
\n
and (note the matching bracket argument)
if [ expression ]; then<\/P>
\n
etc…<\/P>
\n
On System V machines this is a builtin (check out the com- mand \/bin\/test).
On BSD systems (like the Suns) compare the command \/usr\/bin\/test with \/usr\/bin\/[. <\/P>
\n
Useful expressions are: <\/P>
\n
test { -w, -r, -x, -s, … } filename<\/P>
\n
is file writeable, readable, executeable, empty, etc?
test n1 { -eq, -ne, -gt, … } n2<\/P>
\n
are numbers equal, not equal, greater than, etc.?
test s1 { =, != } s2<\/P>
\n
Are strings the same or different?
test cond1 { -o, -a } cond2<\/P>
\n
Binary or; binary and; use ! for unary negation.
For example <\/P>
\n
if [ $year -lt 1901 -o $year -gt 2099 ]; then
echo 1>&2 Year \\”$year\\” out of range
exit 127
fi<\/P>
\n
Learn this command inside out! It does a lot for you. <\/P>
\n
String matching
The test command provides limited string matching tests. A more powerful trick is to match strings with the case switch. <\/P>
\n
# parse argument list<\/P>
\n
while [ $# -ge 1 ]; do
case $1 in
-c*) rate=`echo $1 | cut -c3-`$$
-c) shift; rate=$1 $$
-p*) prefix=`echo $1 | cut -c3-`$$
-p) shift; prefix=$1 $$
-*) echo $Usage; exit 1 $$
*) disks=$*; break $$
esac<\/P>
\n
shift<\/P>
\n
done<\/P>
\n
Of course getopt would work much better. <\/P>
\n
SysV vs BSD echo
On BSD systems to get a prompt you’d say: <\/P>
\n
echo -n Ok to procede?; read ans<\/P>
\n
On SysV systems you’d say:
echo Ok to procede? \\c; read ans<\/P>
\n
In an effort to produce portable code we’ve been using:
# figure out what kind of echo to use<\/P>
\n
if [ “`echo -n`” = “-n” ]; then
n=””; c=”\\c”
else
n=”-n”; c=””
fi<\/P>
\n
etc…<\/P>
\n
echo $n Ok to procede? $c; read ans<\/P>
\n
Is there a person?
The Unix tradition is that programs should execute as qui- etly as possible. Especially for pipelines, cron jobs, etc. <\/P>
\n
User prompts aren’t required if there’s no user. <\/P>
\n
# If there’s a person out there, prod him a bit.<\/P>
\n
if tty -s; then
echo Enter text end with \\^D
fi<\/P>
\n
The tradition also extends to output.
# If the output is to a terminal, be verbose<\/P>
\n
if tty -s <&1; then
verbose=true
else
verbose=false
fi<\/P>
\n
Beware: just because stdin is a tty that doesn’t mean that stdout is too. User prompts should be directed to the user terminal.
# If there’s a person out there, prod him a bit.<\/P>
\n
if tty -s; then
echo Enter text end with \\^D >&0
fi<\/P>
\n
Have you ever had a program stop waiting for keyboard input when the output is directed elsewhere? <\/P>
\n
Creating Input
We’re familiar with redirecting input. For example: <\/P>
\n
# take standard input (or a specified file) and do it.<\/P>
\n
if [ “$1” != “” ]; then
cat $1 | do_file
else
do_file
fi<\/P>
\n
alternatively, redirection from a file:
# take standard input (or a specified file) and do it.<\/P>
\n
if [ “$1” != “” ]; then
do_file < $1
else
do_file
fi<\/P>
\n
You can also construct files on the fly. subscribe $2 Usenet Feeder at UWO Note: that variables are expanded in the input. <\/P> String Manipulations TIME=`date | sed ‘s\/.* .* .* \\(.*\\) .* .*\/\\1\/’`<\/P> TIME=`date | awk ‘{print $4}’`<\/P> TIME=`set \\`date\\`; echo $4`<\/P> TIME=`date | (read u v w x y z; echo $x)`<\/P> With some care, redefining the input field separators can help. <\/P> #!\/bin\/sh name() if [ $# -ne 1 ]; then add=`name $1`<\/P> nslookup < < EOF | grep “$add” | sed ‘s\/.*= \/\/’ Debugging sh -n command<\/P> Read the shell script but don’t execute the commands. IE. check syntax. <\/P> sh -x command<\/P> Display commands and arguments as they’re executed. In a lot of my shell scripts you’ll see <\/P> # Uncomment the next line for testing <\/P><\/p>\n","protected":false},"excerpt":{"rendered":" How to write a shell scriptIntroductionA shell is a command line interpretor. It takes commands and executes them. As such, it implements a programming language. The Bourne shell is used to create shell scripts — ie. programs that are interpreted\/executed by the shell. You can write shell scripts with the C-shell; however, this is not … Continue reading How to write a shell script<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[101],"class_list":["post-440","post","type-post","status-publish","format-standard","hentry","category-linux","tag-shell"],"_links":{"self":[{"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/posts\/440","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.strongd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=440"}],"version-history":[{"count":1,"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/posts\/440\/revisions"}],"predecessor-version":[{"id":935,"href":"https:\/\/www.strongd.net\/index.php?rest_route=\/wp\/v2\/posts\/440\/revisions\/935"}],"wp:attachment":[{"href":"https:\/\/www.strongd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=440"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.strongd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=440"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.strongd.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=440"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
rmail bsmtp <
rcpt to:
data
from: <$1@newshost.uwo.ca<\/A>>
to:
Subject: Signon $2<\/P>
\n
.
quit
EOF<\/P>
\n
\n
One of the more common things you’ll need to do is parse strings. Some tricks <\/P>
\n
TIME=`date | cut -c12-19`<\/P>
\n
\n
\n
\n
\n
\n
# convert IP number to in-addr.arpa name<\/P>
\n
{ set `IFS=”.”;echo $1`
echo $4.$3.$2.$1.in-addr.arpa
}<\/P>
\n
echo 1>&2 Usage: bynum IP-address
exit 127
fi<\/P>
\n
\n
set type=any
$add
EOF<\/P>
\n
The shell has a number of flags that make debugging easier: <\/P>
\n
\n
\n
\n
\n
# set -x<\/P>
\n