This is an old revision of the document!

The basics of shell scripting

A shellscript usually resides inside a file. This file can be executable, but you can also call a Bash with that filename as parameter:

bash ./myfile
There is no need to add a boring filename extension like .bash or .sh. This is UNIX®, where executables are not tagged by the extension, but by permissions (filemode). Of course, you can name the file like you want! To add proper filename extensions is a convention, nothing else.
chmod +x ./myfile

If the file is executable (and you want to use it by just calling the script name), you need to specify the shebang!

The in-file specification of the interpreter of that file, like:

echo "Hello world..."
This thing usually 1) is interpreted by the kernel of your system. In general, if a file is executable, but actually not an executable (binary) program, and such a line is present, the program specified after #! is started with the scriptname and all its arguments. These two characters # and ! have to be the first two bytes in the file!

You can follow it by using the echo program as fake-interpreter:

We don't need a script-body here, as the file will never be interpreted and executed by "echo", but you can see what the system does, it calls "/bin/echo" with the name of the executable file and all what follows.
$ /home/bash/bin/test testword hello
/home/bash/bin/test testword hello

The same way, with #!/bin/bash the shell "/bin/bash" is called with the script-file as argument. It's exactly the same to execute "/bin/bash /home/bash/bin/test testword hello" here!

If the interpreter can be specified with arguments and how long it can be is system-specific (see #!-magic). Just by the way: When Bash executes a file with a #!/bin/bash-shebang, it ignores the shebang itself, because its first character is the hashmark "#", which introduces a comment. The shebang is for the operating system, not for the shell. Programs that don't ignore such lines may not work as shebang-driven interpreters.

Attention:When the specified interpreter is unavailable or not executable (permissions), you'll get a "bad interpreter" error message., usually. If you get nothing and it fails, it's still worth to check the shebang. Older Bash versions will throw a "no such file or directory" for a nonexisting interpreter specified in the shebang.

Additional note: When you specify #!/bin/sh as shebang and that's a link to a Bash, then Bash will run in POSIX® mode! See:

A common method is to specify a shebang like

#!/usr/bin/env bash
…which just moves the location of the potential problem to

  • the env utility must be located in /usr/bin/
  • the needed bash binary must be located in PATH

If you need the one or the other, or if you think the one or the other way is good/bad - it's up to you. It's just to say there is no waterproof portable way to specify an interpreter. It is a common misinterpretion that it solves all problems. Period.

Every normal UNIX®-program has, once initialized, at least 3 open files:

  • stdin: standard input
  • stdout: standard output
  • stderr: standard error output

Usually they're all connected to your terminal, stdin as input file (keyboard), stdout and stderr as output files (screen). When calling such a program, the invoking shell can change these filedescriptor's connections away from the terminal to any other file (see redirection). Why two different output filedescriptors? Well, it's a convention to output debug logs, error messages and warnings on stderr and only useful data on stdout. That way the user (you!) can decide if he wants to see nothing, only the data, only the errors, both - and where he wants to see them.

You should follow some rules when you write a script:

  • read user-input always from stdin
  • always write diagnostic/error/warning-messages to stderr

To learn more about the standard filedescriptors, especially about redirecting and piping them, see:

It's common to use lowercase variable-names for yourself, as usually shell- and system-variables are all in UPPERCASE, however you should avoid to use the following variable-names for your own purposes (incomplete list!):


This list is fairly incomplete, but it might help you to understand: The safest way really is to only use lowercase variable names.

Every program you start terminates with a so-called exit code and reports it to the operating system. This exit code can be utilized by Bash. You can show it, you can react on it, you can control the script's flow with it. The code is a number between 0 and 255, where the part from 126 to 255 is reserved to be used by the shell directly or for special purposes, like reporting a termination by a signal:

  • 126: the requested command (file) can't be executed (but was found)
  • 127: command (file) not found
  • 128: according to ABS it's used to report an invalid argument to the exit builtin, but I wasn't able to verify that in the source code of Bash (see code 255)
  • 128 + N: the shell was terminated by the signal N
  • 255: wrong argument to the exit builtin (see code 128)

The lower codes 0 to 125 are not reserved and may be used for whatever the program likes to report. A value of 0 means successful termination, a value not 0 means unsuccessful termination. This behavior (== 0, != 0) is also what Bash reacts on in some code flow control statements.

An example of using the exit code of the program grep to check if a specific user is present in /etc/passwd:

if grep ^root /etc/passwd; then
   echo "The user root was found"
   echo "The user root was not found"
A common command to use for decisions is the command "test" or its equivalent "[". But note that, when using the test-command with the command name "[", the braces are not part of the shell syntax, they are the test command! :!:
if [ "$mystring" = "Hello world" ]; then
   echo "Yeah dude, you entered the right words..."
   echo "Eeeek - go away..."
Read more about the test command

Please, when your script exits on errors, provide a "FALSE" exit code, that others can check the script execution.

In a bigger script, it's wise to comment the code. Also for debugging purposes or tests. Comments are introduced with # (hashmark) and go from that to the end of the line:

# This is a small script to say something.
echo "Be liberal in what you accept, and conservative in what you send" # say something
The first thing was already explained, it's the so-called shebang, for the shell, only a comment. The second one is a comment from the beginning of the line, where the third comment starts after a valid command. All three comments are in valid syntax.

To temporarily disable complete blocks of code you normally would have to preceede every line of that block with a # (hashmark) to make it being a comment. Now, there's a little trick, using the pseudo command : (colon) and input redirection. The : does nothing, it's a pseudo command, so it also does not care about its standard input. In the following code (you don't have to understand the code, just look what I do with the stuff), you want to test only the things that don't harm (mail, logging) but actually don't do anything to the system (dump database, shutdown):

# Write info mails, do some tasks and bring down the system in a safe way
echo "System halt requested" | mail -s "System halt"
logger -t SYSHALT "System halt requested"

##### The following "code block" is effectively ignored
/etc/init.d/mydatabase clean_stop
mydatabase_dump /var/db/db1 /mnt/fsrv0/backups/db1
logger -t SYSHALT "System halt: pre-shutdown actions done, now shutting down the system"
shutdown -h NOW
##### The ignored codeblock ends here
What happened, again? Well, the : pseudo command was given some input by redirection (a here-document) - the pseudo command didn't care about it, effectively, this complete block is ignored now. One could say, the whole block is a comment. For completeness: To make the here-document possible, the shell might generate a temporary file unter /tmp or similar.

The here-document-tag was quoted here to avoid substitutions in the "commented" text! Check redirection with here-documents for more

In Bash, the scope of the used variables is generally global. That means, if a variable is set in the "main program" or a "function" does not matter, the variable is defined everywhere.

Compare the following equivalent code snips:


myfunction() {


In both cases, the variable MYVARIABLE is set and accessible from everywhere in that script, functions and "main program".

Attention: When you set variables in a child process, for example a subshell, they will be set there, but you will never have access to them. One way to create a subshell is the pipe. It's all mentioned in a small article about Bash in the processtree!

Bash provides ways to make variable scope local to a funtion:

  • using the local keyword
  • using declare (will detect that it was called from within a function an make the variable(s) local)

myfunc() {

# alternative, only when used INSIDE a function
declare VAR=VALUE


The local (or declaring a variable using the declare command) keyword tags a variable to be treated completely local and separate inside the function where it was declared:


printvalue() {
local FOO=internal

echo $FOO

# this will print "external"
echo $FOO

# this will print "internal"

# this will print - again - "external"
echo $FOO

The environment space is not directly related to the topic about scope, but it's worth to mention.

Every UNIX® process has a so-called environment. Beside other stuff (unimportant for us), variables are saved there, so-called environment variables. Now when a child process is created (in Bash e.g. by simply executing another program, say ls to list files), the whole environment including the environment variables is copied to the new process. Reading that from the other side means: Only variables that are part of the environment are available in the child process.

A variable can be tagged to be part of the environment using the export command:

# create a new variable and set it:
# -> This is a normal shell variable, not an environment variable!
MYVARIABLE="Hello world."

# make the variable visible to all child processes:
# -> Make it an environment variable: "export" it

Remember that the exported variable is a copy when accessed in the child process. There is no chance to "copy it back to the parent", it's a one-way! Also see the article about Bash in the process tree!

sometimes, or under specific circumstances also by the shell itself
This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information
You could leave a comment if you were logged in.