Cse-IV-unix and Shell Programming (10cs44) - Notes

Download as pdf or txt
Download as pdf or txt
You are on page 1of 161

UNIX and Shell Programming

10CS44

UNIX AND SHELL PROGRAMMING


Subject Code: 10CS44
Hours/Week : 04
Total Hours : 52

UNIT 1

Scheme and Syllabus

PART A

I.A.Marks : 25
Exam Hours: 03
Exam Marks: 100

6 Hours

The Unix Operating System, The UNIX architecture and Command Usage,The File System
UNIT - 2

6 H o ur s

Basic File Attributes, the vi Editor


UNIT - 3

7 H o ur s

The Shell, The Process, Customizing the environment


UNIT - 4

7 H o ur s

More file attributes, Simple filters


PART B
UNIT - 5

6 Hours

Filters using regular expressions,


UNIT - 6

6 H o ur s

Essential Shell Programming


UNIT - 7

7 H o ur s

awk An Advanced Filter


UNIT - 8

7 H o ur s

perl - The Master Manipulator


Text Book:
1. Sumitabha Das: UNIX Concepts and Applications, 4th Edition,Tata McGraw Hill, 2006.
(Chapters 1.2, 2, 4, 6, 7, 8, 9, 10, 11, 12, 13, 14, 18, 19)
Reference Books:
1. Behrouz A. Forouzan and Richard F. Gilberg: UNIX and Shell Programming, Cengage
Learning, 2005.
2. M.G. Venkateshmurthy: UNIX & Shell Programming, Pearson Education, 2005.

Dept. of CSE, SJBIT

UNIX and Shell Programming

10CS44

Table of contents
Sl
No.
1
2

Unit Description
UNIT 1
The Unix Operating System
UNIT - 2
Basic File Attributes, the vi Editor
UNIT - 3

4
5

7
8

The Shell, The Process, Customizing the environment


UNIT - 4
More file attributes, Simple filters
UNIT - 5
Filters using regular expressions,
UNIT - 6
Essential Shell Programming

Page
No.
1-19
20-33

34-62

63-76
77-87

88-121

UNIT - 7

122-

awk An Advanced Filter

143

UNIT - 8

144-

perl - The Master Manipulator

159

Dept. of CSE, SJBIT

UNIX and Shell Programming

10CS44

UNIT 1
1.1.
The UNIX Operating System
Introduction
This chapter introduces you to the UNIX operating system. We first look at what is an operating
system and then proceed to discuss the different features of UNIX that have made it a popular
operating system.

Objectives

What is an operating system (OS)?


Features of UNIX OS
A Brief History of UNIX OS, POSIX and Single Unix Specification (SUS)

What is an operating system (OS)?


An operating system (OS) is a resource manager. It takes the form of a set of software routines
that allow users and application programs to access system resources (e.g. the CPU, memory,
disks, modems, printers, network cards etc.) in a safe, efficient and abstract way.
For example, an OS ensures safe access to a printer by allowing only one application program to
send data directly to the printer at any one time. An OS encourages efficient use of the CPU by
suspending programs that are waiting for I/O operations to complete to make way for programs
that can use the CPU more productively. An OS also provides convenient abstractions (such as
files rather than disk locations) which isolate application programmers and users from the details
of the underlying hardware.
User Applications
Application Programs

System Utilities

System Call Interface


Operating System Kernel
Processor/Hardware

UNIX Operating system allows complex tasks to be performed with a few keystrokes. It doesnt
tell or warn the user about the consequences of the command.
Kernighan and Pike (The UNIX Programming Environment) lamented long ago that as the
UNIX system has spread, the fraction of its users who are skilled in its application has
decreased. However, the capabilities of UNIX are limited only by your imagination.

Dept. of CSE, SJBIT

Page 1

UNIX and Shell Programming

10CS44

Features of UNIX OS
Several features of UNIX have made it popular. Some of them are:
Portable
UNIX can be installed on many hardware platforms. Its widespread use can be traced to the
decision to develop it using the C language.
Multiuser
The UNIX design allows multiple users to concurrently share hardware and software
Multitasking
UNIX allows a user to run more than one program at a time. In fact more than one program can
be running in the background while a user is working foreground.
Networking
While UNIX was developed to be an interactive, multiuser, multitasking system, networking is
also incorporated into the heart of the operating system. Access to another system uses a standard
communications protocol known as Transmission Control Protocol/Internet Protocol (TCP/IP).
Organized File System
UNIX has a very organized file and directory system that allows users to organize and maintain
files.
Device Independence
UNIX treats input/output devices like ordinary files. The source or destination for file input and
output is easily controlled through a UNIX design feature called redirection.
Utilities
UNIX provides a rich library of utilities that can be use to increase user productivity.

A Brief History of UNIX


In the late 1960s, researchers from General Electric, MIT and Bell Labs launched a joint
project to develop an ambitious multi-user, multi-tasking OS for mainframe computers
known as MULTICS (Multiplexed Information and Computing System). MULTICS
failed, but it did inspire Ken Thompson, who was a researcher at Bell Labs, to have a go
at writing a simpler operating system himself. He wrote a simpler version of MULTICS
on a PDP7 in assembler and called his attempt UNICS (Uniplexed Information and
Computing System). Because memory and CPU power were at a premium in those days,
UNICS (eventually shortened to UNIX) used short commands to minimize the space

Dept. of CSE, SJBIT

Page 2

UNIX and Shell Programming

10CS44

needed to store them and the time needed to decode them - hence the tradition of short
UNIX commands we use today, e.g. ls, cp, rm, mv etc.
Ken Thompson then teamed up with Dennis Ritchie, the author of the first C compiler in
1973. They rewrote the UNIX kernel in C - this was a big step forwards in terms of the
system's portability - and released the Fifth Edition of UNIX to universities in 1974. The
Seventh Edition, released in 1978, marked a split in UNIX development into two main
branches: SYSV (System 5) and BSD (Berkeley Software Distribution). BSD arose from
the University of California at Berkeley where Ken Thompson spent a sabbatical year. Its
development was continued by students at Berkeley and other research institutions.
SYSV was developed by AT&T and other commercial companies. UNIX flavors based
on SYSV have traditionally been more conservative, but better supported than BSDbased flavors.
Until recently, UNIX standards were nearly as numerous as its variants. In early days, AT&T
published a document called System V Interface Definition (SVID). X/OPEN (now The Open
Group), a consortium of vendors and users, had one too, in the X/Open Portability Guide (XPG).
In the US, yet another set of standards, named Portable Operating System Interface for Computer
Environments (POSIX), were developed at the behest of the Institution of Electrical and
Electronics Engineers (IEEE).
In 1998, X/OPEN and IEEE undertook an ambitious program of unifying the two standards. In
2001, this joint initiative resulted in a single specification called the Single UNIX Specification,
Version 3 (SUSV3), that is also known as IEEE 1003.1:2001 (POSIX.1). In 2002, the
International Organization for Standardization (ISO) approved SUSV3 and IEEE 1003.1:2001.
Some of the commercial UNIX based on system V are:

IBM's AIX
Hewlett-Packard's HPUX
SCO's Open Server Release 5
Silicon Graphics' IRIS
DEC's Digital UNIX
Sun Microsystems' Solaris 2

Some of the commercial UNIX based on BSD are:

SunOS 4.1.X (now Solaris)


DEC's Ultris
BSD/OS, 4.4BSD

Some Free UNIX are:

1.2.

Linux, written by Linus Torvalds at University of Helsinki in Finland.


FreeBSD and NetBSD, a derivative of 4.4BSD

The UNIX Architecture and Command Usage

Dept. of CSE, SJBIT

Page 3

UNIX and Shell Programming

10CS44

Introduction
In order to understand the subsequent chapters, we first need to understand the architecture of
UNIX and the concept of division of labor between two agencies viz., the shell and the kernel.
This chapter introduces the architecture of UNIX. Next we discuss the rich collection of UNIX
command set, with a specific discussion of command structure and usage of UNIX commands.
We also look at the man command, used for obtaining online help on any UNIX command.
Sometimes the keyboard sequences dont work, in which case, you need to know what to do to
fix them. Final topic of this chapter is troubleshooting some terminal problems.

Objectives

The UNIX Architecture


Locating Commands
Internal and External Commands
Command Structure and usage
Flexibility of Command Usage
The man Pages, apropos and whatis
Troubleshooting the terminal problems

The UNIX Architecture

Users

Shell
K e rn e l
Hardware

System Calls

UNIX architecture comprCSEs of two major components viz., the shell and the kernel. The
kernel
interacts with the machines hardware and the shell with the user.

Dept. of CSE, SJBIT

Page 4

UNIX and Shell Programming

10CS44

The kernel is the core of the operating system. It is a collection of routines written in C. It is
loaded into memory when the system is booted and communicates directly with the hardware.
User programs that need to access the hardware use the services of the kernel via use of system
calls and the kernel performs the job on behalf of the user. Kernel is also responsible for
managing systems memory, schedules processes, decides their priorities.

The shell performs the role of command interpreter. Even though theres only one kernel running
on the system, there could be several shells in action, one for each user whos logged in. The shell
is responsible for interpreting the meaning of metacharacters if any, found on the command line
before dispatching the command to the kernel for execution.

The File and Proces


A file is an array of bytes that stores information. It is also related to another file in the sense that
both belong to a single hierarchical directory structure.
A process is the second abstraction UNIX provides. It can be treated as a time image of an
executable file. Like files, processes also belong to a hierarchical structure. We will be discussing
the processes in detain in a subsequent chapter.

Locating Files
All UNIX commands are single words like ls, cd, cat, etc. These names are in lowercase. These
commands are essentially files containing programs, mainly written in C. Files are stored in
directories, and so are the binaries associated with these commands. You can find the location of
an executable program using type command:
$ type ls
ls is /bin/ls
This means that when you execute ls command, the shell locates this file in /bin directory and
makes arrangements to execute it.

The Path
The sequence of directories that the shell searches to look for a command is specified in its own
PATH variable. These directories are colon separated. When you issue a command, the shell
searches this list in the sequence specified to locate and execute it.

Internal and External Commands


Some commands are implemented as part of the shell itself rather than separate executable files.
Such commands that are built-in are called internal commands. If a command exists both as an
internal command of the shell as well as an external one (in /bin or /usr/bin), the shell will accord

Dept. of CSE, SJBIT

Page 5

UNIX and Shell Programming

10CS44

top priority to its own internal command with the same name. Some built-in commands are echo,
pwd, etc.

Command Structure
UNIX commands take the following general form:
verb [options] [arguments]
where verb is the command name that can take a set of optional options and one or more optional
arguments.
Commands, options and arguments have to be separated by spaces or tabs to enable the shell to
interpret them as words. A contiguous string of spaces and tabs together is called a whitespace.
The shell compresses multiple occurrences of whitespace into a single whitespace.

Options
An option is preceded by a minus sign (-) to distinguish it from filenames.
Example: $ ls l
There must not be any whitespaces between and l. Options are also arguments, but given a
special name because they are predetermined. Options can be normally compined with only one
sign. i.e., instead of using
$ ls l a t
we can as well use,
$ ls lat
Because UNIX was developed by people who had their own ideas as to what options should look
like, there will be variations in the options. Some commands use + as an option prefix instead of

Filename Arguments
Many UNIX commands use a filename as argument so that the command can take input from the
file. If a command uses a filename as argument, it will usually be the last argument, after all
options.
Example:

cp file1 file2 file3 dest_dir


rm file1 file2 file3

The command with its options and argumens is known as the command line, which is considered
as complete after [Enter] key is pressed, so that the entire line is fed to the shell as its input for
interpretation and execution.

Dept. of CSE, SJBIT

Page 6

UNIX and Shell Programming

10CS44

Exceptions
Some commands in UNIX like pwd do not take any options and arguments. Some commands like
who may or may not be specified with arguments. The ls command can run without arguments
(ls), with only options (ls l), with only filenames (ls f1 f2), or using a combination of both (ls l
f1 f2). Some commands compulsorily take options (cut). Some commands like grep, sed can take
an expression as an argument, or a set of instructions as argument.

Flexibility of Command Usage


UNIX provides flexibility in using the commands. The following discussion looks at how
permissive the shell can be to the command usage.

Combining Commands
Instead of executing commands on separate lines, where each command is processed and
executed before the next could be entered, UNIX allows you to specify more than one command
in the single command line. Each command has to be separated from the other by a ; (semicolon).
wc sample.txt ; ls l sample.txt
You can even group several commands together so that their combined output is redirected to a
file.
(wc sample.txt ; ls l sample.txt) > newfile
When a command line contains a semicolon, the shell understands that the command on each side
of it needs to be processed separately. Here ; is known as a metacharacter.
Note: When a command overflows into the next line or needs to be split into multiple lines, just
press enter, so that the secondary prompt (normally >) is displayed and you can enter the
remaining part of the command on the next line.

Entering a Command before previous command has finished


You need not have to wait for the previous command to finish before you can enter the next
command. Subsequent commands entered at the keyboard are stored in a buffer (a temporary
storage in memory) that is maintained by the kernel for all keyboard input. The next command
will be passed on to the shell for interpretation after the previous command has completed its
execution.

man: Browsing The Manual Pages Online


UNIX commands are rather cryptic. When you dont remember what options are supported by a
command or what its syntax is, you can always view man (short for manual) pages to get online
help. The man command displays online documentation of a specified command.

Dept. of CSE, SJBIT

Page 7

UNIX and Shell Programming

10CS44

A pager is a program that displays one screenful information and pauses for the user to view the
contents. The user can make use of internal commands of the pager to scroll up and scroll down
the information. The two popular pagers are more and less. more is the Berkeleys pager, which
is a superior alternative to original pg command. less is the standard pager used on Linux
systems. less if modeled after a popular editor called vi and is more powerful than more as it
provides vi-like navigational and search facilities. We can use pagers with commands like ls |
more. The man command is configured to work with a pager.

Understanding The man Documentation


The man documentation is organized in eight (08) sections. Later enhancements have added
subsections like 1C, 1M, 3N etc.) References to other sections are reflected as SEE ALSO section
of a man page.
When you use man command, it starts searching the manuals starting from section 1. If it locates
a keyword in one section, it wont continue the search, even if the keyword occurs in another
section. However, we can provide the section number additionally as argument for man
command.
For example, passwd appears in section 1 and section 4. If we want to get documentation of
passwd in section 4, we use,
$ man 4 passwd OR

$ man s4 passwd (on Solaris)

Understanding a man Page


A typical man page for wc command is shown below:
User Commands

wc(1)

NAME
wc displays a count of lines, words and characters in a file
SYNOPSIS
wc [-c | -m | -C] [-lw] [file ...]
DESCRIPTION
The wc utility reads one or more input files and, by default, writes the number of
newline characters, words and bytes contained in each input file to the standard output. The
utility also writes a total count for all named
files, if more than one input file is specified.
OPTIONS
The following options are supported:
-c

Count bytes.

Dept. of CSE, SJBIT

Page 8

UNIX and Shell Programming

10CS44

-m

Count characters.

-C

same as m.

-l

Count lines.

-w

Count words delimited by white spaces or new line characters ...

OPERANDS
The following operand is supported:
file
A path name of an input file. If no file operands are specified,
standard input will be used.

the

EXIT STATUS
See largefile(5) for the description of the behavior of wc when
greater than or equal to 2 Gbyte (2 **31 bytes)

encountering files

SEE ALSO
cksum(1),

isspace(3C), iswalpha(3C), iswspace(3C), largefile(5), ...

A man page is divided into a number of compulsory and optional sections. Every command
doesnt need all sections, but the first three (NAME, SYNOPSIS and DESCRIPTION) are
generally seen in all man pages. NAME presents a one-line introduction of the command.
SYNOPSIS shows the syntax used by the command and DESCRIPTION provides a detailed
description.
The SYNOPSIS follows certain conventions and rules:
If a command argument is enclosed in rectangular brackets, then it is optional;
otherwCSE,
the argument is required.
The ellipsis (a set if three dots) implies that there can be more instances of the preceding
word.
The | means that only one of the options shows on either side of the pipe can be used.
All the options used by the command are listed in OPTIONS section. There is a separate section
named EXIT STATUS which lists possible error conditions and their numeric representation.
Note: You can use man command to view its own documentation ($ man man). You can also set
the pager to use with man ($ PAGER=less ; export PAGER). To understand which pager is being
used by man, use $ echo $PAGER.
The following table shows the organization of man documentation.
Section Subject (SVR4)

Subject (Linux)

User programs

User programs

Dept. of CSE, SJBIT

Page 9

UNIX and Shell Programming

10CS44

Kernels system calls

Kernels system calls

Library functions

Library functions

Administrative file formats

Special files (in /dev)

Miscellaneous

Administrative file formats

Games

Games

Special files (in /dev)

Macro packages and conventions

Administration commands

Administration commands

Further Help with man k, apropos and whatis


man k: Searches a summary database and prints one-line description of the command.
Example:
$ man k awk
awk

awk(1) -pattern scanning and processing language

nawk

nawk(1)

-pattern scanning and processing language

apropos: lists the commands and files associated with a keyword.


Example:
$ apropos FTP
ftp

ftp(1)

-file transfer program

f t pd

in.ftpd(1m)

-file transfer protocol server

ftpusers ftpusers(4) -file listing users to be disallowed


ftp login privileges
whatis: lists one-liners for a command.
Example:
$ whatis cp
cp

cp(1)

Dept. of CSE, SJBIT

-copy files

Pag e 1 0

UNIX and Shell Programming

10CS44

W hen T hi ng s G o W ro n g
Terminals and keyboards have no uniform behavioral pattern. Terminal settings directly impact
the keyboard operation. If you observe a different behavior from that expected, when you press
certain keystrokes, it means that the terminal settings are different. In such cases, you should
know which keys to press to get the required behavior. The following table lists keyboard
commands to try when things go wrong.
Keystroke

Function

or
command
[Ctrl-h]

Erases text

[Ctrl-c] or

Interrupts a command

Delete
[Ctrl-d]

Terminates login session or a program that expects its input from


keyboard

[Ctrl-s]

Stops scrolling of screen output and locks keyboard

[Ctrl-q]

Resumes scrolling of screen output and unlocks keyboard

[Ctrl-u]

Kills command line without executing it

[Ctrl-\]

Kills running program but creates a core file containing the memory
image of the program

[Ctrl-z]

Suspends process and returns shell prompt; use fg to resume job

[Ctrl-j]

Alternative to [Enter]

[Ctrl-m]

Alternative to [Enter]

stty sane

Restores terminal to normal status

1.3.

The File System

Introduction
In this chapter we will look at the file system of UNIX. We also look at types of files their
significance. We then look at two ways of specifying a file viz., with absolute pathnames and

Dept. of CSE, SJBIT

Pag e 1 1

UNIX and Shell Programming

10CS44

relative pathnames. A discussion on commands used with directory files viz., cd, pwd, mkdir,
rmdir and ls will be made. Finally we look at some of the important directories contained under
UNIX file system.

Objectives
Types of files
UNIX Filenames
Directories and Files
Absolute and Relative Pathnames
pwd print working directory
cd change directory
mkdir make a directory
rmdir remove directory
The PATH environmental variable
ls list directory contents
The UNIX File System
Types of files
A simple description of the UNIX system is this:
On a UNIX system, everything is a file; if something is not a file, it is a process.
A UNIX system makes no difference between a file and a directory, since a directory is just a file
containing names of other files. Programs, services, texts, images, and so forth, are all files. Input
and output devices, and generally all devices, are considered to be files, according to the system.
Most files are just files, called regular files; they contain normal data, for example text files,
executable files or programs, input for or output from a program and so on.
While it is reasonably safe to suppose that everything you encounter on a UNIX system is a file,
there are some exceptions.
Directories: files that are lists of other files.
Special files or Device Files: All devices and peripherals are represented by files. To read or write
a device, you have to perform these operations on its associated file. Most special files are in
/dev.
Links: a system to make a file or directory visible in multiple parts of the system's file tree.
(Domain) sockets: a special file type, similar to TCP/IP sockets, providing inter-process
networking protected by the file system's access control.
Named pipes: act more or less like sockets and form a way for processes to communicate with
each other, without using network socket semantics.

Dept. of CSE, SJBIT

Pag e 1 2

UNIX and Shell Programming

10CS44

Ordinary (Regular) File


This is the most common file type. An ordinary file can be either a text file or a binary file.
A text file contains only printable characters and you can view and edit them. All C and Java
program sources, shell scripts are text files. Every line of a text file is terminated with the newline
character.
A binary file, on the other hand, contains both printable and nonprintable characters that cover the
entire ASCII range. The object code and executables that you produce by compiling C programs
are binary files. Sound and video files are also binary files.

Directory File
A directory contains no data, but keeps details of the files and subdirectories that it contains. A
directory file contains one entry for every file and subdirectory that it houses. Each entry has two
components namely, the filename and a unique identification number of the file or directory
(called the inode number).
When you create or remove a file, the kernel automatically updates its corresponding directory by
adding or removing the entry (filename and inode number) associated with the file.

Device File
All the operations on the devices are performed by reading or writing the file representing the
device. It is advantageous to treat devices as files as some of the commands used to access an
ordinary file can be used with device files as well.
Device filenames are found in a single directory structure, /dev. A device file is not really a
stream of characters. It is the attributes of the file that entirely govern the operation of the device.
The kernel identifies a device from its attributes and uses them to operate the device.

Filenames in UNIX
On a UNIX system, a filename can consist of up to 255 characters. Files may or may not have
extensions and can consist of practically any ASCII character except the / and the Null character.
You are permitted to use control characters or other nonprintable characters in a filename.
However, you should avoid using these characters while naming a file. It is recommended that
only the following characters be used in filenames:
Alphabets and numerals.
The period (.), hyphen (-) and underscore (_).
UNIX imposes no restrictions on the extension. In all cases, it is the application that imposes that
restriction. Eg. A C Compiler expects C program filenames to end with .c, Oracle requires SQL
scripts to have .sql extension.

Dept. of CSE, SJBIT

Pag e 1 3

UNIX and Shell Programming

10CS44

A file can have as many dots embedded in its name. A filename can also begin with or end with a
dot.
UNIX is case sensitive; cap01, Chap01 and CHAP01 are three different filenames that can
coexist in the same directory.

Directories and Files


A file is a set of data that has a name. The information can be an ordinary text, a user-written
computer program, results of a computation, a picture, and so on. The file name may consist of
ordinary characters, digits and special tokens like the underscore, except the forward slash (/). It
is permitted to use special tokens like the ampersand (&) or spaces in a filename.
Unix organizes files in a tree-like hierarchical structure, with the root directory, indicated
by a forward slash (/), at the top of the tree. See the Figure below, in which part of the hierarchy
of files and directories on the computer is shown.

Absolute and relative paths


A path, which is the way you need to follow in the tree structure to reach a given file, can be
described as starting from the trunk of the tree (the / or root directory). In that case, the path starts
with a slash and is called an absolute path, since there can be no mistake: only one file on the
system can comply.
Paths that don't start with a slash are always relative to the current directory. In relative paths we
also use the . and .. indications for the current and the parent directory.

The HOME variable


When you log onto the system, UNIX automatically places you in a directory called the home
directory. The shell variable HOME indicates the home directory of the user.
E.g.,

Dept. of CSE, SJBIT

Pag e 1 4

UNIX and Shell Programming

10CS44

$ echo $HOME
/home/kumar
What you see above is an absolute pathname, which is a sequence of directory names starting
from root (/). The subsequent slashes are used to separate the directories.

pwd - print working directory


At any time you can determine where you are in the file system hierarchy with the pwd, print
working directory, command,
E.g.,:
$ pwd
/home/frank/src

cd - change directory
You can change to a new directory with the cd, change directory, command. cd will accept both
absolute and relative path names.
Syntax
cd [directory]
Examples
cd

changes to user's home directory

cd /

changes directory to the system's root

cd ..

goes up one directory level

cd ../.. goes up two directory levels


cd /full/path/name/from/root changes directory to absolute path named
(note the leading slash)
cd path/from/current/location changes directory to path relative to current
location (no leading slash)

mkdir - make a directory


You extend your home hierarchy by making sub-directories underneath it. This is done with the
mkdir, make directory, command. Again, you specify either the full or relative path of the
directory.

Dept. of CSE, SJBIT

Pag e 1 5

UNIX and Shell Programming

10CS44

Examples
mkdir patch

Creates a directory patch under current directory

mkdir patch dbs doc

Creates three directories under current directory

mkdir pis pis/progs pis/data

Creates a directory tree with pis as a directory under


the current directory and progs and data as
subdirectories under pis

Note the order of specifying arguments in example 3. The parent directory should be specified
first, followed by the subdirectories to be created under it.
The system may refuse to create a directory due to the following reasons:
1. The directory already exists.
2. There may be an ordinary file by the same name in the current directory.
3. The permissions set for the current directory dont permit the creation of files and directories
by the user.

rmdir - remove directory


A directory needs to be empty before you can remove it. If its not, you need to remove the files
first. Also, you cant remove a directory if it is your present working directory; you must first
change out of that directory. You cannot remove a subdirectory unless you are placed in a
directory which is hierarchically above the one you have chosen to remove.

E.g.
rmdir patch

Directory must be empty

rmdir pis pis/progs pis/data

Shows error as pis is not empty. However rmdir


silently deletes the lower level subdirectories progs
and data.

The PATH environment variable


Environmental variables are used to provide information to the programs you use. We have
already seen one such variable called HOME.

Dept. of CSE, SJBIT

Pag e 1 6

UNIX and Shell Programming

10CS44

A command runs in UNIX by executing a disk file. When you specify a command like date, the
system will locate the associated file from a list of directories specified in the PATH variable and
then executes it. The PATH variable normally includes the current directory also.
Whenever you enter any UNIX command, you are actually specifying the name of an executable
file located somewhere on the system. The system goes through the following steps in order to
determine which program to execute:
1. Built in commands (such as cd and history) are executed within the shell.
2. If an absolute path name (such as /bin/ls) or a relative path name (such as ./myprog),
system executes the program from the specified directory.

t he

3. OtherwCSE the PATH variable is used.

ls - list directory contents


The command to list your directories and files is ls. With options it can provide information about
the size, type of file, permissions, dates of file creation, change and access.
Syntax
ls [options] [argument]
Common Options
When no argument is used, the listing will be of the current directory. There are many very useful
options for the ls command. A listing of many of them follows. When using the command, string
the desired options together preceded by "-".
-a Lists all files, including those beginning with a dot (.).
-d Lists only names of directories, not the files in the directory
-F Indicates type of entry with a trailing symbol: executables with *, directories with / and
symbolic links with @
-R Recursive list
-u Sorts filenames by last access time
-t Sorts filenames by last modification time
-i Displays inode number
-l Long listing: lists the mode, link information, owner, size, last modification (time). If the file is
a symbolic link, an arrow (-->) precedes the pathname of the linked-to file.

Dept. of CSE, SJBIT

Pag e 1 7

UNIX and Shell Programming

10CS44

The mode field is given by the -l option and consists of 10 characters. The first character is one
of the following:
CHARACTER

IF ENTRY IS A

directory

plain file

block-type special file

character-type special file

symbolic link

socket

The next 9 characters are in 3 sets of 3 characters each. They indicate the file access permissions:
the first 3 characters refer to the permissions for the user, the next three for the users in the Unix
group assigned to the file, and the last 3 to the permissions for other users on the system.
Designations are as follows:
r read permission
w write permission
x execute permission
- no permission
Examples
1. To list the files in a directory:
$ ls
2. To list all files in a directory, including the hidden (dot) files:
$ ls -a
3. To get a long listing:
$ ls -al
total 24
drwxr-sr-x 5 workshop acs 512 Jun 7 11:12 .
drwxr-xr-x 6 root sys 512 May 29 09:59 ..
-rwxr-xr-x 1 workshop acs 532 May 20 15:31 .cshrc

Dept. of CSE, SJBIT

Pag e 1 8

UNIX and Shell Programming

10CS44

-rw------- 1 workshop acs 525 May 20 21:29 .emacs


-rw------- 1 workshop acs 622 May 24 12:13 .history
-rwxr-xr-x 1 workshop acs 238 May 14 09:44 .login
-rw-r--r-- 1 workshop acs 273 May 22 23:53 .plan
-rwxr-xr-x 1 workshop acs 413 May 14 09:36 .profile
-rw------- 1 workshop acs 49 May 20 20:23 .rhosts
drwx------ 3 workshop acs 512 May 24 11:18 demofiles
drwx------ 2 workshop acs 512 May 21 10:48 frank
drwx------ 3 workshop acs 512 May 24 10:59 linda

The UNIX File System


The root directory has many subdirectories. The following table describes some of the
subdirectories contained under root.
Directory

Content

/bin

Common programs, shared by the system, the system administrator and the users.

/ de v

Contains references to all the CPU peripheral hardware, which are represented as files with
special properties.

/etc

Most important system configuration files are in /etc, this directory contains data similar to
those in the Control Panel in Windows

/home

Home directories of the common users.

/lib

Library files, includes files for all kinds of programs needed by the system and the users.

/sbin

Programs for use by the system and the system administrator.

/tmp

Temporary space for use by the system, cleaned upon reboot, so don't use this for saving any
work!

/usr
/var

Programs, libraries, documentation etc. for all user-related programs.


Storage for all variable files and temporary files created by users, such as log files, the mail
queue, the print spooler area, space for temporary storage of files downloaded from the
Internet, or to keep an image of a CD before burning it.

Dept. of CSE, SJBIT

Pag e 1 9

UNIX and Shell Programming

10CS44

UNIT 2
2.1. Basic File Attributes
The UNIX file system allows the user to access other files not belonging to them and without
infringing on security. A file has a number of attributes (properties) that are stored in the inode. In
this chapter, we discuss,

ls l to display file attributes (properties)


Listing of a specific directory
Ownership and group ownership
Different file permissions

Listing File Attributes


ls command is used to obtain a list of all filenames in the current directory. The output in
UNIX lingo is often referred to as the listing. Sometimes we combine this option with other
options for displaying other attributes, or ordering the list in a different sequence. ls look up the
files inode to fetch its attributes. It lists seven attributes of all files in the current directory and
they are:

File type and Permissions


Links
Ownership
Group ownership
File size
Last Modification date and time
File name

The file type and its permissions are associated with each file. Links indicate the number of
file names maintained by the system. This does not mean that there are so many copies of the file.
File is created by the owner. Every user is attached to a group owner. File size in bytes is
displayed. Last modification time is the next field. If you change only the permissions or
ownership of the file, the modification time remains unchanged. In the last field, it displays the
file name.
For example,
$ ls l
total 72
-rw-r--r--

1 kumar metal 19514 may 10 13:45 chap01

-rw-r--r--

1 kumar metal 4174 may 10 15:01 chap02

-rw-rw-rw-

1 kumar metal

Dept. of CSE, SJBIT

84 feb 12 12:30 dept.lst

Pag e 2 0

UNIX and Shell Programming


-rw-r--r--

10CS44

1 kumar metal 9156 mar 12 1999 genie.sh

drwxr-xr-x 2 kumar metal

512 may 9 10:31 helpdir

drwxr-xr-x 2 kumar metal

512 may 9 09:57 progs

Listing Directory Attributes


ls -d will not list all subdirectories in the current directory
For example,
ls ld helpdir progs
drwxr-xr-x 2 kumar metal

512 may 9 10:31 helpdir

drwxr-xr-x 2 kumar metal

512 may 9 09:57 progs

Directories are easily identified in the listing by the first character of the first column,
which here shows a d. The significance of the attributes of a directory differs a good deal from an
ordinary file. To see the attributes of a directory rather than the files contained in it, use ls ld
with the directory name. Note that simply using ls d will not list all subdirectories in the current
directory. Strange though it may seem, ls has no option to list only directories.

File Ownership
When you create a file, you become its owner. Every owner is attached to a group owner.
Several users may belong to a single group, but the privileges of the group are set by the owner of
the file and not by the group members. When the system administrator creates a user account, he
has to assign these parameters to the user:
The user-id (UID) both its name and numeric representation
The group-id (GID) both its name and numeric representation

File Permissions
UNIX follows a three-tiered file protection system that determines a files access rights.
It is displayed in the following format:
Filetype owner (rwx) groupowner (rwx) others (rwx)
For Example:
-rwxr-xr-- 1 kumar metal 20500 may 10 19:21 chap02
rwx
owner/user

Dept. of CSE, SJBIT

r-x
group owner

r-others

Pag e 2 1

UNIX and Shell Programming

10CS44

The first group has all three permissions. The file is readable, writable and executable by
the owner of the file. The second group has a hyphen in the middle slot, which indicates the
absence of write permission by the group owner of the file. The third group has the write and
execute bits absent. This set of permissions is applicable to others.
You can set different permissions for the three categories of users owner, group and
others. Its important that you understand them because a little learning here can be a dangerous
thing. Faulty file permission is a sure recipe for disaster

Changing File Permissions


A file or a directory is created with a default set of permissions, which can be determined
by umask. Let us assume that the file permission for the created file is -rw-r--r--. Using chmod
command, we can change the file permissions and allow the owner to execute his file. The
command can be used in two ways:
In a relative manner by specifying the changes to the current permissions
In an absolute manner by specifying the final permissions

Relative Permissions
chmod only changes the permissions specified in the command line and leaves the other
permissions unchanged. Its syntax is:
chmod category operation permission filename(s)
chmod takes an expression as its argument which contains:
user category (user, group, others)
operation to be performed (assign or remove a permission)
type of permission (read, write, execute)
Category

operation

permission

u - us e r

+ assign

r - read

g - group

- remove

w - write

o - others

= absolute

x - execute

a - all (ugo)
Let us discuss some examples:
Initially,
-rw-r--r--

Dept. of CSE, SJBIT

kumar

metal 1906 sep

23:38 xstart

Pag e 2 2

UNIX and Shell Programming

10CS44

chmod u+x xstart


-rwxr--r--

kumar

metal 1906 sep

23:38 xstart

The command assigns (+) execute (x) permission to the user (u), other permissions remain
unchanged.
chmod ugo+x xstart

or

chmod a+x xstart

or

chmod +x xstart
-rwxr-xr-x

kumar

metal 1906 sep

23:38 xstart

chmod accepts multiple file names in command line


chmod u+x note note1 note3
Let initially,
-rwxr-xr-x

1 kumar metal 1906 sep 23:38 xstart

chmod go-r xstart


Then, it becomes
-rwx--x--x

1 kumar metal 1906 sep 23:38 xstart

Absolute Permissions
Here, we need not to know the current file permissions. We can set all nine permissions
explicitly. A string of three octal digits is used as an expression. The permission can be
represented by one octal digit for each category. For each category, we add octal digits. If we
represent the permissions of each category by one octal digit, this is how the permission can be
represented:

Read permission 4 (octal 100)


Write permission 2 (octal 010)
Execute permission 1 (octal 001)

Octal

Permissions

Significance

---

no permissions

--x

execute only

-w-

write only

-wx

write and execute

Dept. of CSE, SJBIT

Pag e 2 3

UNIX and Shell Programming

10CS44

r--

read only

r-x

read and execute

rw-

read and write

rwx

read, write and execute

We have three categories and three permissions for each category, so three octal digits
can describe a files permissions completely. The most significant digit represents user and the
least one represents others. chmod can use this three-digit string as the expression.
Using relative permission, we have,
chmod a+rw xstart
Using absolute permission, we have,
chmod 666 xstart
chmod 644 xstart
chmod 761 xstart
will assign all permissions to the owner, read and write permissions for the group and only
execute permission to the others.
777 signify all permissions for all categories, but still we can prevent a file from being
deleted. 000 signifies absence of all permissions for all categories, but still we can delete a file. It
is the directory permissions that determine whether a file can be deleted or not. Only owner can
change the file permissions. User can not change other users files permissions. But the system
administrator can do anything.
The Security Implications
Let the default permission for the file xstart is
-rw-r--r-chmod u-rw, go-r xstart

or

chmod 000 xstart


---------This is simply useless but still the user can delete this file
On the other hand,
chmod a+rwx xstart

Dept. of CSE, SJBIT

Pag e 2 4

UNIX and Shell Programming

10CS44

chmod 777 xstart


-rwxrwxrwx
The UNIX system by default, never allows this situation as you can never have a secure system.
Hence, directory permissions also play a very vital role here
We can use chmod Recursively.
chmod -R a+x shell_scripts
This makes all the files and subdirectories found in the shell_scripts directory, executable by all
users. When you know the shell meta characters well, you will appreciate that the * doesnt match
filenames beginning with a dot. The dot is generally a safer but note that both commands change
the permissions of directories also.

Directory Permissions
It is possible that a file cannot be accessed even though it has read permission, and can be
removed even when it is write protected. The default permissions of a directory are,
rwxr-xr-x (755)
A directory must never be writable by group and others
Example:
mkdir c_progs
ls ld c_progs
drwxr-xr-x

2 kumar metal 512 may 9 09:57 c_progs

If a directory has write permission for group and others also, be assured that every user
can remove every file in the directory. As a rule, you must not make directories universally
writable unless you have definite reasons to do so.

Changing File Ownership


Usually, on BSD and AT&T systems, there are two commands meant to change the
ownership of a file or directory. Let kumar be the owner and metal be the group owner. If sharma
copies a file of kumar, then sharma will become its owner and he can manipulate the attributes
chown changing file owner and chgrp changing group owner
On BSD, only system administrator can use chown
On other systems, only the owner can change both

Dept. of CSE, SJBIT

Pag e 2 5

UNIX and Shell Programming

10CS44

chown
Changing ownership requires superuser permission, so use su command
ls -l note
-rwxr----x

1 kumar metal 347 may 10 20:30 note

chown sharma note; ls -l note


-rwxr----x

1 sharma metal 347 may 10 20:30 note

Once ownership of the file has been given away to sharma, the user file permissions that
previously applied to Kumar now apply to sharma. Thus, Kumar can no longer edit note since
there is no write privilege for group and others. He can not get back the ownership either. But he
can copy the file to his own directory, in which case he becomes the owner of the copy.
chgrp
This command changes the files group owner. No superuser permission is required.
ls l dept.lst
-rw-r--r--

1 kumar metal 139 jun 8 16:43 dept.lst


chgrp dba dept.lst; ls l dept.lst

-rw-r--r--

1 kumar dba 139 jun 8 16:43 dept.lst

In this chapter we considered two important file attributes permissions and ownership.
After we complete the first round of discussions related to files, we will take up the other file
attributes.

2.2. The vi Editor


To write and edit some programs and scripts, we require editors. UNIX provides vi editor for
BSD system created by Bill Joy. Bram Moolenaar improved vi editor and called it as vim (vi
improved) on Linux OS.

vi Basics
To add some text to a file, we invoke,
vi <filename>
In all probability, the file doesnt exist, and vi presents you a full screen with the filename
shown at the bottom with the qualifier. The cursor is positioned at the top and all remaining lines
of the screen show a ~. They are non-existent lines. The last line is reserved for commands that
you can enter to act on text. This line is also used by the system to display messages. This is the
command mode. This is the mode where you can pass commands to act on text, using most of the

Dept. of CSE, SJBIT

Pag e 2 6

UNIX and Shell Programming

10CS44

keys of the keyboard. This is the default mode of the editor where every key pressed is interpreted
as a command to run on text. You will have to be in this mode to copy and delete text
For, text editing, vi uses 24 out of 25 lines that are normally available in the terminal. To
enter text, you must switch to the input mode. First press the key i, and you are in this mode ready
to input text. Subsequent key depressions will then show up on the screen as text input.
After text entry is complete, the cursor is positioned on the last character of the last line.
This is known as current line and the character where the cursor is stationed is the current cursor
position. This mode is used to handle files and perform substitution. After the command is run,
you are back to the default command mode. If a word has been misspelled, use ctrl-w to erase the
entire word.
Now press esc key to revert to command mode. Press it again and you will hear a beep. A
beep in vi indicates that a key has been pressed unnecessarily. Actually, the text entered has not
been saved on disk but exists in some temporary storage called a buffer. To save the entered text,
you must switch to the execute mode (the last line mode). Invoke the execute mode from the
command mode by entering a: which shows up in the last line.

The Repeat Factor


vi provides repeat factor in command and input mode commands. Command mode
command k moves the cursor one line up. 10k moves cursor 10 lines up.
To undo whenever you make a mistake, press
Esc u
To clear the screen in command mode, press
ctrl-l
Dont use (caps lock) - vi commands are case-sensitive
Avoid using the PC navigation keys

Input Mode Entering and Replacing Text


It is possible to display the mode in which is user is in by typing,
:set showmode
Messages like INSERT MODE, REPLACE MODE, CHANGE MODE, etc will appear in the last
l i ne .
Pressing i changes the mode from command to input mode. To append text to the right of the
cursor position, we use a, text. I and A behave same as i and a, but at line extremes

Dept. of CSE, SJBIT

Pag e 2 7

UNIX and Shell Programming

10CS44

I inserts text at the beginning of line. A appends text at end of line.


below the current line

o opens a new line

r<letter> replacing a single character


s<text/word> replacing text with s
R<text/word> replacing text with R
Press esc key to switch to command mode after you have keyed in text

Some of the input mode commands are:


COMMAND

FUNCTION

inserts text

appends text

inserts at beginning of line

appends text at end of line

opens line below

opens line above

replaces a single character

replaces with a text

replaces entire line

Saving Text and Quitting The ex Mode


When you edit a file using vi, the original file is not distributed as such, but only a copy
of it that is placed in a buffer. From time to time, you should save your work by writing the buffer
contents to disk to keep the disk file current. When we talk of saving a file, we actually mean
saving this buffer. You may also need to quit vi after or without saving the buffer. Some of the
save and exit commands of the ex mode is:
Command

Action

:W

saves file and remains in editing mode

:x

saves and quits editing mode

:wq

saves and quits editing mode

:w <filename> save as
:w! <filename>

Dept. of CSE, SJBIT

save as, but overwrites existing file

Pag e 2 8

UNIX and Shell Programming

10CS44

:q

quits editing mode

:q!

quits editing mode by rejecting changes made

:sh

escapes to UNIX shell

:recover

recovers file from a crash

Navigation
A command mode command doesnt show up on screen but simply performs a function.
To move the cursor in four directions,
k

moves cursor up

moves cursor down

moves cursor left

moves cursor right

Word Navigation
Moving by one character is not always enough. You will often need to move faster along a
line. vi understands a word as a navigation unit which can be defined in two ways, depending on
the key pressed. If your cursor is a number of words away from your desired position, you can
use the word-navigation commands to go there directly. There are three basic commands:
b

moves back to beginning of word

moves forward to end of word

moves forward to beginning word

Example,
5b takes the cursor 5 words back
3w takes the cursor 3 words forward

Moving to Line Extremes


Moving to the beginning or end of a line is a common requirement.
To move to the first character of a line
0 or |
30| moves cursor to column 30

Dept. of CSE, SJBIT

Pag e 2 9

UNIX and Shell Programming

10CS44

$ moves to the end of the current line


The use of these commands along with b, e, and w is allowed

Scrolling
Faster movement can be achieved by scrolling text in the window using the control keys.
The two commands for scrolling a page at a time are
ctrl-f

scrolls forward

ctrl-b

scrolls backward

10ctrl-f scroll 10 pages and navigate faster


ctrl-d

scrolls half page forward

ctrl-u

scrolls half page backward

The repeat factor can also be used here.

Absolute Movement
The editor displays the total number of lines in the last line
Ctrl-g

to know the current line number

40G

goes to line number 40

1G

goes to line number 1

goes to end of file

Editing Text
The editing facilitates in vi are very elaborate and invoke the use of operators. They use
operators, such as,
d

delete

yank (copy)

Deleting Text
x

deletes a single character

dd

delete entire line

yy

copy entire line

6dd

deletes the current line and five lines below

Dept. of CSE, SJBIT

Pag e 3 0

UNIX and Shell Programming

10CS44

Moving Text
Moving text (p) puts the text at the new location.
p and P place text on right and left only when you delete parts of lines. But the same keys get
associated with below and above when you delete complete lines

Copying Text
Copying text (y and p) is achieved as,
yy
10yy

copies current line


copies current line & 9 lines below

Joining Lines
J
4J

to join the current line and the line following it


joins following 3 lines with current line

Undoing Last Editing Instructions


In command mode, to undo the last change made, we use
u
To discard all changes made to the current line, we use
U
vim (LINUX) lets you undo and redo multiple editing instructions. u behaves differently
here; repeated use of this key progressively undoes your previous actions. You could even have
the original file in front of you. Further 10u reverses your last 10 editing actions. The function of
U remains the same.
You may overshoot the desired mark when you keep u pressed, in which case use ctrl-r to
redo your undone actions. Further, undoing with 10u can be completely reversed with 10ctrl-r.
The undoing limit is set by the execute mode command: set undolevels=n, where n is set to 1000
by default.

Repeating the Last Command


The . (dot) command is used for repeating the last instruction in both editing and command mode
commands
For example:
2dd deletes 2 lines from current line and to repeat this operation, type. (dot)

Dept. of CSE, SJBIT

Pag e 3 1

UNIX and Shell Programming

10CS44

Searching for a Pattern


/ search forward
? search backward
/printf
The search begins forward to position the cursor on the first instance of the

word

?pattern
Searches backward for the most previous instance of the pattern

Repeating the Last Pattern Search


n

repeats search in same direction of original search

n doesnt necessarily repeat a search in the forward direction. The direction depends on
the search command used. If you used? printf to search in the reverse direction in the first place,
then n also follows the same direction. In that case, N will repeat the search in the forward
direction, and not n.

Search and repeat commands


Command
/pat

Function

searches forward for pattern pat

?pat searches backward for pattern pat


n

repeats search in same direction along which previous search was made

repeats search in direction opposite to that along which previous search was made

Substitution search and replace


We can perform search and replace in execute mode using :s. Its syntax is,
:address/source_pattern/target_pattern/flags
:1,$s/director/member/g can also use % instead of 1,$
:1,50s/unsigned//g

deletes unsigned everywhere in lines 1 to 50

:3,10s/director/member/g

substitute lines 3 through 10

:.s/director/member/g

only the current line

:$s/director/member/g

only the last line

Dept. of CSE, SJBIT

Pag e 3 2

UNIX and Shell Programming

10CS44

Interactive substitution: sometimes you may like to selectively replace a string. In that case, add
the c parameter as the flag at the end:
:1,$s/director/member/gc
Each line is selected in turn, followed by a sequence of carets in the next line, just below the
pattern that requires substitution. The cursor is positioned at the end of this caret sequence,
waiting for your response.
The ex mode is also used for substitution. Both search and replace operations also use
regular expressions for matching multiple patterns.
The features of vi editor that have been highlighted so far are good enough for a beginner
who should not proceed any further before mastering most of them. There are many more
functions that make vi a very powerful editor. Can you copy three words or even the entire file
using simple keystrokes? Can you copy or move multiple sections of text from one file to another
in a single file switch? How do you compile your C and Java programs without leaving the
editor? vi can do all this.

Dept. of CSE, SJBIT

Pag e 3 3

UNIX and Shell Programming

10CS44

UNIT 3
3.1. The Shell
Introduction
In this chapter we will look at one of the major component of UNIX architecture The Shell.
Shell acts as both a command interpreter as well as a programming facility. We will look at the
interpretive nature of the shell in this chapter.

Objectives

The Shell and its interpretive cycle


Pattern Matching The wild-cards
Escaping and Quoting
Redirection The three standard files
Filters Using both standard input and standard output
/dev/null and /dev/tty The two special files
Pipes
tee Creating a tee
Command Substitution
Shell Variables

The shell and its interpretive cycle


The shell sits between you and the operating system, acting as a command interpreter. It reads
your terminal input and translates the commands into actions taken by the system. The shell is
analogous to command.com in DOS. When you log into the system you are given a default shell.
When the shell starts up it reads its startup files and may set environment variables, command
search paths, and command aliases, and executes any commands specified in these files. The
original shell was the Bourne shell, sh. Every Unix platform will either have the Bourne shell, or
a Bourne compatible shell available.
Numerous other shells are available. Some of the more well known of these may be on your Unix
system: the Korn shell, ksh, by David Korn, C shell, csh, by Bill Joy and the Bourne Again
SHell, bash, from the Free Software Foundations GNU project, both based on sh, the T-C shell,
tcsh, and the extended C shell, cshe, both based on csh.
Even though the shell appears not to be doing anything meaningful when there is no activity at
the terminal, it swings into action the moment you key in something.
The following activities are typically performed by the shell in its interpretive cycle:

The shell issues the prompt and waits for you to enter a command.
After a command is entered, the shell scans the command line for metacharacters and
expands abbreviations (like the * in rm *) to recreate a simplified command line.
It then passes on the command line to the kernel for execution.

Dept. of CSE, SJBIT

Pag e 3 4

UNIX and Shell Programming

10CS44

The shell waits for the command to complete and normally cant do any work while the
command is running.
After the command execution is complete, the prompt reappears and the shell returns to
its waiting role to start the next cycle. You are free to enter another command.

Pattern Matching The Wild-Cards


A pattern is framed using ordinary characters and a metacharacter (like *) using well-defined
rules. The pattern can then be used as an argument to the command, and the shell will expand it
suitably before the command is executed.
The metacharacters that are used to construct the generalized pattern for matching filenames
belong to a category called wild-cards. The following table lists them:
Wild-Card

Matches

Any number of characters including none

A single character

[ijk]

A single character either an i, j or k

[x-z]

A single character that is within the ASCII range of characters x and x

[!ijk]

A single character that is not an i,j or k (Not in C shell)

[!x-z]

A single character that is not within the ASCII range of the characters x and x
(Not in C Shell)

{pat1,pat2}

Pat1, pat2, etc. (Not in Bourne shell)

Examples:
To list all files that begin with chap, use
$ ls chap*
To list all files whose filenames are six character long and start with chap, use
$ ls chap??
Note: Both * and ? operate with some restrictions. for example, the * doesnt match all files
beginning with a . (dot) ot the / of a pathname. If you wish to list all hidden filenames in your
directory having at least three characters after the dot, the dot must be matched explicitly.
$ ls .???*

Dept. of CSE, SJBIT

Pag e 3 5

UNIX and Shell Programming

10CS44

However, if the filename contains a dot anywhere but at the beginning, it need not be matched
explicitly.
Similarly, these characters dont match the / in a pathname. So, you cannot use
$ cd /usr?local to change to /usr/local.

The character class


You can frame more restrictive patterns with the character class. The character class comprCSEs
a
set of characters enclosed by the rectangular brackets, [ and ], but it matches a single character in
the class. The pattern [abd] is character class, and it matches a single character an a,b or d.
Examples:
$ls chap0[124]

Matches chap01, chap02, chap04 and lists if found.

$ ls chap[x-z]

Matches chapx, chapy, chapz and lists if found.

You can negate a character class to reverse a matching criteria. For example,
- To match all filenames with a single-character extension but not the .c ot .o files,
use *.[!co]
- To match all filenames that dont begin with an alphabetic character,
use [!a-zA-Z]*

Matching totally dissimilar patterns


This feature is not available in the Bourne shell. To copy all the C and Java source programs from
another directory, we can delimit the patterns with a comma and then put curly braces around
them.
$ cp $HOME/prog_sources/*.{c,java} .
The Bourne shell requires two separate invocations of cp to do this job.
$ cp /home/srm/{project,html,scripts/* .
The above command copies all files from three directories (project, html and scripts) to the
current directory.

Escaping and Quoting


Escaping is providing a \ (backslash) before the wild-card to remove (escape) its special meaning.
For instance, if we have a file whose filename is chap* (Remember a file in UNIX can be names
with virtually any character except the / and null), to remove the file, it is dangerous to give

Dept. of CSE, SJBIT

Pag e 3 6

UNIX and Shell Programming

10CS44

command as rm chap*, as it will remove all files beginning with chap. Hence to suppress the
special meaning of *, use the command rm chap\*
To list the contents of the file chap0[1-3], use
$ cat chap0\[1-3\]
A filename can contain a whitespace character also. Hence to remove a file named
My Documend.doc, which has a space embedded, a similar reasoning should be followed:
$ rm My\ Document.doc
Quoting is enclosing the wild-card, or even the entire pattern, within quotes. Anything within
these quotes (barring a few exceptions) are left alone by the shell and not interpreted.
When a command argument is enclosed in quotes, the meanings of all enclosed special characters
are turned off.
Examples:
$ rm chap*

Removes fil chap*

$ rm My Document.doc

Removes file My Document.doc

Redirection : The three standard files


The shell associates three files with the terminal two for display and one for the keyboard.
These files are streams of characters which many commands see as input and output. When a user
logs in, the shell makes available three files representing three streams. Each stream is associated
with a default device:
Standard input: The file (stream) representing input, connected to the keyboard.
Standard output: The file (stream) representing output, connected to the display.
Standard error: The file (stream) representing error messages that emanate from the command or
shell, connected to the display.
The standard input can represent three input sources:
The keyboard, the default source.
A file using redirection with the < symbol.
Another program using a pipeline.
The standard output can represent three possible destinations:
The terminal, the default destination.

Dept. of CSE, SJBIT

Pag e 3 7

UNIX and Shell Programming

10CS44

A file using the redirection symbols > and >>.


As input to another program using a pipeline.
A file is opened by referring to its pathname, but subsequent read and write operations identify
the file by a unique number called a file descriptor. The kernel maintains a table of file
descriptors for every process running in the system. The first three slots are generally allocated to
the three standard streams as,
0 Standard input
1 Standard output
2 Standard error
These descriptors are implicitly prefixed to the redirection symbols.
Examples:
Assuming file2 doesnt exist, the following command redirects the standard output to file
myOutput and the standard error to file myError.
$ ls l file1 file2 1>myOutput 2>myError
To redirect both standard output and standard error to a single file use:
$ ls l file1 file2 1>| myOutput 2>| myError OR
$ ls l file1 file2 1> myOutput 2>& 1

Filters: Using both standard input and standard output


UNIX commands can be grouped into four categories viz.,
1. Directory-oriented commands like mkdir, rmdir and cd, and basic file handling
commands like cp, mv and rm use neither standard input nor standard output.
2. Commands like ls, pwd, who etc. dont read standard input but they write to standard
output.
3. Commands like lp that read standard input but dont write to standard output.
4. Commands like cat, wc, cmp etc. that use both standard input and standard output.
Commands in the fourth category are called filters. Note that filters can also read directly from
files whose names are provided as arguments.
Example: To perform arithmetic calculations that are specified as expressions in input file calc.txt
and redirect the output to a file result.txt, use
$ bc < calc.txt > result.txt

Dept. of CSE, SJBIT

Pag e 3 8

UNIX and Shell Programming

10CS44

/dev/null and /dev/tty : Two special files


/dev/null: If you would like to execute a command but dont like to see its contents on the screen,
you may wish to redirect the output to a file called /dev/null. It is a special file that can accept any
stream without growing in size. Its size is always zero.
/dev/tty: This file indicates ones terminal. In a shell script, if you wish to redirect the output of
some select statements explicitly to the terminal. In such cases you can redirect these explicitly to
/dev/tty inside the script.

Pipes
With piping, the output of a command can be used as input (piped) to a subsequent command.
$ command1 | command2
Output from command1 is piped into input for command2.
This is equivalent to, but more efficient than:
$ command1 > temp
$ command2 < temp
$ rm temp
Examples
$ ls -al | more
$ who | sort | lpr

When a command needs to be ignorant of its source


If we wish to find total size of all C programs contained in the working directory, we can use the
command,
$ wc c *.c
However, it also shows the usage for each file(size of each file). We are not interested in
individual statistics, but a single figure representing the total size. To be able to do that, we must
make wc ignorant of its input source. We can do that by feeding the concatenated output stream
of all the .c files to wc c as its input:
$ cat *.c | wc c

Creating a tee

Dept. of CSE, SJBIT

Page 39

UNIX and Shell Programming

10CS44

tee is an external command that handles a character stream by duplicating its input. It saves one
copy in a file and writes the other to standard output. It is also a filter and hence can be placed
anywhere in a pipeline.
Example: The following command sequence uses tee to display the output of who and saves this
output in a file as well.
$ who | tee users.lst

Command substitution
The shell enables the connecting of two commands in yet another way. While a pipe enables a
command to obtain its standard input from the standard output of another command, the shell
enables one or more command arguments to be obtained from the standard output of another
command. This feature is called command substitution.
Example:
$ echo Current date and time is `date`
Observe the use of backquotes around date in the above command. Here the output of the
command execution of date is taken as argument of echo. The shell executes the enclosed
command and replaces the enclosed command line with the output of the command.
Similarly the following command displays the total number of files in the working directory.
$ echo There are `ls | wc l` files in the current directory
Observe the use of double quotes around the argument of echo. If you use single quotes, the
backquote is not interpreted by the shell if enclosed in single quotes.

Shell variables
Environmental variables are used to provide information to the programs you use. You can have
both global environment and local shell variables. Global environment variables are set by your
login shell and new programs and shells inherit the environment of their parent shell. Local shell
variables are used only by that shell and are not passed on to other processes. A child process
cannot pass a variable back to its parent process.
To declare a local shell variable we use the form variable=value (no spaces around =) and its
evaluation requires the $ as a prefix to the variable.
Example:
$ count=5
$ echo $count
5

Dept. of CSE, SJBIT

Pag e 4 0

UNIX and Shell Programming

10CS44

A variable can be removed with unset and protected from reassignment by readonly. Both are
shell internal commands.
Note: In C shell, we use set statement to set variables. Here, there either has to be whitespace on
both sides of the = or none at all.
$ set count=5
$ set size = 10

Uses of local shell variables


1. Setting pathnames: If a pathname is used several times in a script, we can assign it to a
variable and use it as an argument to any command.
2. Using command substitution: We can assign the result of execution of a command to a
variable. The command to be executed must be enclosed in backquotes.
3. Concatenating variables and strings: Two variables can be concatenated to form a new
variable.
Example: $ base=foo ; ext=.c
$

file=$base$ext

echo $file

// prints foo.c

3.2. The Process


Introduction
A process is an OS abstraction that enables us to look at files and programs as their time image.
This chapter discusses processes, the mechanism of creating a process, different states of a
process and also the ps command with its different options. A discussion on creating and
controlling background jobs will be made next. We also look at three commands viz., at, batch
and cron for scheduling jobs. This chapter also looks at nice command for specifying job priority,
signals and time command for getting execution time usage statistics of a command.

Objectives

Process Basics
ps: Process Status
Mechanism of Process Creation
Internal and External Commands
Process States and Zombies
Background Jobs
nice: Assigning execution priority
Processes and Signals
job Control
at and batch: Execute Later
cron command: Running Jobs Periodically
time: Timing Usage Statistics at process runtime

Dept. of CSE, SJBIT

Pag e 4 1

UNIX and Shell Programming

10CS44

Process Basics
UNIX is a multiuser and multitasking operating system. Multiuser means that several people can
use the computer system simultaneously (unlike a single-user operating system, such as MSDOS). Multitasking means that UNIX, like Windows NT, can work on several tasks concurrently;
it can begin work on one task and take up another before the first task is finished.
When you execute a program on your UNIX system, the system creates a special environment for
that program. This environment contains everything needed for the system to run the program as
if no other program were running on the system. Stated in other words, a process is created. A
process is a program in execution. A process is said to be born when the program starts execution
and remains alive as long as the program is active. After execution is complete, the process is said
t o di e .
The kernel is responsible for the management of the processes. It determines the time and
priorities that are allocated to processes so that more than one process can share the CPU
resources.
Just as files have attributes, so have processes. These attributes are maintained by the kernel in a
data structure known as process table. Two important attributes of a process are:
1. The Process-Id (PID): Each process is uniquely identified by a unique integer called the
PID, that is allocated by the kernel when the process is born. The PID can be used to
control a process.
2. The Parent PID (PPID): The PID of the parent is available as a process attribute.
There are three types of processes viz.,

1.
2.
3.

Interactive: Initiated by a shell and running in the foreground or background


batch: Typically a series of processes scheduled for execution at a specified point in time
daemon: Typically initiated at boot time to perform operating system functions on
demand, such as LPD, NFS, and DNS

The Shell Process


As soon as you log in, a process is set up by the kernel. This process represents the login shell,
which can be either sh(Bourne Shell), ksh(korn Shell), bash(Bourne Again Shell) or csh(C Shell).

Parents and Children


When you enter an external command at the prompt, the shell acts as the parent process, which in
turn starts the process representing the command entered. Since every parent has a parent, the
ultimate ancestry of any process can be traced back to the first process (PID 0) that is set up when
the system is booted. It is analogous to the root directory of the file system. A process can have
only one parent. However, a process can spawn multiple child processes.

Dept. of CSE, SJBIT

Pag e 4 2

UNIX and Shell Programming

10CS44

Wait or not Wait?


A parent process can have two approaches for its child:

It may wait for the child to die so that it can spawn the next process. The death of the
child is intimated to the parent by the kernel. Shell is an example of a parent that waits
for the child to terminate. However, the shell can be told not to wait for the child to
terminate.
It may not wait for the child to terminate and may continue to spawn other processes. init
process is an example of such a parent process.

ps: Process Status


Because processes are so important to getting things done, UNIX has several commands that
enable you to examine processes and modify their state. The most frequently used command is
ps, which prints out the process status for processes running on your system. Each system has a
slightly different version of the ps command, but there are two main variants, the System V
version (POSIX) and the Berkeley version. The following table shows the options available with
ps command.
POSIX

BSD

Significance

-f

Full listing showing PPID of each process

-e or A

a ux

All processes (user and system) processes

-u user

U user

Processes of user user only

-a

Processes of all users excluding processes not associated


with terminal

-l

Long listing showing memory related information

-t term

t term

Processes running on the terminal term

Examples
$ ps
PID TTY TIME

CMD

4245 pts/7 00:00:00 bash


5314 pts/7 00:00:00 ps

Dept. of CSE, SJBIT

Pag e 4 3

UNIX and Shell Programming

10CS44

The output shows the header specifying the PID, the terminal (TTY), the cumulative processor
time (TIME) that has been consumed since the process was started, and the process name (CMD).
$ ps -f
UID PID PPID C STIME TTY TIME COMMAND
root 14931 136 0 08:37:48 ttys0 0:00 rlogind
sartin 14932 14931 0 08:37:50 ttys0 0:00 -sh
sartin 15339 14932 7 16:32:29 ttys0 0:00 ps f
The header includes the following information:
UID Login name of the user
PID Process ID
PPID Parent process ID
C An index of recent processor utilization, used by kernel for scheduling
STIME Starting time of the process in hours, minutes and seconds
TTY Terminal ID number
TIME Cumulative CPU time consumed by the process
CMD The name of the command being executed

System processes (-e or A)


Apart from the processes a user generates, a number of system processes keep running all the
time. Most of them are not associated with any controlling terminal.
They are spawned during system startup and some of them start when the system goes into
multiuser mode. These processes are known as daemons because they are called without a
specific request from a user. To list them use,
$ ps e
PID

TTY TIME

CMD

0:34

41:55 init

23274 Console 0:03

sh

272

2:47

Dept. of CSE, SJBIT

sched

cron

Pag e 4 4

UNIX and Shell Programming


7015

10CS44

term/12 20:04 vi

Mechanism of Process Creation


There are three distinct phases in the creation of a process and uses three important system calls
viz., fork, exec, and wait. The three phases are discussed below:

Fork: A process in UNIX is created with the fork system call, which creates a copy of the
process that invokes it. The process image is identical to that of the calling process,
except for a few parameters like the PID. The child gets a new PID.
Exec: The forked child overwrites its own image with the code and data of the new
program. This mechanism is called exec, and the child process is said to exec a new
program, using one of the family of exec system calls. The PID and PPID of the execd
process remain unchanged.
Wait: The parent then executes the wait system call to wait for the child to complete. It
picks up the exit status of the child and continues with its other functions. Note that a
parent need not decide to wait for the child to terminate.
To get a better idea of this, let us explain with an example. When you enter ls to look at the
contents of your current working directory, UNIX does a series of things to create an environment
for ls and the run it:

The shell has UNIX perform a fork. This creates a new process that the shell will use to
run the ls program.
The shell has UNIX perform an exec of the ls program. This replaces the shell program
and data with the program and data for ls and then starts running that new program.
The ls program is loaded into the new process context, replacing the text and data of the
shell.
The ls program performs its task, listing the contents of the current directory. In the
meanwhile, the shell executes wait system call for ls to complete.

When a process is forked, the child has a different PID and PPID from its parent. However, it
inherits most of the attributes of the parent. The important attributes that are inherited are:

User name of the real and effective user (RUID and EUID): the owner of the process.
The real owner is the user issuing the command, the effective user is the one determining
access to system resources. RUID and EUID are usually the same, and the process has
the same access rights the issuing user would have.
Real and effective group owner (RGID and EGID): The real group owner of a process is
the primary group of the user who started the process. The effective group owner is
usually the same, except when SGID access mode has been applied to a file.
The current directory from where the process was run.
The file descriptors of all files opened by the parent process.
Environment variables like HOME, PATH.
The inheritance here means that the child has its own copy of these parameters and thus can alter
the environment it has inherited. But the modified environment is not available to the parent
process.

Dept. of CSE, SJBIT

Pag e 4 5

UNIX and Shell Programming

10CS44

H o w th e S he l l i s c r e a te d ?
init

getty
fork

shell

login
fork-exec

fork-exec

When the system moves to multiuser mode, init forks and execs a getty for every active
communication port.
Each one of these gettys prints the login prompt on the respective terminal and then goes off
to sleep.
When a user tries to log in, getty wakes up and fork-execs the login program to verify login
name and password entered.
On successful login, login for-execs the process representing the login shell.
init goes off to sleep, waiting for the children to terminate. The processes getty and login
overlay themselves.
When the user logs out, it is intimated to init, which then wakes up and spawns another getty
for that line to monitor the next login.

Internal and External Commands


From the process viewpoint, the shell recognizes three types of commands:
1. External commands: Commonly used commands like cat, ls etc. The shell creates a
process for each of these commands while remaining their parent.
2. Shell scripts: The shell executes these scripts by spawning another shell, which then
executes the commands listed in the script. The child shell becomes the parent of the
commands that feature in the shell.
3. Internal commands: When an internal command is entered, it is directly executed by the
shell. Similarly, variable assignment like x=5, doesnt generate a process either.
Note: Because the child process inherits the current working directory from its parent as one of
the environmental parameters, it is necessary for the cd command not to spawn a child to achieve
a change of directory. If this is allowed, after the child dies, control would revert to the parent and
the original directory would be restored. Hence, cd is implemented as an internal command.

Process States and Zombies


At any instance of time, a process is in a particular state. A process after creation is in the
runnable state. Once it starts running, it is in the running state. When a process requests for a
resource (like disk I/O), it may have to wait. The process is said to be in waiting or sleeping state.
A process can also be suspended by pressing a key (usually Ctrl-z).
When a process terminates, the kernel performs clean-up, assigns any children of the exiting
process to be adopted by init, and sends the death of a child signal to the parent process, and
converts the process into the zombie state.
A process in zombie state is not alive; it does not use any resources nor does any work. But it is
not allowed to die until the exit is acknowledged by the parent process.

Dept. of CSE, SJBIT

Pag e 4 6

UNIX and Shell Programming

10CS44

It is possible for the parent itself to die before the child dies. In such case, the child becomes an
orphan and the kernel makes init the parent of the orphan. When this adopted child dies, init
waits for its death.

Running Jobs in Background


The basic idea of a background job is simple. It's a program that can run without prompts or other
manual interaction and can run in parallel with other active processes.
Interactive processes are initialized and controlled through a terminal session. In other words,
there has to be someone connected to the system to start these processes; they are not started
automatically as part of the system functions. These processes can run in the foreground,
occupying the terminal that started the program, and you can't start other applications as long as
this process is running in the foreground.
There are two ways of starting a job in the background with the shells & operator and the
nohup command.

&: No Logging out


Ordinarily, when the shell runs a command for you, it waits until the command is completed.
During this time, you cannot communicate with the shell. You can run a command that takes a
long time to finish as a background job, so that you can be doing something else. To do this, use
the & symbol at the end of the command line to direct the shell to execute the command in the
background.
$ sort o emp.dat emp.dat &
[1] 1413

The jobs PID

Note:
1. Observe that the shell acknowledges the background command with two numbers. First
number [1] is the job ID of this command. The other number 1413 is the PID.
2. When you specify a command line in a pipeline to run in the background, all the
commands are run in the background, not just the last command.
3. The shell remains the parent of the background process.

nohup: Log out Safely


A background job executed using & operator ceases to run when a user logs out. This is because,
when you logout, the shell is killed and hence its children are also killed. The UNIX system
provides nohup statement which when prefixed to a command, permits execution of the process
even after the user has logged out. You must use the & with it as well.
The syntax for the nohup command is as follows:
nohup command-string [input-file] output-file &

Dept. of CSE, SJBIT

Pag e 4 7

UNIX and Shell Programming

10CS44

If you try to run a command with nohup and havent redirected the standard error, UNIX
automatically places any error messages in a file named nohup.out in the directory from which
the command was run.
In the following command, the sorted file and any error messages are placed in the file nohup.out.
$ nohup sort sales.dat &
1252
Sending output to nohup.out
Note that the shell has returned the PID (1252) of the process.
When the user logs out, the child turns into an orphan. The kernel handles such situations by
reassigning the PPID of the orphan to the systems init process (PID 1) - the parent of all shells.
When the user logs out, init takes over the parentage of any process run with nohup. In this way,
you can kill a parent (the shell) without killing its child.
Additional Points
When you run a command in the background, the shell disconnects the standard input from the
keyboard, but does not disconnect its standard output from the screen. So, output from the
command, whenever it occurs, shows up on screen. It can be confusing if you are entering
another command or using another program. Hence, make sure that both standard output and
standard error are redirected suitably.
$ find . name *.log print> log_file 2> err.dat &
OR

$ find . name *.log print> log_file 2> /dev/null &

Important:
1. You should relegate time-consuming or low-priority jobs to the background.
2. If you log out while a background job is running, it will be terminated.

nice: Job Execution with Low Priority


Processes in UNIX are sequentially assigned resources for execution. The kernel assigns the CPU
to a process for a time slice; when the time elapses, the process is places in a queue. How the
execution is scheduled depends on the priority assigned to the process.
The nice command is used to control background process dispatch priority.
The idea behind nice is that background jobs should demand less attention from the system than
interactive processes.

Dept. of CSE, SJBIT

Pag e 4 8

UNIX and Shell Programming

10CS44

Background jobs execute without a terminal attached and are usually run in the background for
two reasons:
1. the job is expected to take a relatively long time to finish, and
2. the job's results are not needed immediately.
Interactive processes, however, are usually shells where the speed of execution is critical because
it directly affects the system's apparent response time. It would therefore be nice for everyone
(others as well as you) to let interactive processes have priority over background work.
nice values are system dependent and typically range from 1 to 19.
A high nice value implies a lower priority. A program with a high nice number is friendly to other
programs, other users and the system; it is not an important job. The lower the nice number, the
more important a job is and the more resources it will take without sharing them.
Example:
$ nice wc l hugefile.txt
OR

$ nice wc l hugefile.txt &

The default nice value is set to 10.


We can specify the nice value explicitly with n number option where number is an offset to the
default. If the n number argument is present, the priority is incremented by that amount up to a
limit of 20.
Example:

$ nice n 5 wc l hugefile.txt &

Killing Processes with Signals


When you execute a command, one thing to keep in mind is that commands do not run in a
vacuum. Many things can happen during a command execution that are not under the control of
the command. The user of the command may press the interrupt key or send a kill command to
the process, or the controlling terminal may become disconnected from the system. In UNIX, any
of these events can cause a signal to be sent to the process. The default action when a process
receives a signal is to terminate.
When a process ends normally, the program returns its exit status to the parent. This exit status is
a number returned by the program providing the results of the program's execution.
Sometimes, you want or need to terminate a process.
The following are some reasons for stopping a process:

Its using too much CPU time.


Its running too long without producing the expected output.
Its producing too much output to the screen or to a disk file.
It appears to have locked a terminal or some other session.

Dept. of CSE, SJBIT

Pag e 4 9

UNIX and Shell Programming

10CS44

Its using the wrong files for input or output because of an operator or
programming error.

Its no longer useful.

If the process to be stopped is a background process, use the kill command to get out of these
situations. To stop a command that isnt in the background, press <ctrl-c>.
To use kill, use either of these forms:
kill PID(s)

OR

kill s NUMBER PID(s)

To kill a process whose PID is 123 use,


$ kill 123
To kill several processes whose PIDs are 123, 342, and 73 use,
$ kill 123 342 73
Issuing the kill command sends a signal to a process. The default signal is SIGTERM signal (15).
UNIX programs can send or receive more than 20 signals, each of which is represented by a
number. (Use kill l to list all signal names and numbers)
If the process ignores the signal SIGTERM, you can kill it with SIGKILL signal (9) as,
$ kill -9 123

OR

$ kill s KILL 123

The system variable $! stores the PID of the last background job. You can kill the last background
job without knowing its PID by specifying $ kill $!
Note: You can kill only those processes that you own; You cant kill processes of other
users. To kill all background jobs, enter kill 0.

Job Control
A job is a name given to a group of processes that is typically created by piping a series of
commands using pipeline character. You can use job control facilities to manipulate jobs. You
can use job control facilities to,
1. Relegate a job to the background (bg)
2. Bring it back to the foreground (fg)
3. List the active jobs (jobs)
4. Suspend a foreground job ([Ctrl-z])
5. Kill a job (kill)
The following examples demonstrate the different job control facilities.
Assume a process is taking a long time. You can suspend it by pressing [Ctrl-z].
[1] + Suspended

Dept. of CSE, SJBIT

wc l hugefile.txt

Pag e 5 0

UNIX and Shell Programming

10CS44

A suspended job is not terminated. You can now relegate it to background by,
$ bg
You can start more jobs in the background any time:
$ sort employee.dat > sortedlist.dat &
[2]

530

$ grep director emp.dat &


[3]

540

You can see a listing of these jobs using jobs command,


$ jobs
[3] + Running

grep director emp.dat &

[2] - Running

sort employee.dat > sortedlist.dat &

[1]

wc l hugefile.txt

Suspended

You can bring a job to foreground using fg %jobno OR fg %jobname as,


$ fg %2 OR

$ fg %sort

at And batch: Execute Later


UNIX provides facilities to schedule a job to run at a specified time of day. If the system load
varies greatly throughout the day, it makes sense to schedule less important jobs at a time when
the system load is low. The at and batch commands make such job scheduling possible.

at: One-Time Execution


To schedule one or more commands for a specified time, use the at command. With this
command, you can specify a time, a date, or both.
For example,
$ at 14:23 Friday
at> lp /usr/sales/reports/*
at> echo Files printed, Boss! | mail -sJob done boss
[Ctrl-d]
commands will be executed using /usr/bin/bash

Dept. of CSE, SJBIT

Pag e 5 1

UNIX and Shell Programming

10CS44

job 1041198880.a at Fri Oct 12 14:23:00 2007


The above job prints all files in the directory /usr/sales/reports and sends a user named boss some
mail announcing that the print job was done.
All at jobs go into a queue known as at queue.at shows the job number, the date and time of
scheduled execution. This job number is derived from the number of seconds elapsed since the
Epoch. A user should remember this job number to control the job.
$ at 1 pm today
at> echo ^G^GLunch with Director at 1 PM^G^G > /dev/term/43
The above job will display the following message on your screen (/dev/term/43) at 1:00 PM,
along with two beeps(^G^G).
Lunch with Director at 1 PM
To see which jobs you scheduled with at, enter at -l. Working with the preceding examples, you
may see the following results:
job 756603300.a at Tue Sep 11 01:00:00 2007
job 756604200.a at Fri Sep 14 14:23:00 2007
The following forms show some of the keywords and operations permissible with at command:
Schedules job at the hour (hh) and minute (mm) specified, using a

at hh:mm

24-hour clock
at hh:mm month day year

Schedules job at the hour (hh), minute (mm), month, day,


and year specified

at -l

Lists scheduled jobs

at now +count time-units

Schedules the job right now plus count number of


timeunits; time units can be minutes, hours, days, or weeks

at r job_id

Cancels the job with the job number matching job_id

batch: Execute in Batch Queue


The batch command lets the operating system decide an appropriate time to run a process. When
you schedule a job with batch, UNIX starts and works on the process whenever the system load
isnt too great.

Dept. of CSE, SJBIT

Pag e 5 2

UNIX and Shell Programming

10CS44

To sort a collection of files, print the results, and notify the user named boss that the job is done,
enter the following commands:
$ batch
sort /usr/sales/reports/* | lp
echo Files printed, Boss! | mailx -sJob done boss
The system returns the following response:
job 7789001234.b at Fri Sep 7 11:43:09 2007
The date and time listed are the date and time you pressed <Ctrl-d> to complete the batch
command. When the job is complete, check your mail; anything that the commands normally
display is mailed to you. Note that any job scheduled with batch command goes into a special at
queue.

cron: Running jobs periodically


cron program is a daemon which is responsible for running repetitive tasks on a regular schedule.
It is a perfect tool for running system administration tasks such as backup and system logfile
maintenance. It can also be useful for ordinary users to schedule regular tasks including calendar
reminders and report generation.
Both at and batch schedule commands on a one-time basis. To schedule commands or processes
on a regular basis, you use the cron (short for chronograph) program. You specify the times and
dates you want to run a command in crontab files. Times can be specified in terms of minutes,
hours, days of the month, months of the year, or days of the week.
cron is listed in a shell script as one of the commands to run during a system boot-up sequence.
Individual users dont have permission to run cron directly.
If theres nothing to do, cron goes to sleep and becomes inactive; it wakes up every minute,
however, to see if there are commands to run.
cron looks for instructions to be performed in a control file in
/var/spool/cron/crontabs
After executing them, it goes back to sleep, only to wake up the next minute.
To a create a crontab file,
First use an editor to create a crontab file say cron.txt
Next use crontab command to place the file in the directory containing crontab files.
crontab will create a file with filename same as user name and places it in
/var/spool/cron/crontabs directory.

Dept. of CSE, SJBIT

Pag e 5 3

UNIX and Shell Programming

10CS44

Alternately you can use crontab with e option.


You can see the contents of your crontab file with crontab l and remove them with crontab r.
The cron system is managed by the cron daemon. It gets information about which programs and
when they should run from the system's and users' crontab entries. The crontab files are stored in
the file /var/spool/cron/crontabs/<user> where <user> is the login-id of the user. Only the root
user has access to the system crontabs, while each user should only have access to his own
crontabs.

A typical entry in crontab file


A typical entry in the crontab file of a user will have the following format.
minute hour day-of-month month-of-year day-of-week command
where, Time-Field Options are as follows:
Field

Range

----------------------------------------------------------------------------------------------minute

00 through 59

hour

00 through 23 (midnight is 00)

day-of-month

01 through 31

Number of minutes after the hour

month-of-year 01 through 12
day-of-week

01 through 07 (Monday is 01, Sunday is 07)

----------------------------------------------------------------------------------------------The first five fields are time option fields. You must specify all five of these fields. Use an
asterisk (*) in a field if you want to ignore that field.
Examples:
00-10 17 * 3.6.9.12 5 find / -newer .last_time print >backuplist
In the above entry, the find command will be executed every minute in the first 10 minutes after 5
p.m. every Friday of the months March, June, September and December of every year.
30 07 * * 01 sort /usr/wwr/sales/weekly |mail -sWeekly Sales srm
In the above entry, the sort command will be executed with /usr/www/sales/weekly as argument
and the output is mailed to a user named srm at 7:30 a.m. each Monday.

time: Timing Processes


Dept. of CSE, SJBIT

Pag e 5 4

UNIX and Shell Programming

10CS44

The time command executes the specified command and displays the time usage on the terminal.
Example: You can find out the time taken to perform a sorting operation by preceding the sort
command with time.
$ time sort employee.dat > sortedlist.dat
real

0m29.811s

user

0m1.370s

sys

0m9.990s

where,
the real time is the clock elapsed from the invocation of the command until its termination.
the user time shows the time spent by the program in executing itself.
the sys time indicates the time used by the kernel in doing work on behalf of a user process.
The sum of user time and sys time actually represents the CPU time. This could be significantly
less than the real time on a heavily loaded system.

3.3.

Customizing the Environment

Introduction
The UNIX environment can be highly customized by manipulating the settings of the shell.
Commands can be made to change their default behavior, environment variables can be
redefined, the initialization scripts can be altered to obtain a required shell environment. This
chapter discusses different ways and approaches for customizing the environment.

Objectives

The Shell
Environment Variables
Common Environment Variables
Command Aliases (bash and korn)
Command History Facility (bash and korn)
In-Line Command Editing (bash and korn)
Miscellaneous Features (bash and korn)
The Initialization Scripts

The Shell
The UNIX shell is both an interpreter as well as a scripting language. An interactive shell turns
noninteractive when it executes a script.

Dept. of CSE, SJBIT

Pag e 5 5

UNIX and Shell Programming

10CS44

Bourne Shell This shell was developed by Steve Bourne. It is the original UNIX shell. It has
strong programming features, but it is a weak interpreter.
C Shell This shell was developed by Bill Joy. It has improved interpretive features, but it
wasnt suitable for programming.
Korn Shell This shell was developed by David Korn. It combines best features of the bourne
and C shells. It has features like aliases, command history. But it lacks some features of the C
shell.
Bash Shell This was developed by GNU. It can be considered as a superset that combined the
features of Korn and C Shells. More importantly, it conforms to POSIX shell specification.

Environment Variables
We already mentioned a couple of environment variables, such as PATH and HOME. Until now,
we only saw examples in which they serve a certain purpose to the shell. But there are many other
UNIX utilities that need information about you in order to do a good job.
What other information do programs need apart from paths and home directories? A lot of
programs want to know about the kind of terminal you are using; this information is stored in the
TERM variable. The shell you are using is stored in the SHELL variable, the operating system
type in OS and so on. A list of all variables currently defined for your session can be viewed
entering the env command.
The environment variables are managed by the shell. As opposed to regular shell variables,
environment variables are inherited by any program you start, including another shell. New
processes are assigned a copy of these variables, which they can read, modify and pass on in turn
to their own child processes.
The set statement display all variables available in the current shell, but env command displays
only environment variables. Note than env is an external command and runs in a child process.
There is nothing special about the environment variable names. The convention is to use
uppercase letters for naming one.

The Common Environment Variables


The following table shows some of the common environment variables.
Variable name
HISTSIZE

Stored information
size of the shell history file in number of lines

HOME

path to your home directory

HOSTNAME

local host name

LOGNAME

login name

MAIL
MANPATH

location of your incoming mail folder


paths to search for man pages

Dept. of CSE, SJBIT

Pag e 5 6

UNIX and Shell Programming

10CS44

PATH

search paths for commands

PS1
PS2

primary prompt
secondary prompt

PWD
SHELL

present working directory


current shell

TERM
UID

terminal type
user ID

USER
MAILCHECK
CDPATH

Login name of user


Mail checking interval for incoming mail
List of directories searched by cd when used with a non-absolute pathname

We will now describe some of the more common ones.


The command search path (PATH): The PATH variable instructs the shell about the route it
should follow to locate any executable command.
Your home directory (HOME): When you log in, UNIX normally places you in a directory
named after your login name. This is called the home directory or login directory. The home
directory for a user is set by the system administrator while creating users (using useradd
command).
mailbox location and checking (MAIL and MAILCHECK): The incoming mails for a user are
generally stored at /var/mail or /var/spool/mail and this location is available in the environment
variable MAIL. MAILCHECK determines how often the shell checks the file for arrival of new
mail.
The prompt strings (PS1, PS2): The prompt that you normally see (the $ prompt) is the shells
primary prompt specified by PS1. PS2 specifies the secondary prompt (>). You can change the
prompt by assigning a new value to these environment variables.
Shell used by the commands with shell escapes (SHELL): This environment variable specifies
the login shell as well as the shell that interprets the command if preceded with a shell escape.

Variables used in Bash and Korn


The Bash and korn prompt can do much more than displaying such simple information as your
user name, the name of your machine and some indication about the present working directory.
Some examples are demonstrated next.
$ PS1=[PWD]
[/home/srm] cd progs
[/home/srm/progs] _

Dept. of CSE, SJBIT

Pag e 5 7

UNIX and Shell Programming

10CS44

Bash and Korn also support a history facility that treats a previous command as an event and
associates it with a number. This event number is represented as !.
$ PS1=[!]

$ PS1=[! $PWD]

[42] _

[42 /home/srm/progs] _

$ PS1=\h>

// Host name of the machine

saturn> _

Aliases
Bash and korn support the use of aliases that let you assign shorthand names to frequently used
commands. Aliases are defined using the alias command. Here are some typical aliases that one
may like to use:

alias lx='/usr/bin/ls -lt'


alias l='/usr/bin/ls -l'
You can also use aliasing to redefine an existing command so it is always invoked with certain
options. For example:
alias cp=cp i
alias rm=rm i
Note that to execute the original external command, you have to precede the command with a \.
This means that you have to use \cp file1 file2 to override the alias.
The alias command with a argument displays its alias definition, if defined. The same command
without any arguments displays all aliases and to unset an alias use unalias statement. To unset
the alias cp, use unalias cp

Command History
Bash and Korn support a history feature that treats a previous command as an event and
associates it with an event number. Using this number you can recall previous commands, edit
them if required and reexecute them.
The history command displays the history list showing the event number of every previously
executed command. With bash, the complete history list is displayed, while with korn, the last 16
commands. You can specify a numeric argument to specify the number of previous commands to
display, as in, history 5 (in bash) or history -5 (korn).

Dept. of CSE, SJBIT

Pag e 5 8

UNIX and Shell Programming

10CS44

By default, bash stores all previous commands in $HOME/.bash_history and korn stores them in
$HOME/.sh_history. When a command is entered and executed, it is appended to the list
maintained in the file.

Accessing previous commands by Event Numbers (! and r)


The ! symbol (r in korn) is used to repeat previous commands. The following examples
demonstrate the use of this symbol with corresponding description.
$ !38

The command with event number 38 is displayed and executed (Use r 38 in korn)

$ !38:p

The command is displayed. You can edit and execute it

$ !!

Repeats previous command (Use r in korn)

$ !-2

Executes command prior to the previous one ( r -2 in korn)

Executing previous commands by Context


When you dont remember the event number of a command but know that the command started
with a specific letter of a string, you can use the history facility with context.
Example: $ !v

Repeats the last command beginning with v (r v in korn)

Substitution in previous commands


If you wish to execute a previous command after some changes, you can substitute the old string
with new one by substitution.
If a previous command cp progs/*.doc backup is to be executed again with doc replaced with txt,
$ !cp:s/doc/txt

in bash

$ r cp doc=txt

in korn

$_ is a shorthand feature to represent the directory used by the previous command.


$ mkdir progs
Now, instead of using cd progs, you can use,
$ c d $_

The History Variables


The command history will be maintained in default history files viz.,
.bash_history in Bash
.sh_history in Korn

Dept. of CSE, SJBIT

Pag e 5 9

UNIX and Shell Programming

10CS44

Variable HISTFILE determines the filename that saves the history list. Bash uses two variables
HISTSIZE for setting the size of the history list in memory and HISTFILESIZE for setting the
size of disk file. Korn uses HISTSIZE for both the purposes.

In-Line Command Editing


One of the most attractive aspects of bash and korn shells is their treatment of command line
editing. In addition to viewing your previous commands and reexecuting them, these shells let
you edit your current command line, or any of the commands in your history list, using a special
command line version of vi text editor. We have already seen the features of vi as a text editor
and these features can be used on the current command line, by making the following setting:
set o vi
Command line editing features greatly enhance the value of the history list. You can use them to
correct command line errors and to save time and effort in entering commands by modifying
previous commands. It also makes it much easier to search through your command history list,
because you can use the same search commands you use in vi.

Miscellaneous Features (bash and korn)

1. Using set o

The set statement by default displays the variables in the current shell, but in Bash and Korn, it
can make several environment settings with o option.
File Overwriting(noclobber): The shells > symbol overwrites (clobbers) an existing file, and o
prevent such accidental overwriting, use the noclobber argument:
set o noclobber
Now, if you redirect output of a command to an existing file, the shell will respond with a
message that says it cannot overwrite existing file or file already exists. To override this
protection, use the | after the > as in,
head n 5 emp.dat >| file1
Accidental Logging out (ignoreeof): The [Ctrl-d] key combination has the effect of terminating
the standard input as well as logging out of the system. In case you accidentally pressed [Ctrl-d]
twice while terminating the standard input, it will log you off! The ignoreeof keyword offers
protection from accidental logging out:
set o ignoreeof
But note that you can logout only by using exit command.
A set option is turned off with set +o keyword. To reverse the noclobber feature, use
set +o noclobber

Dept. of CSE, SJBIT

Pag e 6 0

UNIX and Shell Programming

10CS44

2. Tilde Substitution

The ~ acts as a shorthand representation for the home directory. A configuration file like .profile
that exists in the home directory can be referred to both as $HOME/.profile and ~/.profile.
You can also toggle between the directory you switched to most recently and your current
directory. This is done with the ~- symbols (or simply -, a hyphen). For example, either of the
following commands change to your previous directory:
cd ~ -

OR

cd

The Initialization Scripts


The effect of assigning values to variables, defining aliases and using set options is applicable
only for the login session; they revert to their default values when the user logs out. To make
them permanent, use certain startup scripts. The startup scripts are executed when the user logs in.
The initialization scripts in different shells are listed below:
.profile (Bourne shell)
.profile and .kshrc (Korn shell)
.bash_profile (or .bash_login) and .bashrc (Bash)
.login and .cshrc (C shell)

The Profile
When logging into an interactive login shell, login will do the authentication, set the environment
and start your shell. In the case of bash, the next step is reading the general profile from /etc, if
that file exists. bash then looks for ~/.bash_profile, ~/.bash_login and ~/.profile, in that order, and
reads and executes commands from the first one that exists and is readable. If none exists,
/etc/bashrc is applied.
When a login shell exits, bash reads and executes commands from the file, ~/.bash_logout, if it
exists.
The profile contains commands that are meant to be executed only once in a session. It can also
be used to customize the operating environment to suit user requirements. Every time you change
the profile file, you should either log out and log in again or You can execute it by using a special
command (called dot).
$ . .profile

The rc File
Normally the profiles are executed only once, upon login. The rc files are designed to be executed
every time a separate shell is created. There is no rc file in Bourne, but bash and korn use one.
This file is defined by an environment variable BASH_ENV in Bash and ENV in Korn.

Dept. of CSE, SJBIT

Pag e 6 1

UNIX and Shell Programming

10CS44

export BASH_ENV=$HOME/.bashrc
export ENV=$HOME/.kshrc
Korn automatically executes .kshrc during login if ENV is defined. Bash merely ensures that a
sub-shell executes this file. If the login shell also has to execute this file then a separate entry
must be added in the profile:
. ~/.bashrc
The rc file is used to define command aliases, variable settings, and shell options. Some sample
entries of an rc file are
alias cp=cp i
alias rm=rm i
set o noclobber
set o ignoreeof
set o vi
The rc file will be executed after the profile. However, if the BASH_ENV or ENV variables are
not set, the shell executes only the profile.

Dept. of CSE, SJBIT

Pag e 6 2

UNIX and Shell Programming

10CS44

UNIT 4
4.1. MORE FILE ATTRIBUTES
Apart from permissions and ownership, a UNIX file has several other attributes, and in
this chapter, we look at most of the remaining ones. A file also has properties related to its time
stamps and links. It is important to know how these attributes are interpreted when applied to a
directory or a device.
This chapter also introduces the concepts of file system. It also looks at the inode, the
lookup table that contained almost all file attributes. Though a detailed treatment of the file
systems is taken up later, knowledge of its basics is essential to our understanding of the
significance of some of the file attributes. Basic file attributes has helped us to know about - ls l
to display file attributes (properties), listing of a specific directory, ownership and group
ownership and different file permissions. ls l provides attributes like permissions, links, owner,
group owner, size, date and the file name.
File Systems and inodes
The hard disk is split into distinct partitions, with a separate file system in each partition.
Every file system has a directory structure headed by root.
n partitions = n file systems = n separate root directories
All attributes of a file except its name and contents are available in a table inode (index
node), accessed by the inode number. The inode contains the following attributes of a file:

File type
File permissions
Number of links
The UID of the owner
The GID of the group owner
File size in bytes
Date and time of last modification
Date and time of last access
Date and time of last change of the inode
An array of pointers that keep track of all disk blocks used by the file

Please note that, neither the name of the file nor the inode number is stored in the inode. To know
inode number of a file:
ls -il tulec05
9059 -rw-r--r-- 1 kumar metal 51813 Jan 31 11:15 tulec05
Where, 9059 is the inode number and no other file can have the same inode number in the same
file system.

Dept. of CSE, SJBIT

Pag e 6 3

UNIX and Shell Programming

10CS44

Hard Links
The link count is displayed in the second column of the listing. This count is normally 1, but the
following files have two links,
-rwxr-xr-- 2 kumar metal 163 Jull 13 21:36 backup.sh
-rwxr-xr-- 2 kumar metal 163 Jul 13 21:36 restore.sh
All attributes seem to be identical, but the files could still be copies. Its the link count that seems
to suggest that the files are linked to each other. But this can only be confirmed by using the i
option to ls.
ls -li backup.sh restore.sh
478274 -rwxr-xr-- 2 kumar metal163 jul 13 21:36 backup.sh
478274 -rwxr-xr-- 2 kumar metal163 jul 13 21:36 restore.sh

ln: Creating Hard Links


A file is linked with the ln command which takes two filenames as arguments (cp
command). The command can create both a hard link and a soft link and has syntax similar to the
one used by cp. The following command links emp.lst with employee:
ln emp.lst employee
The i option to ls shows that they have the same inode number, meaning that they are
actually one end the same file:
ls -li emp.lst employee
29518 -rwxr-xr-x 2 kumar metal 915 may 4 09:58 emp.lst
29518 -rwxr-xr-x 2 kumar metal 915 may 4 09:58 employee
The link count, which is normally one for unlinked files, is shown to be two. You can
increase the number of links by adding the third file name emp.dat as:
ln employee emp.dat ; ls -l emp*
29518 -rwxr-xr-x 3 kumar metal 915 may 4 09:58 emp.dat
29518 -rwxr-xr-x 3 kumar metal 915 may 4 09:58 emp.lst
29518 -rwxr-xr-x 3 kumar metal 915 may 4 09:58 employee
You can link multiple files, but then the destination filename must be a directory. A file is
considered to be completely removed from the file system when its link count drops to zero. ln

Dept. of CSE, SJBIT

Pag e 6 4

UNIX and Shell Programming

10CS44

returns an error when the destination file exists. Use the f option to force the removal of the
existing link before creation of the new one

Where to use Hard Links


ln data/ foo.txt input_files
It creates link in directory input_files. With this link available, your existing programs
will continue to find foo.txt in the input_files directory. It is more convenient to do this that
modifies all programs to point to the new path. Links provide some protection against accidental
deletion, especially when they exist in different directories. Because of links, we dont need to
maintain two programs as two separate disk files if there is very little difference between them. A
files name is available to a C program and to a shell script. A single file with two links can have
its program logic make it behave in two different ways depending on the name by which it is
called.
We cant have two linked filenames in two file systems and we cant link a directory
even within the same file system. This can be solved by using symbolic links (soft links).

Symbolic Links
Unlike the hard linked, a symbolic link doesnt have the files contents, but simply
provides the pathname of the file that actually has the contents.
ln -s note note.sym
ls -li note note.sym
9948 -rw-r--r-- 1 kumar group 80 feb 16 14:52 note
9952 lrwxrwxrwx 1 kumar group 4 feb16 15:07note.sym ->note
Where, l indicate symbolic link file category. -> indicates note.sym contains the pathname for the
filename note. Size of symbolic link is only 4 bytes; it is the length of the pathname of note.
Its important that this time we indeed have two files, and they are not identical.
Removing note.sym wont affect us much because we can easily recreate the link. But if we
remove note, we would lose the file containing the data. In that case, note.sym would point to a
nonexistent file and become a dangling symbolic link.
Symbolic links can also be used with relative pathnames. Unlike hard links, they can also
span multiple file systems and also link directories. If you have to link all filenames in a directory
to another directory, it makes sense to simply link the directories. Like other files, a symbolic link
has a separate directory entry with its own inode number. This means that rm can remove a
symbolic link even if its points to a directory.
A symbolic link has an inode number separate from the file that it points to. In most
cases, the pathname is stored in the symbolic link and occupies space on disk. However, Linux

Dept. of CSE, SJBIT

Pag e 6 5

UNIX and Shell Programming

10CS44

uses a fast symbolic link which stores the pathname in the inode itself provided it doesnt exceed
60 characters.

The Directory
A directory has its own permissions, owners and links. The significance of the file
attributes change a great deal when applied to a directory. For example, the size of a directory is
in no way related to the size of files that exists in the directory, but rather to the number of files
housed by it. The higher the number of files, the larger the directory size. Permission acquires a
different meaning when the term is applied to a directory.
ls -l -d progs
drwxr-xr-x 2 kumar metal 320 may 9 09:57 progs
The default permissions are different from those of ordinary files. The user has all
permissions, and group and others have read and execute permissions only. The permissions of a
directory also impact the security of its files. To understand how that can happen, we must know
what permissions for a directory really mean.

Read permission
Read permission for a directory means that the list of filenames stored in that directory is
accessible. Since ls reads the directory to display filenames, if a directorys read permission is
removed, ls wont work. Consider removing the read permission first from the directory progs,
ls -ld progs
drwxr-xr-x 2 kumar metal 128 jun 18 22:41 progs
chmod -r progs ; ls progs
progs: permission denied

Write permission
We cant write to a directory file. Only the kernel can do that. If that were possible, any
user could destroy the integrity of the file system. Write permission for a directory implies that
you are permitted to create or remove files in it. To try that out, restore the read permission and
remove the write permission from the directory before you try to copy a file to it.
chmod 555 progs ; ls ld progs
dr-xr-xr-x 2 kumar metal 128 jun 18 22:41 progs
cp emp.lst progs
cp: cannot create progs/emp.lst: permission denied

Dept. of CSE, SJBIT

Pag e 6 6

UNIX and Shell Programming

10CS44

The write permission for a directory determines whether we can create or remove files in
it because these actions modify the directory
Whether we can modify a file depends on whether the file itself has write permission.
Changing a file doesn't modify its directory entry

Execute permission
If a single directory in the pathname doesnt have execute permission, then it cant be
searched for the name of the next directory. Thats why the execute privilege of a directory is
often referred to as the search permission. A directory has to be searched for the next directory, so
the cd command wont work if the search permission for the directory is turned off.
chmod 666 progs ; ls ld progs
drw-rw-rw- 2 kumar metal 128 jun 18 22:41 progs
cd progs
permission denied to search and execute it

umask: DEFAULT FILE AND DIRECTORY PERMISSIONS


When we create files and directories, the permissions assigned to them depend on the
systems default setting. The UNIX system has the following default permissions for all files and
directories.
rw-rw-rw- (octal 666) for regular files
rwxrwxrwx (octal 777) for directories
The default is transformed by subtracting the user mask from it to remove one or more
permissions. We can evaluate the current value of the mask by using umask without arguments,
$ umask
022
This becomes 644 (666-022) for ordinary files and 755 (777-022) for directories umask 000. This
indicates, we are not subtracting anything and the default permissions will remain unchanged.
Note that, changing system wide default permission settings is possible using chmod but not by
umask

MODIFICATION AND ACCESS TIMES


A UNIX file has three time stamps associated with it. Among them, two are:

Time of last file modification


Time of last access

Dept. of CSE, SJBIT

ls -l
ls lu

Pag e 6 7

UNIX and Shell Programming

10CS44

The access time is displayed when ls -l is combined with the -u option. Knowledge of files
modification and access times is extremely important for the system administrator. Many of the
tools used by them look at these time stamps to decide whether a particular file will participate in
a backup or not.

TOUCH COMMAND changing the time stamps


To set the modification and access times to predefined values, we have,
touch options expression filename(s)
touch emp.lst (without options and expression)
Then, both times are set to the current time and creates the file, if it doesnt exist.
touch command (without options but with expression) can be used. The expression consists of
MMDDhhmm (month, day, hour and minute).
touch 03161430 emp.lst ; ls -l emp.lst
-rw-r--r-- 1 kumar metal 870 mar 16 14:30 emp.lst
ls -lu emp.lst
-rw-r--r-- 1 kumar metal 870 mar 16 14:30 emp.lst
It is possible to change the two times individually. The m and a options change the
modification and access times, respectively:
touch command (with options and expression)
-m for changing modification time
-a for changing access time
touch -m 02281030 emp.lst ; ls -l emp.lst
-rw-r--r-- 1 kumar metal 870 feb 28 10:30 emp.lst
touch -a 01261650 emp.lst ; ls -lu emp.lst
-rw-r--r-- 1 kumar metal 870 jan 26 16:50 emp.lst

find : locating files


It recursively examines a directory tree to look for files matching some criteria, and then
takes some action on the selected files. It has a difficult command line, and if you have ever
wondered why UNIX is hated by many, then you should look up the cryptic find documentation.
How ever, find is easily tamed if you break up its arguments into three components:

Dept. of CSE, SJBIT

Pag e 6 8

UNIX and Shell Programming


find path_list

10CS44
selecton_criteria

action

where,

Recursively examines all files specified in path_list


It then matches each file for one or more selection-criteria
It takes some action on those selected files

The path_list comprCSEs one or more subdirectories separated by white space. There can also be
a
host of selection_criteria that you use to match a file, and multiple actions to dispose of the file.
This makes the command difficult to use initially, but it is a program that every user must master
since it lets him make file selection under practically any condition.

4.2. SIMPLE FILTERS


Filters are the commands which accept data from standard input manipulate it and write
the results to standard output. Filters are the central tools of the UNIX tool kit, and each filter
performs a simple function. Some commands use delimiter, pipe (|) or colon (:). Many filters
work well with delimited fields, and some simply wont work without them. The piping
mechanism allows the standard output of one filter serve as standard input of another. The filters
can read data from standard input when used without a filename as argument, and from the file
otherwCSE

The Simple Database


Several UNIX commands are provided for text editing and shell programming. (emp.lst) each line of this file has six fields separated by five delimiters. The details of an employee are
stored in one single line. This text file designed in fixed format and containing a personnel
database. There are 15 lines, where each field is separated by the delimiter |.
$ cat emp.lst
2233 | a.k.shukla | g.m | sales | 12/12/52 | 6000
9876 | jai sharma | director | production | 12/03/50 | 7000
5678 | sumit chakrobarty | d.g.m. | marketing | 19/04/43 | 6000
2365 | barun sengupta | director | personnel | 11/05/47 | 7800
5423 | n.k.gupta | chairman | admin | 30/08/56 | 5400
1006 | chanchal singhvi | director | sales | 03/09/38 | 6700
1265 | s.n. dasgupta | manager | sales | 12/09/63 | 5600
4290 | jayant choudhury | executive | production | 07/09/50 | 6000

Dept. of CSE, SJBIT

Pag e 6 9

UNIX and Shell Programming

10CS44

2476 | anil aggarwal | manager | sales | 01/05/59 | 5000


6521 | lalit chowdury | directir | marketing | 26/09/45 | 8200
3212 | shyam saksena | d.g.m. | accounts | 12/12/55 | 6000
3564 | sudhir agarwal | executive | personnel | 06/07/47 | 7500
2345 | j. b. sexena | g.m. | marketing | 12/03/45 | 8000
0110 | v.k.agrawal | g.m.| marketing | 31/12/40 | 9000

pr : paginating files
We know that,
cat dept.lst
01|accounts|6213
02|progs|5423
03|marketing|6521
04|personnel|2365
05|production|9876
06|sales|1006
pr command adds suitable headers, footers and formatted text. pr adds five lines of margin at the
top and bottom. The header shows the date and time of last modification of the file along with the
filename and page number.
pr dept.lst
May 06 10:38 1997 dept.lst page 1
01:accounts:6213
02:progs:5423
03:marketing:6521
04:personnel:2365
05:production:9876
06:sales:1006
blank lines

Dept. of CSE, SJBIT

Pag e 7 0

UNIX and Shell Programming

10CS44

pr options
The different options for pr command are:
-k prints k (integer) columns
-t to suppress the header and footer
-h to have a header of users choice
-d double spaces input
-n will number each line and helps in debugging
-on offsets the lines by n spaces and increases left margin of page
pr +10 chap01
starts printing from page 10
pr -l 54 chap01
this option sets the page length to 54

head displaying the beginning of the file


The command displays the top of the file. It displays the first 10 lines of the file, when
used without an option.
head emp.lst
-n to specify a line count
head -n 3 emp.lst
will display the first three lines of the file.

tail displaying the end of a file


This command displays the end of the file. It displays the last 10 lines of the file, when
used without an option.
tail emp.lst
-n to specify a line count
tail -n 3 emp.lst
displays the last three lines of the file. We can also address lines from the beginning of
the file instead of the end. The +count option allows to do that, where count represents the line
number from where the selection should begin.

Dept. of CSE, SJBIT

Pag e 7 1

UNIX and Shell Programming

10CS44

tail +11 emp.lst


Will display 11th line onwards
Different options for tail are:

Monitoring the file growth (-f)


Extracting bytes rather than lines (-c)

Use tail f when we are running a program that continuously writes to a file, and we want to see
how the file is growing. We have to terminate this command with the interrupt key.
cut slitting a file vertically
It is used for slitting the file vertically. head -n 5 emp.lst | tee shortlist will select the first five
lines of emp.lst and saves it to shortlist. We can cut by using -c option with a list of column
numbers, delimited by a comma (cutting columns).
cut -c 6-22,24-32 shortlist
cut -c -3,6-22,28-34,55- shortlist
The expression 55- indicates column number 55 to end of line. Similarly, -3 is the same as 1-3.
Most files dont contain fixed length lines, so we have to cut fields rather than columns (cutting
fields).
-d for the field delimiter
-f for the field list
cut -d \ | -f 2,3 shortlist | tee cutlist1
will display the second and third columns of shortlist and saves the output in cutlist1.
here | is escaped to prevent it as pipeline character

To print the remaining fields, we have


cut d \ | -f 1,4- shortlist > cutlist2

paste pasting files


When we cut with cut, it can be pasted back with the paste command, vertically rather than
horizontally. We can view two files side by side by pasting them. In the previous topic, cut was
used to create the two files cutlist1 and cutlist2 containing two cut-out portions of the same file.
paste cutlist1 cutlist2
We can specify one or more delimiters with -d
paste -d | cutlist1 cutlist2

Dept. of CSE, SJBIT

Pag e 7 2

UNIX and Shell Programming

10CS44

Where each field will be separated by the delimiter |. Even though paste uses at least two files for
concatenating lines, the data for one file can be supplied through the standard input.
Joining lines (-s)
Let us consider that the file address book contains the details of three persons
cat addressbook
paste -s addressbook -to print in one single line
paste -s -d | | \n addressbook -are used in a circular manner

sort : ordering a file


Sorting is the ordering of data in ascending or descending sequence. The sort command orders a
file and by default, the entire line is sorted
sort shortlist
This default sorting sequence can be altered by using certain options. We can also sort one or
more keys (fileds) or use a different ordering rule.

sort options
The important sort options are:
-tchar

uses delimiter char to identify fields

-k n

sorts on nth field

-k m,n

starts sort on mth field and ends sort on nth field

-k m.n

starts sort on nth column of mth field

-u

removes repeated lines

-n

sorts numerically

-r

reverses sort order

-f

folds lowercase to equivalent uppercase

-m list

merges sorted files in list

-c

checks if file is sorted

-o flname

places output in file flname

sort t| k 2 shortlist

Dept. of CSE, SJBIT

Pag e 7 3

UNIX and Shell Programming

10CS44

sorts the second field (name)


sort t| r k 2 shortlist

or

sort t| k 2r shortlist
sort order can be revered with this r option.
sort t| k 3,3 k 2,2 shortlist
sorting on secondary key is also possible as shown above.
sort t| k 5.7,5.8 shortlist
we can also specify a character position with in a field to be the beginning of sort as
shown above (sorting on columns).
sort n numfile
when sort acts on numericals, strange things can happen. When we sort a file containing
only numbers, we get a curious result. This can be overridden by n (numeric) option.
cut d | f3 emp.lst | sort u | tee desigx.lst
Removing repeated lines can be possible using u option as shown above. If we cut out
the designation filed from emp.lst, we can pipe it to sort to find out the unique designations that
occur in the file.
Other sort options are:
sort o sortedlist k 3 shortlist
sort o shortlist shortlist
sort c shortlist
sort t | c k 2 shortlist
sort m foo1 foo2 foo3

uniq command locate repeated and nonrepeated lines


When we concatenate or merge files, we will face the problem of duplicate entries
creeping in. we saw how sort removes them with the u option. UNIX offers a special tool to
handle these lines the uniq command. Consider a sorted dept.lst that includes repeated lines:
cat dept.lst
displays all lines with duplicates. Where as,
uniq dept.lst

Dept. of CSE, SJBIT

Pag e 7 4

UNIX and Shell Programming

10CS44

simply fetches one copy of each line and writes it to the standard output. Since uniq requires a
sorted file as input, the general procedure is to sort a file and pipe its output to uniq. The
following pipeline also produces the same output, except that the output is saved in a file:
sort dept.lst | uniq uniqlist
Different uniq options are :
Selecting the nonrepeated lines (-u)
cut d | f3 emp.lst | sort | uniq u
Selecting the duplicate lines (-d)
cut d | f3 emp.lst | sort | uniq d
Counting frequency of occurrence (-c)
cut d | f3 emp.lst | sort | uniq c

tr command translating characters


The tr filter manipulates the individual characters in a line. It translates characters using
one or two compact expressions.
tr options expn1 expn2 standard input
It takes input only from standard input, it doesnt take a filename as argument. By default, it
translates each character in expression1 to its mapped counterpart in expression2. The first
character in the first expression is replaced with the first character in the second expression, and
similarly for the other characters.
tr |/ ~- < emp.lst | head n 3
exp1=|/ ; exp2=~-
tr $exp1 $exp2 < emp.lst
Changing case of text is possible from lower to upper for first three lines of the file.
head n 3 emp.lst | tr [a-z] [A-Z]
Different tr options are:
Deleting charecters (-d)
tr d |/ < emp.lst | head n 3
Compressing multiple consecutive charecters (-s)
tr s < emp.lst | head n 3

Dept. of CSE, SJBIT

Pag e 7 5

UNIX and Shell Programming

10CS44

Complementing values of expression (-c)


tr cd |/ < emp.lst
Using ASCII octal values and escape sequences
tr | \012 < emp.lst | head n 6

Dept. of CSE, SJBIT

Pag e 7 6

UNIX and Shell Programming

10CS44

UNIT 5
5.1. Filters Using Regular Expression
grep and sed
We often need to search a file for a pattern, either to see the lines containing (or not
containing) it or to have it replaced with something else. This chapter discusses two important
filters that are specially suited for these tasks grep and sed. grep takes care of all search
requirements we may have. sed goes further and can even manipulate the individual characters in
a line. In fact sed can de several things, some of then quite well.
grep searching for a pattern
It scans the file / input for a pattern and displays lines containing the pattern, the line
numbers or filenames where the pattern occurs. Its a command from a special family in UNIX
for handling search requirements.
grep options pattern filename(s)
grep sales emp.lst
will display lines containing sales from the file emp.lst. Patterns with and without quotes is
possible. Its generally safe to quote the pattern. Quote is mandatory when pattern involves more
than one word. It returns the prompt in case the pattern cant be located.
grep president emp.lst
When grep is used with multiple filenames, it displays the filenames along with the output.
grep director emp1.lst emp2.lst
Where it shows filename followed by the contents

grep options
grep is one of the most important UNIX commands, and we must know the options that
POSIX requires grep to support. Linux supports all of these options.
-i

ignores case for matching

-v

doesnt display lines matching expression

-n

displays line numbers along with lines

-c

displays count of number of occurrences

-l

displays list of filenames only

-e exp

specifies expression with this option

Dept. of CSE, SJBIT

Pag e 7 7

UNIX and Shell Programming


-x

matches pattern with entire line

-f file

takes pattrens from file, one per line

-E

treats pattren as an extended RE

-F

matches multiple fixed strings

10CS44

grep -i agarwal emp.lst


grep -v director emp.lst > otherlist
wc -l otherlist will display 11 otherlist
grep n marketing emp.lst
grep c director emp.lst
grep c director emp*.lst
will print filenames prefixed to the line count
grep l manager *.lst
will display filenames only
grep e Agarwal e aggarwal e agrawal emp.lst
will print matching multiple patterns
grep f pattern.lst emp.lst
all the above three patterns are stored in a separate file pattern.lst

Basic Regular Expressions (BRE) An Introduction


It is tedious to specify each pattern separately with the -e option. grep uses an expression
of a different type to match a group of similar patterns. If an expression uses meta characters, it is
termed a regular expression. Some of the characters used by regular expression are also
meaningful to the shell.

BRE character subset


The basic regular expression character subset uses an elaborate meta character set,
overshadowing the shells wild-cards, and can perform amazing matches.
*

Zero or more occurrences

g*

nothing or g, gg, ggg, etc.

A single character

Dept. of CSE, SJBIT

Pag e 7 8

UNIX and Shell Programming

10CS44

.*

nothing or any number of characters

[pqr]

a single character p, q or r

[c1-c2]

a single character within the ASCII range represented by c1 and c2

The character class


grep supports basic regular expressions (BRE) by default and extended regular
expressions (ERE) with the E option. A regular expression allows a group of characters enclosed
within a pair of [ ], in which the match is performed for a single character in the group.
grep [aA]g[ar][ar]wal emp.lst
A single pattern has matched two similar strings. The pattern [a-zA-Z0-9] matches a single
alphanumeric character. When we use range, make sure that the character on the left of the
hyphen has a lower ASCII value than the one on the right. Negating a class (^) (caret) can be
used to negate the character class. When the character class begins with this character, all
characters other than the ones grouped in the class are matched.

The *
The asterisk refers to the immediately preceding character. * indicates zero or more occurrences
of the previous character.
g* nothing or g, gg, ggg, etc.
grep [aA]gg*[ar][ar]wal emp.lst
Notice that we dont require to use e option three times to get the same output!!!!!

The dot
A dot matches a single character. The shell uses ? Character to indicate that.
.*

signifies any number of characters or none

grep j.*saxena emp.lst

Specifying Pattern Locations (^ and $)


Most of the regular expression characters are used for matching patterns, but there are
two that can match a pattern at the beginning or end of a line. Anchoring a pattern is often
necessary when it can occur in more than one place in a line, and we are interested in its
occurance only at a particular location.
^

for matching at the beginning of a line

for matching at the end of a line

Dept. of CSE, SJBIT

Pag e 7 9

UNIX and Shell Programming

10CS44

grep ^2 emp.lst
Selects lines where emp_id starting with 2
grep 7$ emp.lst
Selects lines where emp_salary ranges between 7000 to 7999
grep ^[^2] emp.lst
Selects lines where emp_id doesnt start with 2

When meta characters lose their meaning


It is possible that some of these special characters actually exist as part of the text.
Sometimes, we need to escape these characters. For example, when looking for a pattern g*, we
have to use \
To look for [, we use \[
To look for .*, we use \.\*

Extended Regular Expression (ERE) and grep


If current version of grep doesnt support ERE, then use egrep but without the E option.
-E option treats pattern as an ERE.
+

matches one or more occurrences of the previous character

Matches zero or one occurrence of the previous character

b+ matches b, bb, bbb, etc.


b? matches either a single instance of b or nothing
These characters restrict the scope of match as compared to the *
grep E [aA]gg?arwal emp.lst
# ?include +<stdio.h>
The ERE set
ch+

matches one or more occurrences of character ch

ch?

Matches zero or one occurrence of character ch

exp1|exp2

matches exp1 or exp2

(x1|x2)x3

matches x1x3 or x2x3

Dept. of CSE, SJBIT

Pag e 8 0

UNIX and Shell Programming

10CS44

Matching multiple patterns (|, ( and ))


grep E sengupta|dasgupta emp.lst
We can locate both without using e option twice, or
grep E (sen|das)gupta emp.lst

sed The Stream Editor


sed is a multipurpose tool which combines the work of several filters. sed uses
instructions to act on text. An instruction combines an address for selecting lines, with an action
to be taken on them.
sed options address action file(s)
sed supports only the BRE set. Address specifies either one line number to select a single line or a
set of two lines, to select a group of contiguous lines. action specifies print, insert, delete,
substitute the text.
sed processes several instructions in a sequential manner. Each instruction operates on
the output of the previous instruction. In this context, two options are relevant, and probably they
are the only ones we will use with sed the e option that lets us use multiple instructions, and
the f option to take instructions from a file. Both options are used by grep in identical manner.

Line Addressing
sed 3q emp.lst
Just similar to head n 3 emp.lst. Selects first three lines and quits
sed n 1,2p emp.lst
p prints selected lines as well as all lines. To suppress this behavior, we use n whenever we use
p command
sed n $p emp.lst
Selects last line of the file
sed n 9,11p emp.lst
Selecting lines from anywhere of the file, between lines from 9 to 11
sed n 1,2p
7,9p
$p emp.lst

Dept. of CSE, SJBIT

Pag e 8 1

UNIX and Shell Programming

10CS44

Selecting multiple groups of lines


sed n 3,$!p emp.lst
Negating the action, just same as 1,2p

Using Multiple Instructions (-e and f)


There is adequate scope of using the e and f options whenever sed is used with
multiple instructions.
sed n e 1,2p e 7,9p e $p emp.lst
Let us consider,
cat instr.fil
1,2p
7,9p
$p
-f option to direct the sed to take its instructions from the file
sed n f instr.fil emp.lst
We can combine and use e and f options as many times as we want
sed n f instr.fil1 f instr.fil2 emp.lst
sed n e /saxena/p f instr.fil1 f instr.fil2 emp.lst

Context Addressing
We can specify one or more patterns to locate lines
sed n /director/p emp.lst
We can also specify a comma-separated pair of context addresses to select a group of lines.
sed n /dasgupta/,/saxena/p emp.lst
Line and context addresses can also be mixed
sed n 1,/dasgupta/p emp.lst

Using regular expressions


Context addresses also uses regular expressions.

Dept. of CSE, SJBIT

Pag e 8 2

UNIX and Shell Programming

10CS44

Sed n /[aA]gg*[ar][ar]wal/p emp.lst


Selects all agarwals.
Sed n /sa[kx]s*ena/p
/gupta/p emp.lst
Selects saxenas and gupta.
We can also use ^ and $, as part of the regular expression syntax.
sed n /50..$/p emp.lst
Selects all people born in the year 1950.

Writing Selected Lines to a File (w)


We can use w command to write the selected lines to a separate file.
sed n /director/w dlist emp.lst
Saves the lines of directors in dlist file
sed n /director/w dlist
/manager/w mlist
/executive/w elist emp.lst
Splits the file among three files
sed n 1,500w foo1
501,$w foo2 foo.main
Line addressing also is possible. Saves first 500 lines in foo1 and the rest in foo2

Text Editing
text.

sed supports inserting (i), appending (a), changing (c) and deleting (d) commands for the
$ sed 1i\
> #include <stdio.h>\
> #include <unistd.h>
> foo.c > $$

Dept. of CSE, SJBIT

Pag e 8 3

UNIX and Shell Programming

10CS44

Will add two include lines in the beginning of foo.c file. Sed identifies the line without the \ as
the last line of input. Redirected to $$ temporary file. This technique has to be followed when
using the a and c commands also. To insert a blank line after each line of the file is printed
(double spacing text), we have,
sed a\
emp.lst

Deleting lines (d)


sed /director/d emp.lst > olist

or

sed n /director/!p emp.lst > olist


Selects all lines except those containing director, and saves them in olist
Note that n option not to be used with d

Substitution (s)
Substitution is the most important feature of sed, and this is one job that sed does
exceedingly well.
[address]s/expression1/expression2/flags
Just similar to the syntax of substitution in vi editor, we use it in sed also.
sed s/|/:/ emp.lst | head n 2
2233:a.k.shukla |gm |sales |12/12/52|6000
9876:jai sharma |director|production|12/03/50|7000
Only the first instance of | in a line has been replaced. We need to use the g (global) flag
to replace all the pipes.
sed s/|/:/g emp.lst | head n 2
We can limit the vertical boundaries too by specifying an address (for first three lines only).
sed 1,3s/|/:/g emp.lst
Replace the word director with member in the first five lines of emp.lst
sed 1,5s/director/member/ emp.lst
sed also uses regular expressions for patterns to be substituted. To replace all occurrence of
agarwal, aggarwal and agrawal with simply Agarwal, we have,
sed s/[Aa]gg*[ar][ar]wal/Agarwal/g emp.lst

Dept. of CSE, SJBIT

Pag e 8 4

UNIX and Shell Programming

10CS44

We can also use ^ and $ with the same meaning. To add 2 prefix to all emp-ids,
sed s/^/2/ emp.lst | head n 1
22233 | a.k.shukla | gm | sales | 12/12/52 | 6000
To add .00 suffix to all salary,
sed s/$/.00/ emp.lst | head n 1
2233 | a.k.shukla | gm | sales | 12/12/52 | 6000.00
Performing multiple substitutions
sed s/<I>/<EM>/g
s/<B>/<STRONG>/g
s/<U>/<EM>/g form.html
An instruction processes the output of the previous instruction, as sed is a stream editor and
works on data stream
sed s/<I>/<EM>/g
s/<EM>/<STRONG>/g form.html
When a g is used at the end of a substitution instruction, the change is performed globally along
the line. Without it, only the left most occurrence is replaced. When there are a group of
instructions to execute, you should place these instructions in a file instead and use sed with the
f option.
Compressing multiple spaces
sed s/*|/|/g emp.lst | tee empn.lst | head n 3
2233|a.k.shukla|g.m|sales|12/12/52|6000
9876|jai sharma|director|production|12/03/50|7000
5678|sumit chakrobarty|dgm|mrking|19/04/43|6000
The remembered patterns
Consider the below three lines which does the same job
sed s/director/member/ emp.lst
sed /director/s//member/ emp.lst
sed /director/s/director/member/ emp.lst

Dept. of CSE, SJBIT

Pag e 8 5

UNIX and Shell Programming

10CS44

The // representing an empty regular expression is interpreted to mean that the search and
substituted patterns are the same
sed s/|//g emp.lst

removes every | from file

Basic Regular Expressions (BRE) Revisited


Three more additional types of expressions are:
The repeated patterns - &
The interval regular expression (IRE) { }
The tagged regular expression (TRE) ( )

The repeated patterns - &


To make the entire source pattern appear at the destination also
sed s/director/executive director/ emp.lst
sed s/director/executive &/ emp.lst
sed /director/s//executive &/ emp.lst
Replaces director with executive director where & is a repeated pattern

The interval RE - { }
sed and grep uses IRE that uses an integer to specify the number of characters preceding a
pattern. The IRE uses an escaped pair of curly braces and takes three forms:
ch\{m\} the ch can occur m times
ch\{m,n\} ch can occur between m and n times
ch\{m,\} ch can occur at least m times
The value of m and n can't exceed 255. Let teledir.txt maintains landline and mobile phone
numbers. To select only mobile numbers, use IRE to indicate that a numerical can occur 10 times.
grep [0-9]\{10\} teledir.txt
Line length between 101 and 150
grep ^.\{101,150\}$ foo
Line length at least 101
sed n /.{101,\}/p foo

Dept. of CSE, SJBIT

Pag e 8 6

UNIX and Shell Programming

10CS44

The Tagged Regular Expression (TRE)


You have to identify the segments of a line that you wish to extract and enclose each segment
with a matched pair of escaped parenthesis. If we need to extract a number, \([0-9]*\). If we need
to extract non alphabetic characters,
\([^a-zA-Z]*\)
Every grouped pattern automatically acquires the numeric label n, where n signifies the nth group
from the left.
sed s/ \ (a-z]*\) *\ ([a-z]*\) / \2, \1/ teledir.txt
To get surname first followed by a , and then the name and rest of the line. sed does not use
compulsorily a / to delimit patterns for substitution. We can use only any character provided it
doesnt occur in the entire command line. Choosing a different delimiter has allowed us to get
away without escaping the / which actually occurs in the pattern.

Dept. of CSE, SJBIT

Pag e 8 7

UNIX and Shell Programming

10CS44

UNIT 6
6.1. Essential Shell Programming
Definition:
Shell is an agency that sits between the user and the UNIX system.
Description:
Shell is the one which understands all user directives and carries them out. It processes the
commands issued by the user. The content is based on a type of shell called Bourne shell.

Shell Scripts
When groups of command have to be executed regularly, they should be stored in a file, and the
file itself executed as a shell script or a shell program by the user. A shell program runs in
interpretive mode. It is not complied with a separate executable file as with a C program but each
statement is loaded into memory when it is to be executed. Hence shell scripts run slower than the
programs written in high-level language. .sh is used as an extension for shell scripts. However the
use of extension is not mandatory.
Shell scripts are executed in a separate child shell process which may or may not be same as the
login shell.
Example: script.sh
#! /bin/sh
# script.sh: Sample Shell Script
echo Welcome to Shell Programming
echo Todays date : `date`
echo This months calendar:
cal `date +%m 20%y`

#This months calendar.

echo My Shell :$ SHELL


The # character indicates the comments in the shell script and all the characters that follow the #
symbol are ignored by the shell. However, this does not apply to the first line which beings with
#. This because, it is an interpreter line which always begins with #! followed by the pathname of
the shell to be used for running the script. In the above example the first line indicates that we are
using a Bourne Shell.
To run the script we need to first make it executable. This is achieved by using the chmod
command as shown below:

Dept. of CSE, SJBIT

Pag e 8 8

UNIX and Shell Programming

10CS44

$ chmod +x script.sh
Then invoke the script name as:
$ script.sh
Once this is done, we can see the following output :
Welcome to Shell Programming
Todays date: Mon Oct 8 08:02:45 IST 2007
This months calendar:
October 2007
Su

Mo

Tu

We

Th

Fr

Sa

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

My Shell: /bin/Sh
As stated above the child shell reads and executes each statement in interpretive mode. We can
also explicitly spawn a child of your choice with the script name as argument:
sh script.sh
Note: Here the script neither requires a executable permission nor an interpreter line.

Read: Making scripts interactive


The read statement is the shells internal tool for making scripts interactive (i.e. taking
input from the user). It is used with one or more variables. Inputs supplied with the
standard input are read into these variables. For instance, the use of statement like
r ea d n a m e
causes the script to pause at that point to take input from the keyboard. Whatever is
entered by you will be stored in the variable name.
Dept. of CSE, SJBIT

Pag e 8 9

UNIX and Shell Programming

10CS44

Example: A shell script that uses read to take a search string and filename from the
terminal.
#! /bin/sh
# emp1.sh: Interactive version, uses read to accept two inputs
#
echo Enter the pattern to be searched: \c

# No newline

read pname
echo Enter the file to be used: \c

# use echo e in bash

read fname
echo Searching for pattern $pname from the file $fname
grep $pname $fname
echo Selected records shown above
Running of the above script by specifying the inputs when the script pauses twice:
$ emp1.sh
Enter the pattern to be searched : director
Enter the file to be used: emp.lst
Searching for pattern director from the file emp.lst
9876

Jai Sharma

Director

Productions

2356

Rohit

Director

Sales

Selected records shown above

Using Command Line Arguments


Shell scripts also accept arguments from the command line. Therefore e they can be run
non interactively and be used with redirection and pipelines. The arguments are assigned
to special shell variables. Represented by $1, $2, etc; similar to C command arguments
argv[0], argv[1], etc. The following table lists the different shell parameters.
Shell parameter

Dept. of CSE, SJBIT

Significance

Pag e 9 0

UNIX and Shell Programming

10CS44

$1, $2

Positional parameters representing command line arguments

$#

No. of arguments specified in command line

$0

Name of the executed command

$*

Complete set of positional parameters as a single string

$ @

Each quoted string treated as separate argument

$?

Exit status of last command

$$

Pid of the current shell

$!

PID of the last background job.

Table: shell parameters


exit and Exit Status of Command
To terminate a program exit is used. Nonzero value indicates an error condition.
Example 1:
$ cat foo
C a t : c a n t o p e n fo o
Returns nonzero exit status. The shell variable $? Stores this status.
Example 2:
grep director emp.lst > /dev/null:echo $?
0
Exit status is used to devCSE program logic that braches into different paths depending
on
success or failure of a command
The logical Operators && and ||
The shell provides two operators that aloe conditional execution, the && and ||.
Usage: cmd1 && cmd2
cmd1 || cmd2

Dept. of CSE, SJBIT

Pag e 9 1

UNIX and Shell Programming

10CS44

&& delimits two commands. cmd 2 executed only when cmd1 succeeds.
Example1:
$ grep director emp.lst && echo Pattern found
Output:
9876

Jai Sharma

Director

Productions

2356

Rohit

Director

Sales

Pattern found
Example 2:
$ grep clerk emp.lst || echo Pattern not found
Output:
Pattern not found
Example 3:
grep $1 $2 || exit 2
echo Pattern Found Job Over

The if Conditional
The if statement makes two way decisions based on the result of a condition. The following forms
of if are available in the shell:
Form 1

Form 2

if command is successful

if command is successful

then

then

execute commands
fi

Form 3

if command is successful
then

execute commands

execute commands
elif command is successful

el s e
execute commands

then...

fi

else...
fi

Dept. of CSE, SJBIT

Pag e 9 2

UNIX and Shell Programming

10CS44

If the command succeeds, the statements within if are executed or else statements in else block
are executed (if else present).
Example:
#! /bin/sh
if grep ^$1 /etc/passwd 2>/dev/null
then
echo Pattern Found
else
echo Pattern Not Found
fi
Output1:
$ emp3.sh ftp
ftp: *.325:15:FTP User:/Users1/home/ftp:/bin/true
Pattern Found
Output2:
$ emp3.sh mail
Pattern Not Found

While: Looping
To carry out a set of instruction repeatedly shell offers three features namely while, until and for.
Syntax:
while condition is true
do
Commands
done
The commands enclosed by do and done are executed repeatedly as long as condition is true.
Example:

Dept. of CSE, SJBIT

Pag e 9 3

UNIX and Shell Programming

10CS44

#! /bin/usr
ans=y
while [$ans=y]
do
echo Enter the code and description : \c > /dev/tty
read code description
echo $code $description >>newlist
echo Enter any more [Y/N]
r e a d a ny
case $any in
Y* | y* ) answer =y;;
N* | n*) answer = n;;
*) answer=y;;
esac
done
Input:
Enter the code and description : 03 analgestics
Enter any more [Y/N] :y
Enter the code and description : 04 antibiotics
Enter any more [Y/N] : [Enter]
Enter the code and description : 05 OTC drugs
Enter any more [Y/N] : n
Output:
$ cat newlist
03 | analgestics

Dept. of CSE, SJBIT

Pag e 9 4

UNIX and Shell Programming

10CS44

04 | antibiotics
05 | OTC drugs

Using test and [ ] to Evaluate Expressions


Test statement is used to handle the true or false value returned by expressions, and it is not
possible with if statement. Test uses certain operators to evaluate the condition on its right and
returns either a true or false exit status, which is then used by if for making decisions. Test works
in three ways:

Compare two numbers


Compares two strings or a single one for a null value
Checks files attributes

Test doesnt display any output but simply returns a value that sets the parameters $?
Numeric Comparison
Operator

Meaning

-eq

Equal to

-ne

Not equal to

-gt

Greater than

-ge

Greater than or equal to

-lt

Less than

-le

Less than or equal


Table: Operators

Operators always begin with a (Hyphen) followed by a two word character word and enclosed
on either side by whitespace.
Numeric comparison in the shell is confined to integer values only, decimal values are simply
truncated.
Ex:
$x=5;y=7;z=7.2
1. $test $x eq $y; echo $?
1
2. $test $x lt $y; echo $?
0

Dept. of CSE, SJBIT

Not equal
True

Pag e 9 5

UNIX and Shell Programming

10CS44

3. $test $z gt $y; echo $?


1
2
4. $test $z eq $y ; echo $y
0
1

7.2 is not greater than 7

7.2 is equal to 7

Example 3 and 4 shows that test uses only integer comparison.


The script emp.sh uses test in an if-elif-else-fi construct (Form 3) to evaluate the shell parameter
$#
#!/bin/sh
#emp.sh: using test, $0 and $# in an if-elif-else-fi construct
#
If test $# -eq 0; then
Echo Usage : $0 pattern file > /dev/tty
Elfi test $# -eq 2 ;then
Grep $1 $2 || echo $1 not found in $2>/dev/tty
Else
echo You didnt enter two arguments >/dev/tty
fi
It displays the usage when no arguments are input, runs grep if two arguments are entered and
displays an error message otherwCSE.
Run the script four times and redirect the output every time
$emp31.sh>foo
Usage : emp.sh pattern file
$emp31.sh ftp>foo
You didnt enter two arguments
$emp31.sh henry /etc/passwd>foo
Henry not found in /etc/passwd

Dept. of CSE, SJBIT

Pag e 9 6

UNIX and Shell Programming

10CS44

$emp31.sh ftp /etc/passwd>foo


ftp:*:325:15:FTP User:/user1/home/ftp:/bin/true

Shorthand for test


[ and ] can be used instead of test. The following two forms are equivalent
Test $x eq $y
and
[ $x eq $y ]

String Comparison
Test command is also used for testing strings. Test can be used to compare strings with the
following set of comparison operators as listed below.
Test

True if

s1=s2

String s1=s2

s1!=s2

String s1 is not equal to s2

-n stg

String stg is not a null string

-z stg

String stg is a null string

st g

String stg is assigned and not null

s1= =s2

String s1=s2

Table: String test used by test


Example:
#!/bin/sh
#emp1.sh checks user input for null values finally turns emp.sh developed previously
#
if [ $# -eq 0 ] ; then
echo Enter the string to be searched :\c
read pname
if [ -z $pname ] ; then
echo You have not entered th e string; exit 1
fi

Dept. of CSE, SJBIT

Pag e 9 7

UNIX and Shell Programming

10CS44

echo Enter the filename to be used :\c


read flname
if [ ! n $flname ] ; then
echo You have not entered the flname ; exit 2
fi
emp.sh $pname $flname
el s e
emp.sh $*
fi
Output1:
$emp1.sh
Enter the string to be searched :[Enter]
You have not entered the string

Output2:
$emp1.sh
Enter the string to be searched :root
Enter the filename to be searched :/etc/passwd
Root:x:0:1:Super-user:/:/usr/bin/bash
When we run the script with arguments emp1.sh bypasses all the above activities and calls
emp.sh to perform all validation checks
$emp1.sh jai
You didnt enter two arguments
$emp1.sh jai emp,lst
9878|jai sharma|director|sales|12/03/56|70000
$emp1.sh jai sharma emp.lst
You didnt enter two arguments

Dept. of CSE, SJBIT

Pag e 9 8

UNIX and Shell Programming

10CS44

Because $* treats jai and sharma are separate arguments. And $# makes a wrong argument count.
Solution is replace $* with $@ (with quote and then run the script.

File Tests
Test can be used to test various file attributes like its type (file, directory or symbolic links) or its
permission (read, write. Execute, SUID, etc).
Example:
$ ls l emp.lst
-rw-rw-rw-

1 kumar group 870 jun 8 15:52 emp.lst

$ [-f emp.lst] ; echo $?

Ordinary file

0
$ [-x emp.lst] ; echo $?

Not an executable.

1
$ [! -w emp.lst] || echo False that file not writeable
False that file is not writable.
Example: filetest.sh
#! /bin/usr
#
if [! e $1] : then
Echo File doesnot exist
elif [! r S1]; then
Echo File not readable
elif[! w $1]; then
Echo File not writable
el s e
Echo File is both readable and writable\
fi

Dept. of CSE, SJBIT

Pag e 9 9

UNIX and Shell Programming

10CS44

Output:
$ filetest.sh emp3.lst
File does not exist
$ filetest.sh emp.lst
File is both readable and writable
The following table depicts file-related Tests with test:
Test

True if

-f file

File exists and is a regular file

-r file

File exists and readable

-w file

File exists and is writable

-x file

File exists and is executable

-d file

File exists and is a directory

-s file

File exists and has a size greater than zero

-e file

File exists (Korn & Bash Only)

-u file

File exists and has SUID bit set

-k file

File exists and has sticky bit set

-L file

File exists and is a symbolic link (Korn & Bash Only)

f1 nt f2

File f1 is newer than f2 (Korn & Bash Only)

f1 ot f2

File f1 is older than f2 (Korn & Bash Only)

f1 ef f2

File f1 is linked to f2 (Korn & Bash Only)


Table: file-related Tests with test

Dept. of CSE, SJBIT

Page 100

UNIX and Shell Programming

10CS44

The case Conditional


The case statement is the second conditional offered by the shell. It doesnt have a
parallel either in C (Switch is similar) or perl. The statement matches an expression for
more than one alternative, and uses a compact construct to permit multiway branching.
case also handles string tests, but in a more efficient manner than if.
Sy n t ax :
case expression in
Pa t t e rn 1 ) c o m m a n d s 1 ; ;
Pa t t e rn 2 ) c o m m a n d s 2 ; ;
Pa t t e rn 3 ) c o m m a n d s 3 ; ;

Esac
Case first matches expression with pattern1. if the match succeeds, then it executes
commands1, which may be one or more commands. If the match fails, then pattern2 is
matched and so forth. Each command list is terminated with a pair of semicolon and the
entire construct is closed with esac (reverse of case).
Example:
#! /bin/sh
#
ech o
Menu\n
1. List of files\n2. Processes of user\n3. Todays Date
4. Users of system\n5.Quit\nEnter your option: \c
read ch o i ce
case $choice in
1) ls l;;
2) ps f ;;
3) date ;;
4) who ;;
5) exit ;;
*) echo Invalid option
esac
Output
$ m en u . s h
Menu
1. List of files
2. Processes of user
Dept. of CSE, SJBIT

Page 101

UNIX and Shell Programming

10CS44

3. Todays Date
4. Users of system
5. Quit
Enter your option: 3
Mon Oct 8 08:02:45 IST 2007
Note:

case can not handle relational and file test, but it matches strings with compact code. It is
very effective when the string is fetched by command substitution.

case can also handle numbers but treats them as strings.

Matching Multiple Patterns:


case can also specify the same action for more than one pattern . For instance to test a user
response for both y and Y (or n and N).
Example:
Echo Do you wish to continue? [y/n]: \c
Read ans
Case $ans in
Y | y );;
N | n) exit ;;
es ac

Wild-Cards: case uses them:


case has a superb string matching feature that uses wild-cards. It uses the filename
matching metacharacters *, ? and character class (to match only strings and not files in
the current directory).
Example:
Case $ans in
[Yy] [eE]* );;

Matches YES, yes, Yes, yEs, etc

[Nn] [oO]) exit ;;

Matches no, NO, No, nO

*) echo Invalid Response


esac

Dept. of CSE, SJBIT

Page 102

UNIX and Shell Programming

10CS44

expr: Computation and String Handling


The Broune shell uses expr command to perform computations. This command combines
the following two functions:
Performs arithmetic operations on integers
Manipulates strings
Computation:
expr can perform the four basic arithmetic operations (+, -, *, /), as well as modulus (%)
functions.
Examples:
$ x=3 y=5
$ expr 3+5
8
$ expr $x-$y
-2
$ expr 3 \* 5
15

Note:\ is used to prevent the shell from interpreting * as metacharacter

$ expr $y/$x
1
$ expr 13%5
3
expr is also used with command substitution to assign a variable.
Example1:
$ x=6 y=2 : z=`expr $x+$y`
$ ech o $ z
8
Example2:
$ x=5
$ x=`expr $x+1`
$ echo $x
6

Dept. of CSE, SJBIT

Page 103

UNIX and Shell Programming

10CS44

String Handling:
expr is also used to handle strings. For manipulating strings, expr uses two expressions
separated by a colon (:). The string to be worked upon is closed on the left of the colon
and a regular expression is placed on its right. Depending on the composition of the
expression expr can perform the following three functions:
1. Determine the length of the string.
2. Extract the substring.
3. Locate the position of a character in a string.
1. Length of the string:
The regular expression .* is used to print the number of characters
matching the pattern .
Example1:
$ expr abcdefg : .*
7
Example2:
while echo Enter your name: \c ;do
read n am e
if [`expe $name :.*` -gt 20] ; then
echo Name is very long
else
break
fi
done
2. Extracting a substring:
expr can extract a string enclosed by the escape characters \ (and \).
Example:
$ st=2007
$ expr $st :..\(..\)
07

Extracts last two characters.

3. Locating position of a character:


expr can return the location of the first occurrence of a character inside a string.

Dept. of CSE, SJBIT

Page 104

UNIX and Shell Programming

10CS44

Example:
$ stg = abcdefgh ; expr $stg : [^d]*d
4
Extracts the position of character d
$0: Calling a Script by Different Names
There are a number of UNIX commands that can be used to call a file by different names
and doing different things depending on the name by which it is called. $0 can also be to
call a script by different names.
Example:
#! /bin/sh
#
lastfile=`ls t *.c |head -1`
co m m an d = $ 0
exe=`expr $lastfile: \(.*\).c`
cas e $ co m m an d i n
*runc) $exe ;;
*vic) vi $lastfile;;
*comc) cc o $exe $lastfile &&
Echo $lastfile compiled successfully;;
esac
After this create the following three links:
ln comc.sh comc
ln comc.sh runc
ln comc.sh vic
Output:
$ co m c
hello.c compiled successfully.
While: Looping
To carry out a set of instruction repeatedly shell offers three features namely while, until and for.
Synatx:
while condition is true
do
Commands
done

Dept. of CSE, SJBIT

Page 105

UNIX and Shell Programming

10CS44

The commands enclosed by do and done are executed repadetedly as long as condition is true.
Example:
#! /bin/usr
ans=y
while [$ans=y]
do
echo Enter the code and description : \c > /dev/tty
read code description
echo $code $description >>newlist
echo Enter any more [Y/N]
r e a d a ny
case $any in
Y* | y* ) answer =y;;
N* | n*) answer = n;;
*) answer=y;;
esac
done
Input:
Enter the code and description : 03 analgestics
Enter any more [Y/N] :y
Enter the code and description : 04 antibiotics
Enter any more [Y/N] : [Enter]
Enter the code and description : 05 OTC drugs
Enter any more [Y/N] : n
Output:
$ cat newlist

Dept. of CSE, SJBIT

Page 106

UNIX and Shell Programming

10CS44

03 | analgestics
04 | antibiotics
05 | OTC drugs

Other Examples: An infinite/semi-infinite loop


(1 )
while true ; do
[ -r $1 ] && break
sleep $2
done

(2)
while [ ! -r $1 ] ; do
sleep $2
done

for: Looping with a List


for is also a repetitive structure.
Synatx:
for variable in list
do
Commands
done

list here comprCSEs a series of character strings. Each string is assigned to variable
specified.
Example:
for file in ch1 ch2; do
> cp $file ${file}.bak
> echo $file copied to $file.bak
done
Output:
ch1 copied to ch1.bak
ch2 copied to ch2.bak
Sources of list:

List from variables: Series of variables are evaluated by the shell before
executing the loop

Dept. of CSE, SJBIT

Page 107

UNIX and Shell Programming

10CS44

Example:
$ for var in $PATH $HOME; do echo $var ; done
Output:
/bin:/usr/bin;/home/local/bin;
/home/user1

List from command substitution: Command substitution is used for creating a


list. This is used when list is large.
Example:
$ for var in `cat clist`

List from wildcards: Here the shell interprets the wildcards as filenames.
Example:
for file in *.htm *.html ; do
sed s/strong/STRONG/g
s/img src/IMG SRC/g $file > $$
mv $$ $file
done

List from positional parameters:


Example: emp.sh
#! /bin/sh
for pattern in $@; do
grep $pattern emp.lst || echo Pattern $pattern not found
done
Output:
$emp.sh 9876 Rohit
9876

Jai Sharma

Director

Productions

2356

Rohit

Director

Sales

basename: Changing Filename Extensions


They are useful in chaining the extension of group of files. Basename extracts the base
filename from an absolute pathname.
Dept. of CSE, SJBIT

Page 108

UNIX and Shell Programming

10CS44

Example1:
$basename /home/user1/test.pl
Ouput:
test.pl
Example2:
$basename test2.doc doc
Ouput:
test2
Example3: Renaming filename extension from .txt to .doc
for file in *.txt ; do
leftname=`basename $file .txt` Stores left part of filename
m v $ fi l e $ { l e ft n a m e } . d o c
done
set and shift: Manipulating the Positional Parameters
The set statement assigns positional parameters $1, $2 and so on, to its arguments. This is used
for picking up individual fields from the output of a program.
Example 1:
$ set 9876 2345 6213
$
This assigns the value 9876 to the positional parameters $1, 2345 to $2 and 6213 to $3. It also
sets the other parameters $# and $*.
Example 2:
$ set `date`
$ echo $*
Mon Oct 8 08:02:45 IST 2007
Example 3:
$ echo The date today is $2 $3, $6

Dept. of CSE, SJBIT

Page 109

UNIX and Shell Programming

10CS44

The date today is Oct 8, 2007

Shift: Shifting Arguments Left


Shift transfers the contents of positional parameters to its immediate lower numbered one. This is
done as many times as the statement is called. When called once, $2 becomes $1, $3 becomes S2
and so on.
Example 1:
$@ and $* are interchangeable

$ echo $@
Mon Oct 8 08:02:45 IST 2007
$ echo $1 $2 $3
Mon Oct 8
$shift
$echo $1 $2 $3
Mon Oct 8 08:02:45

Shifts 2 places

$shift 2
$echo $1 $2 $3
08:02:45 IST 2007
Example 2: emp.sh
#! /bin/sh
Case $# in

0|1) echo Usage: $0 file pattern(S) ;exit ;;


*) fname=$1
shift
for pattern in $@ ; do
grep $pattern $fname || echo Pattern $pattern not found
done;;
es ac
Output:$emp.sh emp.lst

Dept. of CSE, SJBIT

Page 110

UNIX and Shell Programming

10CS44

Insufficient number of arguments


$emp.sh emp.lst Rakesh 1006 9877

9876

Jai Sharma

Director

Productions

2356

Rohit

Director

Sales

Pattern 9877 not found.

Set -- : Helps Command Substitution


Inorder for the set to interpret - and null output produced by UNIX commands the option is
used . If not used in the output is treated as an option and set will interpret it wrongly. In case of
null, all variables are displayed instead of null.
Example:
$set `ls l chp1`
Output:
-rwxr-xr-x: bad options
Example2:
$set `grep usr1 /etc/passwd`
Correction to be made to get correct output are:
$set -- `ls l chp1`
$set -- `grep usr1 /etc/passwd`

The Here Document (<<)


The shell uses the << symbol to read data from the same file containing the script. This is referred
to as a here document, signifying that the data is here rather than in aspirate file. Any command
using standard input can slo take input from a here document.
Example:
mailx kumar << MARK
Your program for printing the invoices has been executed
on `date`.Check the print queue

Dept. of CSE, SJBIT

Page 111

UNIX and Shell Programming

10CS44

The updated file is $flname


MARK
The string (MARK) is delimiter. The shell treats every line following the command and delimited
by MARK as input to the command. Kumar at the other end will see three lines of message text
with the date inserted by command. The word MARK itself doesnt show up.

Using Here Document with Interactive Programs:


A shell script can be made to work non-interactively by suppl ying inputs through here
document.
Example:
$ s e a rc h . s h < < E N D
> d i re c t o r
>emp.lst
>E N D
Output:
Enter the pattern to be searched: Enter the file to be used: Searching for director from file
emp.lst
9876

Jai Sharma

Director

Productions

2356

Rohit

Director

Sales

Selected records shown above.


The script search.sh will run non-interactively and display the lines containing director in the
file emp.lst.

trap: interrupting a Program


Normally, the shell scripts terminate whenever the interrupt key is pressed. It is not a good
programming practice because a lot of temporary files will be stored on disk. The trap statement
lets you do the things you want to do when a script receives a signal. The trap statement is
normally placed at the beginning of the shell script and uses two lists:
trap command_list signal_list
When a script is sent any of the signals in signal_list, trap executes the commands in
command_list. The signal list can contain the integer values or names (without SIG prefix) of one
or more signals the ones used with the kill command.

Dept. of CSE, SJBIT

Page 112

UNIX and Shell Programming

10CS44

Example: To remove all temporary files named after the PID number of the shell:
trap rm $$* ; echo Program Interrupted ; exit HUP INT TERM
trap is a signal handler. It first removes all files expanded from $$*, echoes a message and finally
terminates the script when signals SIGHUP (1), SIGINT (2) or SIGTERM(15) are sent to the
shell process running the script.
A script can also be made to ignore the signals by using a null command list.
Example:
trap 1 2 15
Programs
1)
#!/bin/sh
IFS=|
While echo enter dept code:\c; do
Read dcode
Set -- `grep ^$dcode<<limit
01|CSE|22
02|CSE|45
03|ECE|25
04|TCE|58
limit`
Case $# in
3) echo dept name :$2 \n emp-id:$3\n
*) echo invalid code;continue
es ac
done
Output:
$valcode.sh

Dept. of CSE, SJBIT

Page 113

UNIX and Shell Programming

10CS44

Enter dept code:88


Invalid code
Enter dept code:02
Dept name : CSE
Emp-id :45
Enter dept code:<ctrl-c>
2)
#!/bin/sh
x=1
While [$x le 10];do
echo $x
x=`expr $x+1`
done
#!/bin/sh
sum=0
for I in $@ do
echo $I
sum=`expr $sum + $I`
done
Echo sum is $sum
3)
#!/bin/sh
sum=0
for I in `cat list`; do
echo string is $I
x= `expr $I:.*`

Dept. of CSE, SJBIT

Page 114

UNIX and Shell Programming

10CS44

Echo length is $x
Done
4)
This is a non-recursive shell script that accepts any number of arguments and prints them in a
reverse order.
For example if A B C are entered then output is C B A.
#!/bin/sh
if [ $# -lt 2 ]; then
echo "please enter 2 or more arguments"
exit
fi
for x in $@
do
y=$x" "$y
done
echo "$y"
Run1:
[root@localhost shellprgms]# sh sh1a.sh 1 2 3 4 5 6 7
7654321
Run2: [root@localhost shellprgms]# sh ps1a.sh this is an argument
argument an is this
5)
The following shell script to accept 2 file names checks if the permission for these files are
identical and if they are not identical outputs each filename followed by permission.
#!/bin/sh
if [ $# -lt 2 ]
then

Dept. of CSE, SJBIT

Page 115

UNIX and Shell Programming

10CS44

echo "invalid number of arguments"


exit
fi
str1=`ls -l $1|cut -c 2-10`
str2=`ls -l $2|cut -c 2-10`
if [ "$str1" = "$str2" ]
then
echo "the file permissions are the same: $str1"
el s e
echo " Different file permissions "
echo -e "file permission for $1 is $str1\nfile permission for $2 is $str2"
fi
Run1:
[root@localhost shellprgms]# sh 2a.sh ab.c xy.c
file permission for ab.c is rw-r--r-file permission for xy.c is rwxr-xr-x
Run2:
[root@localhost shellprgms]# chmod +x ab.c
[root@localhost shellprgms]# sh 2a.sh ab.c xy.c
the file permissions are the same: rwxr-xr-x
6)This shell function that takes a valid directory name as an argument and recursively descends
all the subdirectories, finds the
maximum length of any file in that hierarchy and
writes this maximum value to the standard output.
#!/bin/sh
if [ $# -gt 2 ]
then
echo "usage sh flname dir"

Dept. of CSE, SJBIT

Page 116

UNIX and Shell Programming

10CS44

exit
fi
if [ -d $1 ]
then
ls -lR $1|grep -v ^d|cut -c 34-43,56-69|sort -n|tail -1>fn1
echo "file name is `cut -c 10- fn1`"
echo " the size is `cut -c -9 fn1`"
el s e
echo "invalid dir name"
fi
Run1:
[root@localhost shellprgms]# sh 3a.sh
file name is a.out
the size is

12172

7)This shell script that accepts valid log-in names as arguments and prints their corresponding
home directories. If no arguments are specified, print a suitable error message.
if [ $# -lt 1 ]
then
echo " Invlaid Arguments....... "
exit
fi
for x in "$@"
do
grep -w "^$x" /etc/passwd | cut -d ":" -f 1,6
done
Run1:

Dept. of CSE, SJBIT

Page 117

UNIX and Shell Programming

10CS44

[root@localhost shellprgms]# sh 4a.sh root


root:/root
Run2:
[root@localhost shellprgms]# sh 4a.sh
Invalid Arguments.......
8) This shell script finds and displays all the links of a file specified as the first argument to the
script. The second argument, which is optional, can be used to specify the directory in which the
search is to begin. If this second
argument is not present .the search is to begin in current
working directory.
#!/bin/bash
if [ $# -eq 0 ]
then
echo "Usage:sh 8a.sh[file1] [dir1(optional)]"
exit
fi
if [ -f $1 ]
then
dir="."
if [ $# -eq 2 ]
then
dir=$2
fi
inode=`ls -i $1|cut -d " " -f 2`
echo "Hard links of $1 are"
find $dir -inum $inode -print
echo "Soft links of $1 are"
find $dir -lname $1 -print
el s e

Dept. of CSE, SJBIT

Page 118

UNIX and Shell Programming

10CS44

echo "The file $1 does not exist"


fi
Run1:
[root@localhost shellprgms]$ sh 5a.sh hai.c
Hard links of hai.c are
./hai.c
Soft links of hai.c are
./hai_soft
9) This shell script displays the calendar for current month with current date replaced by * or **
depending on whether date has one digit or two digits.
#!/bin/bash
n=` date +%d`
echo " Today's date is : `date +%d%h%y` ";
cal > calfile
if [ $n -gt 9 ]
then
sed "s/$n/\**/g" calfile
el s e
sed "s/$n/\*/g" calfile
[root@localhost shellprgms]# sh 6a.sh
Today's date is : 10 May 05
May 2005
Su Mo Tu We Th Fr Sa
1 2

3 4

5 6 7

8 9

** 11 12 13 14

15 16 17 18 19 20 21
22 23 24 25 26 27 28

Dept. of CSE, SJBIT

Page 119

UNIX and Shell Programming

10CS44

29 30 31
10) This shell script implements terminal locking. Prompt the user for a password after accepting,
prompt for confirmation, if match occurs it must lock and ask for password, if it matches terminal
must be unlocked
t r a p " 1 2 3 5 20
clear
echo -e \nenter password to lock terminal:"
stty -echo
read keynew
stty echo
echo -e \nconfirm password:"
stty -echo
read keyold
stty echo
if [ $keyold = $keynew ]
then
echo "terminal locked!"
while [ 1 ]
do
echo "retype the password to unlock:"
stty -echo
read key
if [ $key = $keynew ]
then
stty echo
echo "terminal unlocked!"
stty sane

Dept. of CSE, SJBIT

Page 120

UNIX and Shell Programming

10CS44

exit
fi
echo "invalid password!"
done
el s e
echo " passwords do not match!"
fi
stty sane
Run1:

[root@localhost shellprgms]# sh 13.sh


enter password:
confirm password:
terminal locked!
retype the password to unlock:
invalid password!
retype the password to unlock:
terminal unlocked!

Dept. of CSE, SJBIT

Page 121

UNIX and Shell Programming

10CS44

UNIT 7
7.1. Awk- An Advanced Filter
Introduction
awk is a programmable, pattern-matching, and processing tool available in UNIX. It
works equally well with text and numbers. It derives its name from the first letter of the
last name of its three authors namely Alfred V. Aho, Peter J. Weinberger and Brian W.
Kernighan.
Simple awk Filtering
awk is not just a command, but a programming language too. In other words, awk utility
is a pattern scanning and processing language. It searches one or more files to see if they
contain lines that match specified patterns and then perform associated actions, such as
writing the line to the standard output or incrementing a counter each time it finds a
match.
Sy n t ax :
awk option selection_criteria {action} file(s)
Here, selection_criteria filters input and selects lines for the action component to act
upon. The selection_criteria is enclosed within single quotes and the action within the
curly braces. Both the selection_criteria and action forms an awk program.
Example: $ awk /manager/ { print } emp.lst
Output:
9876

Jai Sharma

Manager

Productions

2356

Rohit

Manager

Sales

5683

Rakesh

Manager

Marketing

In the above example, /manager/ is the selection_criteria which selects lines that are processed in
the action section i.e. {print}. Since the print statement is used without any field specifiers, it
prints the whole line.
Note: If no selection_criteria is used, then action applies to all lines of the file.
Since printing is the default action of awk, any one of the following three forms can be used:
awk /manager/ emp.lst

Dept. of CSE, SJBIT

Page 122

UNIX and Shell Programming

10CS44

awk /manager/ { print } emp.lst


$0 specifies complete line.

awk /manager/ { print $0} emp.lst

Awk uses regular expression in sed style for pattern matching.


Example: awk F | /r [ao]*/ emp.lst
Output:
2356

Rohit

Manager

Sales

5683

Rakesh

Manager

Marketing

Splitting a line into fields


Awk uses special parameter, $0, to indicate entire line. It also uses $1, $2, $3 to identif y
fields. These special parameters have to be specified in single quotes so that they will not
be interpreted by the shell.
awk uses contiguous sequence of spaces and tabs as a single delimiter.
Example: awk F | /production/ { print $2, $3, $4 } emp.lst
Output:
Jai Sharma |

Manager

Productions

Rahul

Accountant |

Productions

Rakesh

Clerk

Productions

In the above example, comma (,) is used to delimit field specifications to ensure that each field is
separated from the other by a space so that the program produces a readable output.
Note: We can also specify the number of lines we want using the built-in variable NR as
illustrated in the following example:
Example: awk F | NR==2, NR==4 { print NR, $2, $3, $4 } emp.lst
Output:

Dept. of CSE, SJBIT

Page 123

UNIX and Shell Programming

10CS44

Jai Sharma

Manager

Productions

Rahul

Accountant

Productions

Rakesh

Clerk

Productions

printf: Formatting Output


The printf statement can be used with the awk to format the output. Awk accepts most of
the formats used by the printf function of C.
Example: awk F | /[kK]u?[ar]/ { printf %3d %-20s %-12s \n, NR, $2, $3}
>emp.lst
Output:
4

R Kumar

Manager

Sunil kumaar

Accountant

Anil Kummar

Clerk

Here, the name and designation have been printed in spaces 20 and 12 characters wide
respectively.
Note: The printf requires \n to print a newline after each line.

Redirecting Standard Output:


The print and printf statements can be separately redirected with the > and | symbols. Any
command or a filename that follows these redirection symbols should be enclosed within double
quotes.
Example1: use of |
printf %3d %-20s %-12s \n, NR, $2, $3 | sort
Example 2: use of >
printf %3d %-20s %-12s \n, NR, $2, $3 > newlist

Variables and Expressions


Variables and expressions can be used with awk as used with any programming language.
Here, expression consists of strings, numbers and variables combined by operators.
Dept. of CSE, SJBIT

Page 124

UNIX and Shell Programming

10CS44

Example: (x+2)*y, x-15, x/y, etc..,


Note: awk does not have any data types and every expression is interpreted either as a
string or a number. However awk has the ability to make conversions whenever required.
A variable is an identifier that references a value. To define a variable, you only have to
name it and assign it a value. The name can only contain letters, digits, and underscores,
and may not start with a digit. Case distinctions in variable names are important: Salary
and salary are two different variables. awk allows the use of user-defined variables
without declaring them i.e. variables are deemed to be declared when they are used for
the first time itself.
Example: X= 4
X= 3
Print X
Print x
Note: 1. Variables are case sensitive.
2. If variables are not initialized by the user, then implicitly they are initialized to
zero.
Strings in awk are enclosed within double quotes and can contain any character. Awk
strings can include escape sequence, octal values and even hex values. Octal values are
preceded by \ and hex values by \x. Strings that do not consist of numbers have a numeric
value of 0.
Example 1: z = "Hello"
print z
Example 2: y = \t\t Hello \7
print y

prints Hello
prints two tabs followed by the string Hello and
sounds a beep.

String concatenation can also be performed. Awk does not provide any operator for this,
however strings can be concatenated by simply placing them side-by-side.
Example 1: z = "Hello" "World"
print z

prints Hello World

Example 2 : p = UNIX ; q= awk


print p q

prints UNIX awk

Example 3: x = UNIX
y = LINUX
print x & y

prints UNIX & LINUX

Dept. of CSE, SJBIT

Page 125

UNIX and Shell Programming

10CS44

A numeric and string value can also be concatenated.


Example : l = 8 ; m = 2 ; n = Hello
Print l m
Print l - m
Print m + n

prints 82 by converting m to string.


prints 6 by converting l as number.
prints 2 by converting n to numeric 0.

Expressions also have true and false values associated with them. A nonempty string or
any positive number has true value.
This is true if c is a nonempty string or
positive number.

Example: if(c)
The Comparison Operators

awk also provides the comparison operators like >, <, >=, <= ,==, !=, etc..,
Example 1 : $ awk F | $3 == manager || $3 == chairman {
> printf %-20s %-12s %d\n, $2, $3, $5} emp.lst
Output:
ganesh

chairman

15000

jai sharma

manager

9000

rohit

manager

8750

rakesh
manager
8500
The
for two
filed ($3). The second attempted only if (||) the first match fails.

above command looks


strings only in the third

Note: awk uses the || and && logical operators as in C and UNIX shell.

Example 2 : $ awk F | $3 != manager && $3 != chairman {


> printf %-20s %-12s %d\n, $2, $3, $5} emp.lst
Output:
Sunil kumaar

Accountant

7000

Anil Kummar

Clerk

6000

Dept. of CSE, SJBIT

Page 126

UNIX and Shell Programming

10CS44

Rahul

Accountant

7000

Rakesh

Clerk

6000

The above example illustrates the use of != and && operators. Here all the employee
records other than that of manager and chairman are displayed.
~ and !~ : The Regular Expression Operators:

In awk, special characters, called regular expression operators or metacharacters, can be


used with regular expression to increase the power and versatility of regular expressions.
To restrict a match to a specific field, two regular expression operators ~ (matches) and
!~ (does not match).
Example1: $2 ~ /[cC]ho[wu]dh?ury / || $2 ~ /sa[xk]s ?ena /

Matches second field

Neither manager nor chairman

Example2: $2 !~ /manager | chairman /


Note:

The operators ~ and !~ work only with field specifiers like $1, $2, etc.,.
For instance, to locate g.m s the following command does not display the expected output,
because the word g.m. is embedded in d.g.m or c.g.m.
$ awk F | $3 ~ /g.m./ {printf ..
prints fields including g.m like g.m, d.g.m and c.g.m
To avoid such unexpected output, awk provides two operators ^ and $ that indicates the
beginning and end of the filed respectively. So the above command should be modified as
follows:
$ awk F | $3 ~ /^g.m./ {printf ..
prints fields including g.m only and not d.g.m or c.g.m
The following table depicts the comparison and regular expression matching operators.
Operator

Dept. of CSE, SJBIT

Significance

<

Less than

<=

Less than or equal to

==

Equal to

!=

Not equal to

Page 127

UNIX and Shell Programming

10CS44

>=

Greater than or equal to

>

Greater than

Matches a regular expression

!~

Doesnt matches a regular expression

Table 1: Comparison and regular expression matching operators.

Number Comparison:
Awk has the ability to handle numbers (integer and floating type). Relational test or comparisons
can also be performed on them.
Example: $ awk F | $5 > 7500 {
> printf %-20s %-12s %d\n, $2, $3, $5} emp.lst
Output:

In

ganesh

chairman

15000

jai sharma

manager

9000

rohit

manager

8750

rakesh

manager

8500

the above example, the


details of employees

getting salary greater than 7500 are displayed.


Regular expressions can also be combined with numeric comparison.
Example: $ awk F | $5 > 7500 || $6 ~/1980$/ {
> printf %-20s %-12s %d\n, $2, $3, $5, $6} emp.lst
Output:
ganesh

chairman

15000

30/12/1950

jai sharma

manager

9000

01/01/1980

rohit

manager

8750

10/05/1975

Dept. of CSE, SJBIT

Page 128

UNIX and Shell Programming

10CS44

rakesh

manager

8500

20/05/1975

Rahul

Accountant

6000

01/10/1980

Anil

Clerk

5000

20/05/1980

In the above example, the details of employees getting salary greater than 7500 or whose year of
birth is 1980 are displayed.

Number Processing
Numeric computations can be performed in awk using the arithmetic operators like +, -, /, *, %
(modulus). One of the main feature of awk w.r.t. number processing is that it can handle even
decimal numbers, which is not possible in shell.
Example: $ awk F | $3 == manager {
> printf %-20s %-12s %d\n, $2, $3, $5, $5*0.4} emp.lst
Output:
jai sharma

manager

9000

3600

rohit

manager

8750

3500

rakesh

manager

8500

3250

In the above example, DA is calculated as 40% of basic pay.

Variables
Awk allows the user to use variables of there choice. You can now print a serial number,
using the variable kount, and apply it those directors drawing a salary exceeding 6700:
$ awk F| $3 == director && $6 > 6700 {
kount =kount+1
printf %3f %20s %-12s %d\n, kount,$2,$3,$6 } empn.lst
The initial value of kount was 0 (by default). Thats why the first line is correctly
assigned the number 1. awk also accepts the C- style incrementing forms:
Kount ++
Kount +=2
Printf %3d\n, ++kount
THE f OPTION: STORING awk PROGRAMS INA FILE

Dept. of CSE, SJBIT

Page 129

UNIX and Shell Programming

10CS44

You should holds large awk programs in separate file and provide them with the
.awk extension for easier identification. Lets first store the previous program in the file
empawk.awk:
$ cat empawk.awk
Observe that this time we havent used quotes to enclose the awk program. You
can now use awk with the f filename option to obtain the same output:
Awk F| f empawk.awk empn.lst
THE BEGIN AND END SECTIONS
Awk statements are usully applied to all lines selected by the address, and if there
are no addresses, then they are applied to every line of input. But, if you have to print
something before processing the first line, for example, a heading, then the BEGIN
section can be used gainfully. Similarly, the end section useful in printing some totals
after processing is over.
The BEGIN and END sections are optional and take the form
BEGIN {action}
E N D { act i o n }
These two sections, when present, are delimited by the body of the awk program. You
can use them to print a suitable heading at the beginning and the average salary at the
end. Store this program, in a separate file empawk2.awk
Like the shell, awk also uses the # for providing comments. The BEGIN section
prints a suitable heading , offset by two tabs (\t\t), while the END section prints the
average pay (tot/kount) for the selected lines. To execute this program, use the f option:
$awk F| f empawk2.awk empn.lst
Like all filters, awk reads standard input when the filename is omitted. We can make awk
behave like a simple scripting language by doing all work in the BEGIN section. This is
how you perform floating point arithmetic:
$ awk BEGIN {printf %f\n, 22/7 }
3.142857
This is something that you cant do with expr. Depending on the version of the awk the
prompt may be or may not be returned, which means that awk may still be reading
standard input. Use [ctrl-d] to return the prompt.
BUILT-IN VARIABLES
Awk has several built-in variables. They are all assigned automatically, though it
is also possible for a user to reassign some of them. You have already used NR, which
signifies the record number of the current line. Well now have a brief look at some of the
other variable.
Dept. of CSE, SJBIT

Page 130

UNIX and Shell Programming

10CS44

The FS Variable: as stated elsewhere, awk uses a contiguous string of spaces as the
default field delimeter. FS redefines this field separator, which in the sample database
happens to be the |. When used at all, it must occur in the BEGIN section so that the body
of the program knows its value before it starts processing:
BEGIN {FS=|}
This is an alternative to the F option which does the same thing.
The OFS Variable: when you used the print statement with comma-separated arguments,
each argument was separated from the other by a space. This is awks default output field
separator, and can reassigned using the variable OFS in the BEGIN section:
BEGIN { OFS=~ }
When you reassign this variable with a ~ (tilde), awk will use this character for delimiting
the print arguments. This is a useful variable for creating lines with delimited fields.
The NF variable: NF comes in quite handy for cleaning up a database of lines that dont
contain the right number of fields. By using it on a file, say emp.lst, you can locate those
lines not having 6 fields, and which have crept in due to faulty data entry:
$awk BEGIN { FS = | }
NF !=6 {
Print Record No , NR, has , fields} empx.lst
The FILENAME Variable: FILENAME stores the name of the current file being
processed. Like grep and sed, awk can also handle multiple filenames in the command
line. By default, awk doesnt print the filename, but you can instruct it to do so:
$6<4000 {print FILENAME, $0 }
With FILENAME, you can device logic that does different things depending on the file
that is processed.
ARRAYS
An array is also a variable except that this variable can store a set of values or
elements. Each element is accessed by a subscript called the index. Awk arrays are
different from the ones used in other programming languages in many respects:
They are not formally defined. An array is considered declared the
moment it is used.
Array elements are initialized to zero or an empty string unless initialized
explicitly.
Arrays expand automatically.
The index can be virtually any thing: it can even be a string.
Dept. of CSE, SJBIT

Page 131

UNIX and Shell Programming

10CS44

In the program empawk3.awk, we use arrays to store the totals of the basic pay, da, hra
and gross pay of the sales and marketing people. Assume that the da is 25%, and hra 50%
of basic pay. Use the tot[] array to store the totals of each element of pay, and also the
gross pay:
Note that this time we didnt match the pattern sales and marketing specifically in a field.
We could afford to do that because the patterns occur only in the fourth field, and theres
no scope here for ambiguity. When you run the program, it outputs the average of the two
el em en t s o f p ay :
$ awk f empawk3.awk empn.lst

C-programmers will find the syntax quite comfortable to work with except that awk simplifies a
number of things that require explicit specifications in C. there are no type declarations, no
initialization and no statement terminators.
Associative arrays
Even though we used integers as subscripts in the tot [ ] array, awk doesnt treat array
indexes as integers. Awk arrays are associative, where information is held as key-value pairs. The
index is the key that is saved internally as a string. When we set an array element using
mon[1]=mon, awk converts the number 1 to a string. Theres no specified order in which the
array elements are stored. As the following example suggests, the index 1 is different from
01 :
$ awk BEGIN {
direction [N] = North ; direction [S] ;
direction [E] = East ; direction [W] = West ;]
printf(N is %s and W is %s \n, direction[N], direction [W]);

Mon[1] = Jan; mon[1] = january ; mon[01] = JAN ;


Printf(mon is %s\n, mon[1]);
Printf(mon[01] is also %s\n,mon[01]);
Printf(mon[\1\] is also %s \n, mon[1]);
Printf(But mon[\01\] is %s\n, mon[01]);
}
There are two important things to be learned from this output. First, the setting with index 1
overwrites the setng made with index 1. accessing an array element with subscript 1 and 01
actually locates the element with subscript 1. Also note that mon[1] is different from
mon[01].

Dept. of CSE, SJBIT

Page 132

UNIX and Shell Programming

10CS44

ENVIRON[]: The Environment Array:


You may sometimes need to know the name of the user running the program or the home
directing awk maintains the associative array, ENVIRON[], to store all environment variables.
This POSIX requirement is met by recent version of awk including nawk and gawk. This is how
we access the shell variable , HOME and PATH, from inside an awk program:
$nawk BEGIN {
>print HOME = ENVIRON[HOME]
>print PATH = ENVIRON[PATH]
>}

FUNCTIONS
Awk has several built in functions, performing both arithmetic and string operations. The
arguments are passed to a function in C-style, delimited by commas and enclosed by a matched
pair of parentheses. Even though awk allows use of functions with and without parentheses (like
printf and printf()), POSIX discourages use of functions without parentheses.
Some of these functions take a variable number of arguments, and one (length) uses no arguments
as a variant form. The functions are adequately explained here so u can confidently use them in
perl which often uses identical syntaxes.
There are two arithmetic functions which a programmer will except awk to offer. int calculates
the integral portion of a number (without rounding off),while sqrt calculates square root of a
number. awk also has some of the common string handling function you can hope to find in any
language. There are:
length: it determines the length of its arguments, and if no argument is present, the enire line is
assumed to be the argument. You can use length (without any argument) to locate lines whose
length exceeds 1024 characters:
awk F| length > 1024 empn.lst
you can use length with a field as well. The following program selects those people who have
short names:
awk F| length ($2) < 11 empn.lst
index(s1, s2): it determines the position of a string s2within a larger string s1. This function is
especially useful in validating single character fields. If a field takes the values a, b, c, d or e you
can use this function n to find out whether this single character field can be located within a string
abcde:

Dept. of CSE, SJBIT

Page 133

UNIX and Shell Programming

10CS44

x = index (abcde, b)
This returns the value 2.
substr (stg, m, n): it extracts a substring from a string stg. m represents the starting point of
extraction and n indicates the number of characters to be extracted. Because string values can also
be used for computation, the returned string from this function can be used to select those born
between 1946 and 1951:
awk F| substr($5, 7, 2) > 45 && substr($5, 7, 2) < 52 empn.lst
2365|barun sengupta|director|personel|11/05/47|7800|2365
3564|sudhir ararwal|executive|personnel|06/07/47|7500|2365
4290|jaynth Choudhury|executive|production|07/09/50|6000|9876
9876|jai sharma|director|production|12/03/50|7000|9876
you can never get this output with either sed and grep because regular expressions can never
match the numbers between 46 and 51. Note that awk does indeed posses a mechanism of
identifying the type of expression from its context. It identified the date field string for using
substr and then converted it to a number for making a numeric comparison.
split(stg, arr, ch): it breaks up a string stg on the delimiter ch and stores the fields in an array
arr[]. Heres how yo can convert the date field to the format YYYYMMDD:
$awk F | {split($5, ar, /); print 19ar[3]ar[2]ar[1]} empn.lst
19521212
19501203
19431904
..
You can also do it with sed, but this method is superior because it explicitly picks up the fifth
field, whereas sed would transorm the only date field that it finds.
system: you may want to print the system date at the beging of the report. For running a UNIX
command within a awk, youll have to use the system function. Here are two examples:
BEGIN {
system(tput clear)
system(date)

Clears the screen


Executes the UNIX date command

Dept. of CSE, SJBIT

Page 134

UNIX and Shell Programming

10CS44

CONTROL FLOW- THE if STATEMENT:


Awk has practically all the features of a modern programming language. It has
conditional structures (the if statement) and loops (while or for). They all execute a body of
statements depending on the success or failure of the control command. This is simply a condition
that is specified in the first line of the construct.
Function

Description

int(x)

returns the integer value of x

sqrt(x)

returns the square root of x

length

returns the complete length of line

length(x)

returns length of x

substr(stg, m, n)

returns portion of string of length n, starting from position m in


string stg.

index(1s, s2)

returns position of string s2 in string s1

splicit(stg, arr, ch)

splicit string stg into array arr using ch as delimiter, returns


number of fields.

System(cmd)

runs UNIX command cmd and returns its exit status

The if statement can be used when the && and || are found to be inadequate for certain
tasks. Its behavior is well known to all programmers. The statement here takes the form:
If (condition is true) {
Statement
} else {
Statement
}
Like in C, none of the control flow constructs need to use curly braces if theres only one
statement to be executed. But when there are multiple actions take, the statement must be
enclosed within a pair of curly braces. Moreover, the control command must be enclosed in
parentheses.
Most of the addresses that have been used so far reflect the logic normally used in the if
statement. In a previous example, you have selected lines where the basic pay exceeded 7500, by
using the condition as the selection criteria:
$6 > 7500 {

Dept. of CSE, SJBIT

Page 135

UNIX and Shell Programming

10CS44

An alternative form of this logic places the condition inside the action component rather
than the selection criteria. But this form requires the if statement:
Awk F | { if ($6 > 7500) printf .
if can be used with the comparison operators and the special symbols ~ and !~ to match a regular
expression. When used in combination with the logical operators || and &&, awk programming
becomes quite easy and powerful. Some of the earlier pattern matching expressions are rephrased
in the following, this time in the form used by if:
if ( NR > = 3 && NR <= 6 )
if ( $3 == director || $3 == chairman )
if ( $3 ~ /^g.m/ )
if ( $2 !~ / [aA]gg?[ar]+wal/ )
if ( $2 ~[cC]ho[wu]dh?ury|sa[xk]s?ena/ )
To illustrate the use of the optional else statement, lets assume that the dearness
allowance is 25% of basic pay when the latter is less than 600, and 1000 otherwCSE. The if-else
structure that implants this logic looks like this:
If ( $6 < 6000 )
da = 0.25*$6
else
da = 1000
You can even replace the above if construct with a compact conditional structure:
$6 < 6000 ? da = 0.25*$6 : da = 1000
This is the form that C and perl use to implement the logic of simple if-else construct.
The ? and : act as separator of the two actions.
When you have more than one statement to be executed, they must be bounded by a pair
of curly braces (as in C). For example, if the factors determining the hra and da are in turn
dependent on the basic pay itself, then you need to use terminators:
If ( $6 < 6000 ) {
hra = 0.50*$6
da = 0.25*$6
}else {

Dept. of CSE, SJBIT

Page 136

UNIX and Shell Programming

10CS44

hra = 0.40*$6
da = 1000
}

LOOPING WITH for:


awk supports two loops for and while. They both execute the loop body as long as the
control command returns a true value. For has two forms. The easier one resembles its C
counterpart. A simple example illustrates the first form:
for (k=0; k<=9; k+=2)
This form also consists of three components; the first component initializes the value of k, the
second checks the condition with every iteration, while the third sets the increment used for every
iteration. for is useful for centering text, and the following examples uses awk with echo in a
pipeline to do that:
$echo
>Income statement\nfor\nthe month of august, 2002\nDepartment : Sales |
>awk { for (k=1 ; k < (55 length($0)) /2 ; k++)
>printf %s,
>printf $0}
Income statement
for
the month of August, 2002
Department : Sales
The loop here uses the first printf statement to print the required number of spaces (page width
assumed to be 55 ). The line is then printed with the second printf statement, which falls outside
the loop. This is useful routine which can be used to center some titles that normally appear at the
beginning of a report.

Using for with an Associative Array:


The second form of the for loop exploits the associative feature of awks arrays. This
form is also seen in perl but not in the commonly used languages like C and java. The loop selects
each indexof an array:
for ( k in array )

Dept. of CSE, SJBIT

Page 137

UNIX and Shell Programming

10CS44

commamds
Here, k is the subscript of the array arr. Because k can also be a string, we can use this loop to
print all environment variables. We simply have to pick up each subscript of the ENVIRON
array:
$ nawk BIGIN {
>for ( key in ENVIRON )
>print key = ENVIRON [key]
>}
LOGNAME=praveen
MAIL=/var/mail/Praveen
PATH=/usr/bin::/usr/local/bin::/usr/ccs/bin
TERM=xterm
HOME=/home/praveen
SHELL=/bin/bash
Because the index is actually a string, we can use any field as index. We can even use elements of
the array counters. Using our sample databases, we can display the count of the employees,
grouped according to the disgnation ( the third field ). You can use the string value of $3 as the
subscript of the array kount[]:
$awk F| { kount[$3]++ }
>END { for ( desig in kount)
>print desig, kount[desig] } empn.lst
g.m

chairman

executive

director 4
manager

d.g.m

The program here analyzes the databases to break up of the employees, grouped on their
designation. The array kount[] takes as its subscript non-numeric values g.m., chairman,
executive, etc.. for is invoked in the END section to print the subscript (desig) and the number of

Dept. of CSE, SJBIT

Page 138

UNIX and Shell Programming

10CS44

occurrence of the subscript (kount[desig]). Note that you dont need to sort the input file to print
the report!

LOOPING WITH while


The while loop has a similar role to play; it repeatedly iterates the loop until the
command succeeds. For example, the previous for loop used for centering text can be easily
replaced with a while construct:
k=0
while (k < (55 length($0))/2) {
printf %s,
k++
}
print $0
The loop here prints a space and increments the value of k with every iteration. The condition (k
< (55 length($0))/2) is tested at the beginning of every iteration, and the loop body only if the
test succeeds. In this way, entire line is filled with a string spacesbefore the text is printed with
print $0.
Not that the length function has been used with an argument ($0). This awk understands to be
the entire line. Since length, in the absence of arguments, uses the entire line anyway, $0 can be
omitted. Similarly, print $0 may also be replaced by simply print.
Programs
1)awk script to delete duplicate
lines in a file.
BEGIN { i=1;}
{
flag=1;
for(j=1; j<i && flag ; j++ )
{
if( x[j] == $0 )
flag=0;
}

Dept. of CSE, SJBIT

Page 139

UNIX and Shell Programming

10CS44

if(flag)
{
x[i]=$0;
printf "%s \n",x[i];
i++;
}
}
Run1:
[root@localhost shellprgms]$ cat >for7.txt
hello
world
world
hello
this
is
this
Output:
[root@localhost shellprgms]$ awk -F "|" -f 11.awk for7.txt
hello
world
this
is
2)awk script to print the transpose of a matrix.
BEGIN{
system(tput clear)
count =0

Dept. of CSE, SJBIT

Page 140

UNIX and Shell Programming

10CS44

}
{
split($0,a);
for(j=1;j<=NF;j++)

{ count = count+1
arr[count] =a[j]
}
K=NF
}
END{
printf(Transpose\n);
for(j=1;j<=K;j++)
{
for(i=j; i<=count; i=i+K)
{
printf(%s\t, arr[i]);
}
printf(\n);
}
}
Run1:
[root@localhost shellprgms]$ qwk f p8.awk
2

Dept. of CSE, SJBIT

Page 141

UNIX and Shell Programming

10CS44

Transpose
2

3)Awk script that folds long line into 40 columns. Thus any line that exceeds 40 Characters
must be broken after 40th and is to be continued with the residue. The inputs to be supplied
through a text file created by the user.
BEGIN{
start=1; }
{ len=length;
for(i=$0; length(i)>40; len-=40)
{
print substr(i,1,40) "\\"
i=substr(i,41,len);
}
print i; }
Run1:
[root@localhost shellprgms]$ awk -F "|" -f 15.awk sample.txt
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\
aaaaaaaaaaaa
aaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\
aaaaaaaaa
Output:
[root@localhost shellprgms]$ cat sample.txt
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaa

Dept. of CSE, SJBIT

Page 142

UNIX and Shell Programming

10CS44

aaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
4)This is an awk program to provide extra spaces at the end of the line so that the line length is
maintained as 127.
awk { y=127 length($0)
printf %s, $0
if(y > 0)
for(i=0;i<y;i++)
printf %s,
printf \n
} foo
5)A file contains a fixed number of fields in the form of space-delimited numbers. This is an awk
program to print the lines as well as total of its rows.
awk { split($0,a)
for (i=1;i<=NF;i++) {
row[NR]+=a[$i]
}

printf %s, $0
printf %d\n, row[NR]
} f oo

Dept. of CSE, SJBIT

Page 143

UNIX and Shell Programming

10CS44

UNIT 8
8.1. Perl The Mater Manipulator
Introduciton
The following sections tell you what Perl is, the variables and operators in perl, the string
handling functions. The chapter also discusses file handling in perl as also the lists, arrays and
associative arrays (hashes) that have made perl a popular scripting language. One or two lines of
code in perl accomplish many lines of code in a high level language. We finally discuss writing
subroutines in perl.

Objectives

perl preliminaries
The chop function
Variables and Operators
String handling functions
Specifying filenames in a command line
$_(Default Variable)
$. (Current Line Number) and .. (The Range Operator)
Lists and Arrays
ARGV[]: Command Line Arguments
foreach: Looping Through a List
split: Splitting into a List or Array
join: Joining a List
dec2bin.pl: Converting a Decimal Number to Binary
grep: Searching an Array for a Pattern
Associative Arrays
Regular Expressions and Substitution
File Handling
Subroutines
Conclusion

Perl preliminaries
Perl: Perl stands for Practical Extraction and Reporting Language. The language was developed
by Larry Wall. Perl is a popular programming language because of its powerful pattern matching
capabilities, rich library of functions for arrays, lists and file handling. Perl is also a popular
choice for developing CGI (Common Gateway Interface) scripts on the www (World Wide Web).
Perl is a simple yet useful programming language that provides the convenience of shell scripts
and the power and flexibility of high-level programming languages. Perl programs are interpreted
and executed directly, just as shell scripts are; however, they also contain control structures and
operators similar to those found in the C programming language. This gives you the ability to
write useful programs in a very short time.

Dept. of CSE, SJBIT

Page 144

UNIX and Shell Programming

10CS44

Perl is a freeware and can be obtained from http://www.perl.com or http://www.activestate.com


(Perl interpreter for Windows).
A perl program runs in a special interpretive model; the entire script is compiled internally in
memory before being executed. Script errors, if any, are generated before execution. Unlike awk,
printing isnt perls default action. Like C, all perl statements end with a semicolon. Perl
statements can either be executed on command line with the e option or placed in .pl files. In
Perl, anytime a # character is recognized, the rest of the line is treated as a comment.
The following is a sample perl script.
#!/usr/bin/perl
# Script: sample.pl Shows the use of variables
#
print(Enter your name: );
$name=<STDIN>;
Print(Enter a temperature in Centigrade: );
$centigrade=<STDIN>;
$fahr=$centigrade*9/5 + 32;
print The temperature in Fahrenheit is $fahr\n;
print Thank you $name for using this program.
There are two ways of running a perl script. One is to assign execute (x) permission on the script
file and run it by specifying script filename (chmod +x filename). Other is to use perl interpreter
at the command line followed by the script name. In the second case, we dont have to use the
interpreter line viz., #!/usr/bin/perl.

The chop function


The chop function is used to remove the last character of a line or string. In the above program,
the variable $name will contain the input entered as well as the newline character that was entered
by the user. In order to remove the \n from the input variable, we use chop($name).
Example: chop($var); will remove the last character contained in the string specified by the
variable var.
Note that you should use chop function whenever you read a line from the keyboard or a file
unless you deliberately want to retain the newline character.

Variables and Operators


Dept. of CSE, SJBIT

Page 145

UNIX and Shell Programming

10CS44

Perl variables have no type and need no initialization. However we need to precede the variable
name with a $ for both variable initialization as well as evaluation.
Example:

$var=10;
print $var;

Some important points related to variables in perl are:


1. When a string is used for numeric computation or comparison, perl converts it into a
number.
2. If a variable is undefined, it is assumed to be a null string and a null string is numerically
zero. Incrementing an uninitialized variable returns 1.
3. If the first character of a string is not numeric, the entire string becomes numerically
equivalent to zero.
4. When Perl sees a string in the middle of an expression, it converts the string to an integer.
To do this, it starts at the left of the string and continues until it sees a letter that is not a
digit. Example: "12O34" is converted to the integer 12, not 12034.

Comparison Operators
Perl supports operators similar to C for performing numeric comparison. It also provides
operators for performing string comparison, unlike C where we have to use either strcmp() or
strcmpi() for string comparison. The are listed next.
Numeric comparison

String comparison

==

eq

!=

ne

>

gt

<

lt

>=

ge

<=

le

Concatenating and Repeating Strings


Perl provides three operators that operate on strings:

The . operator, which joins two strings together;


The x operator, which repeats a string; and
The .= operator, which joins and then assigns.

The . operator joins the second operand to the first operand:

Dept. of CSE, SJBIT

Page 146

UNIX and Shell Programming

10CS44

Example:
$a = Info" . sys";

# $a is now Infosys"

$x=microsoft; $y=.com; $x=$x . $y; # $x is now microsoft.com


This join operation is also known as string concatenation.
The x operator (the letter x) makes n copies of a string, where n is the value of the right operand:
Example:
$a = R" x 5;

# $a is now RRRRR"

The .= operator combines the operations of string concatenation and assignment:


Example:
$a = VTU";
$a .= Belgaum";

# $a is now VTU Belgaum"

String Handling Functions


Perl has all the string handling functions that you can think of. We list some of the frequently
used functions are:
length determines the length of its argument.
index(s1, s2) determines the position of a string s2 within string s1.
substr(str,m,n) extracts a substring from a string str, m represents the starting point of extraction
and n indicates the number of characters to be extracted.
uc(str) converts all the letters of str into uppercase.
ucfirst(str) converts first letter of all leading words into uppercase.
reverse(str) reverses the characters contained in string str.

Specifying Filenames in Command Line


Unlike awk, perl provides specific functions to open a file and perform I/O operations on it. We
will look at them in a subsequent section. However, perl also supports special symbols that
perform the same functionality. The diamond operator, <> is used for reading lines from a file.
When you specify STDIN within the <>, a line is read from the standard input.
Example:
1. perl e print while (<>) sample.txt

Dept. of CSE, SJBIT

Page 147

UNIX and Shell Programming

10CS44

2. perl e print <> sample.txt


In the first case, the file opening is implied and <> is used in scalar context (reading one line).
In the second case, the loop is also implied but <> is interpreted in list context (reading all lines).
The following script will print all Guptas and Agarwal/Aggarwals contained in a file (specified
using an ERE) that is specified as a command line parameter along with the script name.
#!/usr/bin/perl
printf(%30s, LIST OF EMPLOYEES\n);
while(<>) {
print if /\bGupta|Ag+[ar][ar]wal/ ;
}

$_ : The Default Variable


perl assigns the line read from input to a special variable, $_, often called the default variable.
chop, <> and pattern matching operate on $_ be default. It represents the last line read or the last
pattern matched.
By default, any function that accepts a scalar variable can have its argument omitted. In this case,
Perl uses $_, which is the default scalar variable. chop, <> and pattern matching operate on $_ by
default, the reason why we did not specify it explicitly in the print statement in the previous
script. The $_ is an important variable, which makes the perl script compact.
For example, instead of writing
$var = <STDIN>;
chop($var);
you can write,
chop(<STDIN>);
In this case, a line is read from standard input and assigned to default variable $_, of which the
last character (in this case a \n) will be removed by the chop() function.
Note that you can reassign the value of $_, so that you can use the functions of perl without
specifying either $_ or any variable name as argument.

$. (Current Line number) And .. (The range operator)


$. is the current line number. It is used to represent a line address and to select lines from
anywhere.

Dept. of CSE, SJBIT

Page 148

UNIX and Shell Programming

10CS44

Example:
perl ne print if ($. < 4) in.dat

# is similar ro head n 3 in.dat

perl ne print if ($. > 7 && $. < 11) in.dat # is similar to sed n 8,10p
.. is the range operator.
Example:
perl ne print if (1..3) in.dat # Prints lines 1 to 3 from in.dat
perl ne print if (8..10) in.dat # Prints lines 8 to 10 from in.dat
You can also use compound conditions for selecting multiple segments from a file.
Example: if ((1..2) || (13..15)) { print ;} # Prints lines 1 to 2 and 13 to 15

Lists and Arrays


Perl allows us to manipulate groups of values, known as lists or arrays. These lists can be
assigned to special variables known as array variables, which can be processed in a variety of
ways.
A list is a collection of scalar values enclosed in parentheses. The following is a simple example
of a list:
(1, 5.3, "hello", 2)
This list contains four elements, each of which is a scalar value: the numbers 1 and 5.3, the string
"hello", and the number 2.
To indicate a list with no elements, just specify the parentheses: ()
You can use different ways to form a list. Some of them are listed next.

Lists can also contain scalar variables:


(17, $var, "a string")

A list element can also be an expression:


(17, $var1 + $var2, 26 << 2)

Scalar variables can also be replaced in strings:


(17, "the answer is $var1")

The following is a list created using the list range operator:


(1..10) same as (1, 2, 3, 4, 5, 6, 7, 8, 9, 10)

The list range operator can be used to define part of a list:


(2, 5..7, 11)

Dept. of CSE, SJBIT

Page 149

UNIX and Shell Programming

10CS44

The above list consists of five elements: the numbers 2, 5, 6, 7 and 11

Arrays
Perl allows you to store lists in special variables designed for that purpose. These variables are
called array variables. Note that arrays in perl need not contain similar type of data. Also arrays in
perl can dynamically grow or shrink at run time.
@array = (1, 2, 3); # Here, the list (1, 2, 3) is assigned to the array variable @array.
Perl uses @ and $ to distinguish array variables from scalar variables, the same name can be used
in an array variable and in a scalar variable:
$var = 1;
@var = (11, 27.1, "a string");
Here, the name var is used in both the scalar variable $var and the array variable @var. These are
two completely separate variables. You retrieve value of the scalar variable by specifying $var,
and of that of array at index 1 as $var[1] respectively.
Following are some of the examples of arrays with their description.
x = 27;

# list containing one element

@y = @x;

# assign one array variable to another

@x = (2, 3, 4);
@y = (1, @x, 5);

# the list (2, 3, 4) is substituted for @x, and the resulting list
# (1, 2, 3, 4,5) is assigned to @y.

$len = @y;

# When used as an rvalue of an assignment,

@y evaluates to the

# length of the array.


$last_index = $#y;

# $# prefix to an array signifies the last index of the array.

ARGV[]: Command Line Arguments


The special array variable @ARGV is automatically defined to contain the strings entered on the
command line when a Perl program is invoked. For example, if the program (test.pl):
#!/usr/bin/perl
print("The first argument is $ARGV[0]\n");
Then, entering the command
$ test.pl 1 2 3

Dept. of CSE, SJBIT

Page 150

UNIX and Shell Programming

10CS44

produces the following output:


The first argument is 1
Note that $ARGV[0], the first element of the @ARGV array variable, does not contain the name
of the program. This is a difference between Perl and C.

Modifying Array Contents


For deleting elements at the beginning or end of an array, perl uses the shift and pop functions. In
that sense, array can be thought of both as a stack or a queue.
Example:
@list = (3..5, 9);
shift(@list);

# The 3 goes away, becomes 4 5 9

pop(@list);

# Removes last element, becomes 4 5

The unshift and push functions add elements to an array.


unshift(@list, 1..3);

# Adds 1, 2 and 3 - 1 2 3 4 5

push(@list,9); # Pushes 9 at end - 1 2 3 4 5 9


The splice function can do everything that shift, pop, unshift and push can do. It uses upto four
arguments to add or remove elements at any location in the array. The second argument is the
offset from where the insertion or removal should begin. The third argument represents the
number of elements to be removed. If it is 0, elements have to be added. The new replaced list is
specified by the fourth argument (if present).
splice(@list, 5, 0, 6..8); # Adds at 6th location, list becomes 1 2 3 4 5 6 7 8 9
splice(@list, 0, 2); # Removes from beginning, list becomes 3 4 5 6 7 8 9

foreach: Looping Through a List


foreach construct is used to loop through a list. Its general form is,
foreach $var in (@arr) {
statements
}
Example: To iterate through the command line arguments (that are specified as numbers) and find
their square roots,
foreach $number (@ARGV) {

Dept. of CSE, SJBIT

Page 151

UNIX and Shell Programming


print(The square root of $number is .

10CS44
sqrt($number) .

\n);
}
You can even use the following code segment for performing the same task. Here note the use of
$_ as a default variable.
foreach (@ARGV) {
print(The square root of $_ is . sqrt() . \);
}
Another Example
#!/usr/bin/perl
@list = ("This", "is", "a", "list", "of", "words");
print("Here are the words in the list: \n");
foreach $temp (@list) {
print("$temp ");
}
print("\n");
Here, the loop defined by the foreach statement executes once for each element in the list @list.
The resulting output is
Here are the words in the list:
This is a list of words
The current element of the list being used as the counter is stored in a special scalar variable,
which in this case is $temp. This variable is special because it is only defined for the statements
inside the foreach loop.
perl has a for loop as well whose syntax similar to C.
Example:
for($i=0 ; $i < 3 ; $i++) { . . .

split: Splitting into a List or Array


There are two important array handling functions in perl that are very useful in CGI
programming, viz., split and join.

Dept. of CSE, SJBIT

Page 152

UNIX and Shell Programming

10CS44

split breaks up a line or expression into fields. These fields are assigned either to variables or an
array.
Syntax:
($var1, $var2, $var3 . ) = split(/sep/, str);
@arr = split(/sep/, str);
It splits the string str on the pattern sep. Here sep can be a regular expression or a literal string.
str is optional, and if absent, $_ is used as default. The fields resulting from the split are assigned
to a set of variables , or to an array.

join: Joining a List


It acts in an opposite manner to split. It combines all array elements in to a single string. It uses
the delimiter as the first argument. The remaining arguments could be either an array name or a
list of variables or strings to be joined.
$x = join(" ", "this", "is", "a", "sentence"); # $x becomes "this is a sentence".
@x = ("words","separated","by");
$y = join("::",@x,"colons");

#$y becomes "words::separated::by::colons".

To undo the effects of join(), call the function split():


$y = "words::separated::by::colons";
@x = split(/::/, $y);

dec2bin: Converting a Decimal Number to Binary


Here we summarize our understanding of array handling functions with an illustrative script that
converts a input decimal number into its binary equivalent. The script logic is to repeatedly divide
the number by two and collecting the remainders and finally printing the reverse of all the
collected remainders. The script is as follows:
#!/usr/bin/perl
foreach $num (@ARGV) {
$temp = $num;
until ($num == 0) {
$bit = $num % 2;
unshift(@bit_arr, $bit);
$num = int($num/2);

Dept. of CSE, SJBIT

Page 153

UNIX and Shell Programming

10CS44

}
$binary_num = join(,@bit_arr);
print (Binary form of $temp is $binary_num\n);
splice(@bit_arr, 0, $#bit_arr+1);
}
The output of the above script (assuming script name is dec2bin.pl) is,
$ dec2bin.pl 10
Binary form of 10 is 1010
$ dec2bin.pl 8 12 15 10
Binary form of 8 is 1000
Binary form of 12 is 1100
Binary form of 15 is 1111
Binary form of 10 is 1010
$

grep: Searching an array for pattern


grep function of perl searches an array for a pattern and returns an array which stores the array
elements found in the other array.
Example:
$found_arr = grep(/^$code/, @dept_arr); # will search for the specified $code at the beginning of
the element in the array @dept_arr.

Associative Arrays
In ordinary arrays, you access an array element by specifying an integer as the index:
@fruits = (9, 23, 11);
$count = $fruits[0];

# $count is now 9

In associative arrays, you do not have to use numbers such as 0, 1, and 2 to access array elements.
When you define an associative array, you specify the scalar values you want to use to access the
elements of the array. For example, here is a definition of a simple associative array:
%fruits=("apple", 9, "banana", 23, "cherry", 11);

Dept. of CSE, SJBIT

Page 154

UNIX and Shell Programming

10CS44

It alternates the array subscripts and values in a comma separated strings. i.e., it is basically a
key-value pair, where you can refer to a value by specifying the key.
$fruits{apple} will retrieve 9. $fruits{banana} will retrieve 23 and so on.
Note the use of {} instead of [] here.
There are two associative array functions, keys and values.
keys: Holds the list of subscripts in a separate array.
values: Holds the value of each element in another array.
Normally, keys returns the key strings in a random sequence. To order the list alphabetically, use
sort function with keys.
1. foreach $key (sort(keys %region)) { # sorts on keys in the associative array, region
2. @key_list = reverse sort keys %region; # reverse sorts on keys in assoc. array, region

Regular Expressions and Substitution


perl supports different forms of regular expressions we have studied so far. It makes use of the
functions s and tr to perform substitution and translation respectively.

The s function: Substitution


You can use the =~ operator to substitute one string for another:
$val =~ s/abc/def/;

# replace abc with def

$val =~ s/a+/xyz/;

# replace a, aa, aaa, etc., with xyz

$val =~ s/a/b/g;

# replace all a's with b's;It also uses the g flag for global
# substitution

Here, the s prefix indicates that the pattern between the first / and the second is to be replaced by
the string between the second / and the third.

The tr function: Translation


You can also translate characters using the tr prefix:
$val =~ tr/a-z/A-Z/;

# translate lower case to upper

Here, any character matched by the first pattern is replaced by the corresponding character in the
second pattern.

Using Special Characters in Patterns


Dept. of CSE, SJBIT

Page 155

UNIX and Shell Programming

10CS44

The following examples demonstrate the use of special characters in a pattern.


1. The * character matches zero or more of the character it follows:
/jk*l/
# This matches jl, jkl, jkkl, jkkkl, and so on.
2. The + character matches one or more of the preceding character:
/jk+l/
# This matches jkl, jkkl, jkkkl, and so on.
3. The ? character matches zero or one copies of the preceding character:
/jk?l/
# This matches jl or jkl.
4. If a set of characters is enclosed in square brackets, any character in the set is an
acceptable match:
/j[kK]l/
# matches jkl or jKl
5. Consecutive alphanumeric characters in the set can be represented by a dash (-):
/j[k1-3K]l/
# matches jkl, j1l, j2l, j3l or jKl
6. You can specify that a match must be at the start or end of a line by using ^ or $:
/^jkl/
# matches jkl at start of line
/jkl$/

# matches jkl at end of line

7. Some sets are so common that special characters exist to represent them:
\d matches any digit, and is equivalent to [0-9].
\D doesnt match a digit, same as [^0-9].
\w matches any character that can appear in a variable name; it is equivalent to
[A-Za-z0-9_].
\W doesnt match a word character, same as [^a-zA-Z0-9_]
\s matches any whitespace (any character not visible on the screen); it is equivalent to [
\r\t\n\f].
perl accepts the IRE and TRE used by grep and sed, except that the curly braces and
parenthesis are not escaped.
For example, to locate lines longer than 512 characters using IRE:
perl ne print if /.{513,}/ filename # Note that we didnt escape the curly braces

Editing files in-Place


perl allows you to edit and rewrite the input file itself. Unlike sed, you dont have to redirect
output to a temporary file and then rename it back to the original file.
To edit multiple files in-place, use I option.

Dept. of CSE, SJBIT

Page 156

UNIX and Shell Programming

10CS44

perl p I e s/<B>/<STRONG>/g *.html *.htm


The above statement changes all instances of <B> in all HTML files to <STRONG>. The files
themselves are rewritten with the new output. If in-place editing seems a risky thing to do, oyu
can back the files up before undertaking the operation:
perl p I .bak e tr/a-z/A-Z foo[1-4]
This first backs up foo1 to foo1.bak, foo2 to foo2.bak and so on, before converting all lowercase
letters in each file to uppercase.

File Handling
To access a file on your UNIX file system from within your Perl program, you must perform the
following steps:
1. First, your program must open the file. This tells the system that your Perl program wants to
access the file.
2. Then, the program can either read from or write to the file, depending on how you have
opened the file.
3. Finally, the program can close the file. This tells the system that your program no longer needs
access to the file.
To open a file we use the open() function.
open(INFILE, /home/srm/input.dat);
INFILE is the file handle. The second argument is the pathname. If only the filename is supplied,
the file is assumed to be in the current working directory.
open(OUTFILE,>report.dat);

# Opens the file in write mode

open(OUTFILE,>>report.dat); # Opens the file in append mode


The following script demonstrates file handling in perl. This script copies the first three lines of
one file into another.
#!/usr/bin/perl
open(INFILE, desig.dat) || die(Cannot open file);
open(OUTFILE, >desig_out.dat);
while(<INFILE>) {
print OUTFILE if(1..3);
}

Dept. of CSE, SJBIT

Page 157

UNIX and Shell Programming

10CS44

close(INFILE);
close(OUTFILE);

File Tests
perl has an elaborate system of file tests that overshadows the capabilities of Bourne shell and
even find command that we have already seen. You can perform tests on filenames to see whether
the file is a directory file or an ordinary file, whether the file is readable, executable or writable,
and so on. Some of the file tests are listed next, along with a description of what they do.
if -d filename

True if file is a directory

if -e filename

True if this file exists

if -f filename

True if it is a file

if -l filename

True if file is a symbolic link

if -s filename

True if it is a non-empty file

if -w filename

True if file writeable by the person running the program

if -x filename

True if this file executable by the person running the program

if -z filename

True if this file is empty

if -B filename

True if this is a binary file

if -T filename

True if this is a text file

Subroutines
The use of subroutines results in a modular program. We already know the advantages of modular
approach. (They are code reuse, ease of debugging and better readability).
Frequently used segments of code can be stored in separate sections, known as subroutines. The
general form of defining a subroutine in perl is:
sub procedure_name {
# Body of the subroutine
}
Example: The following is a routine to read a line of input from a file and break it into words.
sub get_words {
$inputline = <>;

Dept. of CSE, SJBIT

Page 158

UNIX and Shell Programming

10CS44

@words = split(/\s+/, $inputline);


}
Note: The subroutine name must start with a letter, and can then consist of any number of letters,
digits, and underscores. The name must not be a keyword.
Precede the name of the subroutine with & to tell perl to call the subroutine.
The following example uses the previous subroutine get_words to count the number of
occurrences of the word the.
#!/usr/bin/perl
$thecount = 0;
&get_words;

Call the subroutine

while ($words[0] ne "") {


for ($index = 0; $words[$index] ne "";
$index += 1) {
$thecount += 1 if $words[$index] eq "the";
}
&get_words;
}

Return Values
In perl subroutines, the last value seen by the subroutine becomes the subroutine's return value.
That is the reason why we could refer to the array variable @words in the calling routine.

Dept. of CSE, SJBIT

Page 159

You might also like