Command Lists and Scripts

Question 1

Multiple commands can be separated with a…?

Answer 1

;

Question 2

Upon exiting, every command returns an integer to its parent called a…?

Answer 2

return value.

Question 3

The shell variable $? expands to the return value of….?

Answer 3

previously executed command.

Question 4

&& and || conditionally separate…?

Answer 4

multiple commands.

Question 5

The bash shell allows users to easily run commands in a subshell, by…?

Answer 5

wrapping the command with parenthesis.

Question 6

Why would someone want to run a command in a subshell?

Answer 6

Subshells are used to avoid side effects. What happens in the subshell should not effect the original shell’s environment (just as, in English, what happens in parenthesis should not change the surrounding sentence’s context).

Question 7

The key to using Red Hat Enterprise Linux effectively is….?

Answer 7

automation.

Question 8

A good Linux administrator should actually be extremely lazy when it comes to doing anything….?

Answer 8

boring or repetitive.

Question 9

However, one important piece of your system administrator’s toolkit is still missing….?

Answer 9

scripting.

Question 10

A script is, in its simplest form, just a text file with a…?

Answer 10

list of commands in it.

(The commands are sent through a specified program, called an interpreter, which runs each command in turn. Usually this interpreter will be the bash shell (referred to as /bin/bash or /bin/sh) and each command is an ordinary Linux command. Other interpreters allow you to use more powerful programming languages like Perl, Python and Ruby.)

Question 11

Before you can begin writing scripts of your own, there are a few important things to remember:

Answer 11

• The first line of your script must specify which interpreter to send instructions to. This is done with a special string called a “shebang” (pronounced “shuh-bang”), which looks like this: #!. The shebang is followed by the name of the interpreter for this script. So, for example, to use bash as your interpreter you would use #!/bin/sh or #!/bin/bash. Most scripts just use #!/bin/sh. Referring to the interpreter as #!/bin/bash enables some extra features but limits the script’s compatibility with older Unix systems and is rarely necessary.
• Before you can run a script, you must enable the “executable” permission on it (otherwise, it’s just a text file). The command to do this is chmod u+x . This grants you (and only you) permission to run this script just like you would any other command. The chmod command will be discussed in much more detail later in this class.
• If you created a script called foo.sh in your home directory and then just typed foo.sh you would get a “no such file or directory” error. This is because when you type a command, there is a fixed set of directories that Linux looks for that command in. These directories are referred to collectively as your PATH and, for security reasons, your PATH never includes the current directory. To solve this problem you have two choices:
  1. You can explicitly specify the location of the script by typing ~/foo.sh or ./foo.sh (“.” always refers to the current directory).
  2. You can place the script in a directory that is part of your PATH. Non-root users do not have permission to place files in most of these directories, but all users have a personal bin, to which they can write, in their home directory. So if foo.sh were moved to ~/bin it could be run by simply typing foo.sh at the command line. This is the preferred technique.

Question 12

Suppose you are an administrator who often needs to see which users are logged into the system. This information can be obtained by running the….?

Answer 12

w command (yes, that’s the whole thing) but, while this provides a nice summary of who is logged into the system, it does not print the time at which this snapshot of user activity was taken. Another command, called date prints out the current date and time, but no user information. If only you could combine those two commands into one….

Suppose you created a script called wdate.sh in your personal bin directory:

see https://academy.redhat.com/courses/rha030-6.1/rha030_bash_cmdlists.html for the example.

Question 13

Every process in Linux has a…?

Answer 13

Lifespan.

Question 14

All processes start at the request of another…?

Answer 14

process (often a shell)

Question 15

The requesting process is referred to as the…?

Answer 15

parent, and the newly born process the child

Question 16

Usually, the child process performs its duties (which might involve spawning children of its own), and then…?

Answer 16

elects to die.

Question 17

An exiting process leaves a little piece of information behind when it dies, called the…?

Answer 17

process’s return value, or exit status.

Question 18

The parent process is responsible for collecting the…?

Answer 18

return values of dead children.

Question 19

Return values come in the form of integers which range from..?

Answer 19

0 to 255

Question 20

Programs are free to choose what….?

Answer 20

value to return upon exiting

Question 21

Often, what implications are meant by different return values are…?

Answer 21

part of a program’s well defined interface, and are documented in that program’s man page. (If you are familiar with the diff command, the “DIAGNOSTICS” section of its man page provides an example)

Question 22

A Linux-wide (and Unix-wide) convention is that a program returns a…?

Answer 22

0 to imply “success” at whatever it was trying to accomplish, and a non zero return value to imply some form of failure.

Question 23

The bash shell stores the return value of the previously executed command in a special variable called…?

Answer 23

simply ?

Question 24

The bash shell uses && and || to…..?

Answer 24

join two commands conditionally

Question 25

When commands are conditionally joined, the...?

Answer 25

first will always execute. The second command may execute or not, depending on the return value of the first command. For example, a user may want to create a directory, and then move a new file into that directory. If the creation of the directory fails, then there is no reason to move the file. By coupling two commands with &&, the second command will only run if the first command succeeded (i.e., had a return value of 0). This is similar to the "and" operation found in may programming languages. In the above example, the mkdir command succeeded, and the file was moved.

Question 26

Similarly, multiple commands can be combined with ||. In this case...?

Answer 26

bash will execute the second command only if the first command "fails" (has a non zero return value). This is similar to the "or" operator found in programming languages. In the following example, elvis attempts to change the permissions on a file. If the command fails, a message to that effect is echoed to the screen.