Notes Unix
Notes Unix
PART – A
UNIT 1:
1. The UNIX Operating System, the UNIX architecture and Command Usage, The File System
6 Hours
UNIT 2:
UNIT 3:
UNIT 4:
PART – B
UNIT 5:
5. Filters using regular expressions, 6 Hours
UNIT 6:
6. Essential Shell Programming 6 Hours
UNIT 7:
7. awk – An Advanced Filter 7 Hours
UNIT 8:
8. perl - The Master Manipulator 7 Hours
Dept of CSE,SJBIT
Unix and Shell programming 10CS44
Text Book
1. “UNIX – Concepts and Applications”, Sumitabha Das, 4th Edition, Tata McGraw
Hill, 2006.
Reference Books
UNIX and Shell Programming, Behrouz A. Forouzan and Richard F. Gilberg, Thomson,
2005.
Unix & Shell Programming, M.G. Venkateshmurthy, Pearson Education, 2005.
Dept of CSE,SJBIT
Unix and Shell programming 10CS44
Table of Contents
Dept of CSE,SJBIT
Unix & Shell programming 10CS44
UNIT 1
. The Unix Operating System, The UNIX architecture and Command Usage, The File
System
6 Hours
Text Book
Reference Books
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)
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
Processor/Hardware
UNIX Operating system allows complex tasks to be performed with a few keystrokes. It
doesn’t 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.
2. 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).
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.
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 BSD-
based 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.
IBM's AIX
Hewlett-Packard's HPUX
SCO's Open Server Release 5
Silicon Graphics' IRIS
DEC's Digital UNIX
Sun Microsystems' Solaris 2
Conclusion
In this chapter we defined an operating system. We also looked at history of UNIX and
features of UNIX that make it a popular operating system. We also discussed the
convergence of different flavors of UNIX into Single Unix Specification (SUS) and
Portable Operating System Interface for Computing Environments (POSIX).
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
Users
Shell
Kernel
Hardware
System Calls
UNIX architecture comprises of two major components viz., the shell and the kernel. The
kernel interacts with the machine’s hardware and the shell with the user.
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 system’s memory, schedules processes, decides their
priorities.
The shell performs the role of command interpreter. Even though there’s only one kernel
running on the system, there could be several shells in action, one for each user who’s
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.
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.
2. 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.
4. 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.
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.
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.
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
Berkeley’s 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.
When you use man command, it starts searching the manuals starting from section 1. If it
locates a keyword in one section, it won’t 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)
A man page is divided into a number of compulsory and optional sections. Every
command doesn’t 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.
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.
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
Conclusion
In this chapter, we looked at the architecture of UNIX and the division of labor between
two agencies viz., the shell and the kernel. We also looked at the structure and usage of
UNIX commands. The man documentation will be the most valuable source of
documentation for UNIX commands. Also, when the keyboard sequences won’t
sometimes work as expected because of different terminal settings. We listed the possible
remedial keyboard sequences when that happens.
1. 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.
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.
2. 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.
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.
/home/frank/src
6. 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)
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 don’t permit the creation of files and
directories by the user.
E.g.
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),
the system executes the program from the specified directory.
3. Otherwise the PATH variable is used.
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
d directory
- plain file
b block-type special file
c character-type special file
l symbolic link
s 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
-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
Directory Content
/bin Common programs, shared by the system, the system administrator and the users.
Contains references to all the CPU peripheral hardware, which are represented as files with
/dev
special properties.
Most important system configuration files are in /etc, this directory contains data similar to
/etc
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.
Temporary space for use by the system, cleaned upon reboot, so don't use this for saving any
/tmp
work!
/usr 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
/var 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.
Conclusion
In this chapter we looked at the UNIX file system and different types of files UNIX
understands. We also discussed different commands that are specific to directory files
viz., pwd, mkdir, cd, rmdir and ls. These commands have no relevance to ordinary or
device files. We also saw filenaming conventions in UNIX. Difference between the
absolute and relative pathnames was highlighted next. Finally we described some of the
important subdirectories contained under root (/).
UNIT 2
Text Book
2. “UNIX – Concepts and Applications”, Sumitabha Das, 4th Edition, Tata McGraw
Hill, 2006.
Reference Books
UNIX and Shell Programming, Behrouz A. Forouzan and Richard F. Gilberg, Thomson,
2005.
Unix & Shell Programming, M.G. Venkateshmurthy, Pearson Education, 2005.
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 file’s inode to fetch its attributes. It lists seven attributes of all
files in the current directory and they are:
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 84 feb 12 12:30 dept.lst
-rw-r--r-- 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
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 file’s access
rights. It is displayed in the following format:
For Example:
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. It’s important that you understand them because a little learning here can be a
dangerous thing. Faulty file permission is a sure recipe for disaster
Relative Permissions
chmod only changes the permissions specified in the command line and leaves the
other permissions unchanged. Its syntax is:
The command assigns (+) execute (x) permission to the user (u), other permissions
remain unchanged.
Let initially,
Then, it becomes
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:
We have three categories and three permissions for each category, so three octal
digits can describe a file’s permissions completely. The most significant digit represents
user and the least one represents others. chmod can use this three-digit string as the
expression.
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 user’s file’s
permissions. But the system administrator can do anything.
----------
This is simply useless but still the user can delete this file
On the other hand,
-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
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 *
doesn’t 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)
Example:
mkdir c_progs
ls –ld 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.
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
ls -l 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 file’s group owner. No superuser permission is required.
ls –l dept.lst
Source: Sumitabha Das, “UNIX – Concepts and Applications”, 4th edition, Tata
McGraw Hill, 2006
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
vi <filename>
In all probability, the file doesn’t 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 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.
ctrl-l
:set showmode
Messages like INSERT MODE, REPLACE MODE, CHANGE MODE, etc will appear in
the last line.
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
I inserts text at the beginning of line. A appends text at end of line. o opens a new line
below the current line
COMMAND FUNCTION
i inserts text
a appends text
I inserts at beginning of line
A appends text at end of line
o opens line below
O opens line above
r replaces a single character
s replaces with a text
S replaces entire line
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> save as, but overwrites existing file
: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 doesn’t show up on screen but simply performs a function.
To move the cursor in four directions,
k moves cursor up
j moves cursor down
h moves cursor left
l 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:
Example,
0 or |
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
Absolute Movement
The editor displays the total number of lines in the last line
Editing Text
The editing facilitates in vi are very elaborate and invoke the use of operators. They use
operators, such as,
d delete
y yank (copy)
Deleting Text
Moving Text
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
Joining Lines
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.
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)
/ 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
Command Function
We can perform search and replace in execute mode using :s. Its syntax is,
:address/source_pattern/target_pattern/flags
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.
Source: Sumitabha Das, “UNIX – Concepts and Applications”, 4th edition, Tata
McGraw Hill, 2006
UNIT 3
Text Book
3. “UNIX – Concepts and Applications”, Sumitabha Das, 4th Edition, Tata McGraw
Hill, 2006.
Reference Books
UNIX and Shell Programming, Behrouz A. Forouzan and Richard F. Gilberg, Thomson,
2005.
Unix & Shell Programming, M.G. Venkateshmurthy, Pearson Education, 2005.
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
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.
The shell waits for the command to complete and normally can’t 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.
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 * doesn’t 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 .???*
However, if the filename contains a dot anywhere but at the beginning, it need not be
matched explicitly.
Similarly, these characters don’t match the / in a pathname. So, you cannot use
$ cd /usr?local to change to /usr/local.
- To match all filenames with a single-character extension but not the .c ot .o files,
use *.[!co]
- To match all filenames that don’t begin with an alphabetic character,
use [!a-zA-Z]*
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
Standard error: The file (stream) representing error messages that emanate from the
command or shell, connected to the display.
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 doesn’t 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
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
/dev/tty: This file indicates one’s 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.
7. 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.
Examples
$ ls -al | more
$ who | sort | lpr
8. Creating a tee
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
9. 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.
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
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
$ file=$base$ext
$ echo $file // prints foo.c
Conclusion
In this chapter we saw the major interpretive features of the shell. The following is a
summary of activities that the shell performs when a command line is encountered at the
prompt.
Parsing: The shell first breaks up the command line into words using spaces
and tabs as delimiters, unless quoted. All consecutive occurrences of a space
or tab are replaced with a single space.
Variable evaluation: All $-prefixed strings are evaluated as variables, unless
quoted or escaped.
Command substitution: Any command surrounded by backquotes is executed
by the shell, which then replaces the standard output of the command into the
command line.
Redirection: The shell then looks for the characters >, < and >> to open the
files they point to.
Wild-card interpretation: The shell then scans the command line for wild-
cards (the characters *, ?, [ and ]). Any word containing a wild-card is
replaced by a sorted list of filenames that match the pattern. The list of these
filenames then forms the arguments to the command.
PATH evaluation: It finally looks for the PATH variable to determine the
sequence of directories it has to search in order to find the associated binary.
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
1. 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 MS-DOS). 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 to die.
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:
Examples
$ ps
PID TTY TIME CMD
4245 pts/7 00:00:00 bash
5314 pts/7 00:00:00 ps
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
$ ps –e
PID TTY TIME CMD
0 ? 0:34 sched
1 ? 41:55 init
23274 Console 0:03 sh
272 ? 2:47 cron
7015 term/12 20:04 vi
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.
When the system moves to multiuser mode, init forks and execs a getty for every
active communication port.
Each one of these getty’s 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.
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.
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.
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 shell’s & operator and
the nohup command.
If you try to run a command with nohup and haven’t 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 system’s 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.
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.
The idea behind nice is that background jobs should demand less attention from the
system than interactive processes.
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 &
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:
It’s using too much CPU time.
It’s running too long without producing the expected output.
It’s producing too much output to the screen or to a disk file.
It appears to have locked a terminal or some other session.
It’s using the wrong files for input or output because of an operator or
programming error.
It’s 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 isn’t in the background, press <ctrl-c>.
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 can’t kill processes of
other users. To kill all background jobs, enter kill 0.
9. 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 wc –l hugefile.txt
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] Suspended wc –l hugefile.txt
You can bring a job to foreground using fg %jobno OR fg %jobname as,
$ fg %2 OR $ fg %sort
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:
at hh:mm Schedules job at the hour (hh) and minute (mm) specified, using a
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
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 -s”Job 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 is listed in a shell script as one of the commands to run during a system boot-up
sequence. Individual users don’t have permission to run cron directly.
If there’s 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.
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.
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.
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.
Conclusion
In this chapter, we saw an important abstraction of the UNIX operating system viz.,
processes. We also saw the mechanism of process creation, the attributes inherited by the
child from the parent process as well as the shell’s behavior when it encounters internal
commands, external commands and shell scripts. This chapter also discussed background
jobs, creation and controlling jobs as well as controlling processes using signals. We
finally described three commands viz., at, batch and cron for process scheduling, with a
discussion of time command for obtaining time usage statistics of process execution.
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.
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 wasn’t 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 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
shell’s 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.
$ PS1=‘[PWD] ‘
[/home/srm] cd progs
[/home/srm/progs] _
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] _
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).
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.
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.
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 shell’s > 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
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 –
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.
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.
Conclusion
In this chapter, we looked at the environment-related features of the shells, and found
weaknesses in the Bourne shell. Knowledge of Bash and Korn only supplements your
knowledge of Bourne and doesn’t take anything away. It is always advisable to use Bash
or korn as your default login shell as it results in a more fruitful experience, with their
rich features in the form of aliases, history features and in-line command editing features.
UNIT 4
4. More file attributes, Simple filters 7 Hours
Text Book
4. “UNIX – Concepts and Applications”, Sumitabha Das, 4th Edition, Tata McGraw
Hill, 2006.
Reference Books
UNIX and Shell Programming, Behrouz A. Forouzan and Richard F. Gilberg, Thomson,
2005.
Unix & Shell Programming, M.G. Venkateshmurthy, Pearson Education, 2005.
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.
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.
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
Where, 9059 is the inode number and no other file can have the same inode number in the
same file system.
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,
All attributes seem to be identical, but the files could still be copies. It’s 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.
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:
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:
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 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
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 don’t need to maintain two programs as two separate disk files if there is very
little difference between them. A file’s 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 can’t have two linked filenames in two file systems and we can’t 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 doesn’t have the file’s contents, but
simply provides the pathname of the file that actually has the contents.
ln -s note note.sym
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.
It’s important that this time we indeed have two files, and they are not identical.
Removing note.sym won’t 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 uses a fast symbolic link which stores the pathname in the inode itself
provided it doesn’t 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
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 directory’s
read permission is removed, ls wont work. Consider removing the read permission first
from the directory progs,
ls -ld progs
Write permission
We can’t 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.
cp emp.lst progs
• 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
cd progs
When we create files and directories, the permissions assigned to them depend on
the system’s default setting. The UNIX system has the following default permissions for
all files and 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
A UNIX file has three time stamps associated with it. Among them, two are:
• Time of last file modification ls -l
• Time of last access ls –lu
The access time is displayed when ls -l is combined with the -u option. Knowledge of
file‘s 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.
Then, both times are set to the current time and creates the file, if it doesn’t exist.
touch command (without options but with expression) can be used. The expression
consists of MMDDhhmm (month, day, hour and minute).
ls -lu emp.lst
It is possible to change the two times individually. The –m and –a options change the
modification and access times, respectively:
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:
The path_list comprises 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.
Source: Sumitabha Das, “UNIX – Concepts and Applications”, 4th edition, Tata
McGraw Hill, 2006
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 won’t 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 otherwise
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
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
01:accounts:6213
02:progs:5423
03:marketing:6521
04:personnel:2365
05:production:9876
06:sales:1006
…blank lines…
pr options
pr +10 chap01
pr -l 54 chap01
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
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
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.
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.
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).
The expression 55- indicates column number 55 to end of line. Similarly, -3 is the same
as 1-3.
Most files don’t contain fixed length lines, so we have to cut fields rather than columns
(cutting fields).
will display the second and third columns of shortlist and saves the output in
cutlist1. here | is escaped to prevent it as pipeline character
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.
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.
Let us consider that the file address book contains the details of three persons
cat addressbook
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
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.
sort –c shortlist
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
uniq dept.lst
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:
It takes input only from standard input, it doesn’t 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.
exp1=‘|/’ ; exp2=‘~-’
Changing case of text is possible from lower to upper for first three lines of the file.
UNIT 5
5. Filters using regular expressions, 6 Hours
Text Book
5. “UNIX – Concepts and Applications”, Sumitabha Das, 4th Edition, Tata McGraw
Hill, 2006.
Reference Books
UNIX and Shell Programming, Behrouz A. Forouzan and Richard F. Gilberg, Thomson,
2005.
Unix & Shell Programming, M.G. Venkateshmurthy, Pearson Education, 2005.
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.
It scans the file / input for a pattern and displays lines containing the pattern, the
line numbers or filenames where the pattern occurs. It’s a command from a special family
in UNIX for handling search requirements.
will display lines containing sales from the file emp.lst. Patterns with and without quotes
is possible. It’s generally safe to quote the pattern. Quote is mandatory when pattern
involves more than one word. It returns the prompt in case the pattern can’t be located.
When grep is used with multiple filenames, it displays the filenames along with the
output.
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.
all the above three patterns are stored in a separate file pattern.lst
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.
The basic regular expression character subset uses an elaborate meta character set,
overshadowing the shell’s wild-cards, and can perform amazing matches.
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.
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.
Notice that we don’t 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.
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.
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 \.\*
If current version of grep doesn’t support ERE, then use egrep but without the –E
option. -E option treats pattern as an ERE.
# ?include +<stdio.h>
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 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.
Line Addressing
Just similar to head –n 3 emp.lst. Selects first three lines and quits
p prints selected lines as well as all lines. To suppress this behavior, we use –n whenever
we use p command
sed –n ‘1,2p
7,9p
$p’ emp.lst
Selecting multiple groups of lines
There is adequate scope of using the –e and –f options whenever sed is used with
multiple instructions.
Let us consider,
cat instr.fil
1,2p
7,9p
$p
-f option to direct the sed to take its instructions from the file
Context Addressing
Sed –n ‘/sa[kx]s*ena/p
/gupta/p’ emp.lst
Line addressing also is possible. Saves first 500 lines in foo1 and the rest in foo2
Text Editing
sed supports inserting (i), appending (a), changing (c) and deleting (d) commands
for the text.
$ sed ‘1i\
> #include <stdio.h>\
> #include <unistd.h>
> ’foo.c > $$
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
Selects all lines except those containing director, and saves them in olist
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
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 also uses regular expressions for patterns to be substituted. To replace all occurrence
of agarwal, aggarwal and agrawal with simply Agarwal, we have,
We can also use ^ and $ with the same meaning. To add 2 prefix to all emp-ids,
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.
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
Consider the below three lines which does the same job
The // representing an empty regular expression is interpreted to mean that the search and
substituted patterns are the same
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:
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.
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.
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 doesn’t 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.
UNIT 6
Text Book
6. “UNIX – Concepts and Applications”, Sumitabha Das, 4th Edition, Tata McGraw
Hill, 2006.
Reference Books
UNIX and Shell Programming, Behrouz A. Forouzan and Richard F. Gilberg, Thomson,
2005.
Unix & Shell Programming, M.G. Venkateshmurthy, Pearson Education, 2005.
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 “Today’s date : `date`”
echo “This months calendar:”
cal `date “+%m 20%y”` #This month’s 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:
$ chmod +x script.sh
Then invoke the script name as:
$ script.sh
Once this is done, we can see the following output :
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.
The read statement is the shell’s 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
read name
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.
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
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.
Example 1:
$ cat foo
Returns nonzero exit status. The shell variable $? Stores this status.
Example 2:
Exit status is used to devise program logic that braches into different paths depending on
success or failure of a command
The shell provides two operators that aloe conditional execution, the && and ||.
Usage:
cmd1 && cmd2
cmd1 || cmd2
&& delimits two commands. cmd 2 executed only when cmd1 succeeds.
Example1:
Output:
9876 Jai Sharma Director Productions
2356 Rohit Director Sales
Pattern found
Example 2:
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:
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:
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]”
read any
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
04 | antibiotics
05 | OTC drugs
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 doesn’t 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
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 didn’t 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 otherwise.
Run the script four times and redirect the output every time
$emp31.sh>foo
Usage : emp.sh pattern file
$emp31.sh ftp>foo
You didn’t enter two arguments
$emp31.sh henry /etc/passwd>foo
Henry not found in /etc/passwd
$emp31.sh ftp /etc/passwd>foo
ftp:*:325:15:FTP User:/user1/home/ftp:/bin/true
[ 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
stg 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
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”
else
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 didn’t enter two arguments
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”
else
Echo “File is both readable and writable”\
fi
Output:
$ filetest.sh emp3.lst
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
The case statement is the second conditional offered by the shell. It doesn’t 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.
Syntax:
case expression in
Pattern1) commands1 ;;
Pattern2) commands2 ;;
Pattern3) commands3 ;;
…
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
#
echo “ Menu\n
1. List of files\n2. Processes of user\n3. Today’s Date
4. Users of system\n5.Quit\nEnter your option: \c”
read choice
case “$choice” in
1) ls –l;;
2) ps –f ;;
3) date ;;
4) who ;;
5) exit ;;
*) echo “Invalid option”
esac
Output
$ menu.sh
Menu
1. List of files
2. Processes of user
3. Today’s 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.
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 ;;
esac
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
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 $y/$x
1
$ expr 13%5
3
Example1:
Example2:
$ x=5
$ x=`expr $x+1`
$ echo $x
6
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:
Example1:
Example2:
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.
expr can return the location of the first occurrence of a character inside a string.
Example:
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`
command=$0
exe=`expr $lastfile: ‘\(.*\).c’`
case $command in
*runc) $exe ;;
*vic) vi $lastfile;;
*comc) cc –o $exe $lastfile &&
Echo “$lastfile compiled successfully”;;
esac
ln comc.sh comc
ln comc.sh runc
ln comc.sh vic
Output:
$ comc
hello.c compiled successfully.
While: Looping
To carry out a set of instruction repeatedly shell offers three features namely while, until
and for.
Synatx:
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]”
read any
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
04 | antibiotics
05 | OTC drugs
(1) (2)
while true ; do while [ ! -r $1 ] ; do
[ -r $1 ] && break sleep $2
sleep $2 done
done
Synatx:
list here comprises a series of character strings. Each string is assigned to variable
specified.
Example:
Output:
Sources of list:
List from variables: Series of variables are evaluated by the shell before
executing the loop
Example:
Output:
/bin:/usr/bin;/home/local/bin;
/home/user1
Example:
List from wildcards: Here the shell interprets the wildcards as filenames.
Example:
Example: emp.sh
#! /bin/sh
for pattern in “$@”; do
grep “$pattern” emp.lst || echo “Pattern $pattern not found”
done
Output:
They are useful in chaining the extension of group of files. Basename extracts the base
filename from an absolute pathname.
Example1:
$basename /home/user1/test.pl
Ouput:
test.pl
Example2:
Ouput:
test2
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:
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:
$ echo “$@” $@ and $* are interchangeable
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
$shift 2 Shifts 2 places
$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;;
esac
Output:
$emp.sh emp.lst
Insufficient number of arguments
$emp.sh emp.lst Rakesh 1006 9877
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`
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:
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 doesn’t show
up.
A shell script can be made to work non-interactively by supplying inputs through here
document.
Example:
Output:
Enter the pattern to be searched: Enter the file to be used: Searching for director from file
emp.lst
The script search.sh will run non-interactively and display the lines containing “director”
in the file emp.lst.
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:
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.
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|ISE|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
esac
done
Output:
$valcode.sh
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”:’.*’`
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.
#!/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
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
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"
else
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:
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:
Run2:
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
Run1:
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
else
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
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
trap “ " 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
exit
fi
echo "invalid password!"
done
else
****
UNIT 7
Text Book
7. “UNIX – Concepts and Applications”, Sumitabha Das, 4th Edition, Tata McGraw
Hill, 2006.
Reference Books
UNIX and Shell Programming, Behrouz A. Forouzan and Richard F. Gilberg, Thomson,
2005.
Unix & Shell Programming, M.G. Venkateshmurthy, Pearson Education, 2005.
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.
Syntax:
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.
Output:
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
awk ‘/manager/ { print }’ emp.lst
awk ‘/manager/ { print $0}’ emp.lst $0 specifies complete line.
Awk uses special parameter, $0, to indicate entire line. It also uses $1, $2, $3 to identify
fields. These special parameters have to be specified in single quotes so that they will not
be interpreted by the shell.
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:
2 Jai Sharma Manager Productions
3 Rahul Accountant Productions
4 Rakesh Clerk Productions
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
8 Sunil kumaar Accountant
4 Anil Kummar Clerk
Here, the name and designation have been printed in spaces 20 and 12 characters wide
respectively.
Example1: use of |
printf “%3d %-20s %-12s \n”, NR, $2, $3 | “sort”
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.
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
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 prints Hello
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 3: x = “UNIX”
y = “LINUX”
print x “&” y prints UNIX & LINUX
Expressions also have true and false values associated with them. A nonempty string or
any positive number has true value.
awk also provides the comparison operators like >, <, >=, <= ,==, !=, etc..,
Output:
Output:
The above example illustrates the use of != and && operators. Here all the employee
records other than that of manager and chairman are displayed.
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.
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:
The following table depicts the comparison and regular expression matching operators.
Operator Significance
< Less than
<= Less than or equal to
== Equal to
!= Not equal to
>= Greater than or equal to
> Greater than
~ Matches a regular expression
!~ Doesn’t matches a regular expression
Number Comparison:
Awk has the ability to handle numbers (integer and floating type). Relational test or
comparisons can also be performed on them.
Output:
In the above example, the details of employees getting salary greater than 7500 are
displayed.
Output:
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:
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). That’s 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
$ cat empawk.awk
Observe that this time we haven’t used quotes to enclose the awk program. You
can now use awk with the –f filename option to obtain the same output:
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:
This is something that you can’t 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. We’ll now have a brief look at some of the
other variable.
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=”|”}
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 awk’s 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 don’t
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:
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 doesn’t print the filename, but you can instruct it to do so:
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.
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 didn’t 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 there’s
no scope here for ambiguity. When you run the program, it outputs the average of the two
elements of pay:
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 doesn’t 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. There’s 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” ;]
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:
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:
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[]. Here’s how yo can convert the date field to the format YYYYMMDD:
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, you’ll have to use the system function. Here are two
examples:
BEGIN {
system(“tput clear”) Clears the screen
system(“date”) Executes the UNIX date command
}
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 there’s
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 {
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:
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, let’s assume that the dearness
allowance is 25% of basic pay when the latter is less than 600, and 1000 otherwise. 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:
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 {
hra = 0.40*$6
da = 1000
}
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:
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.
for ( k in array )
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[]:
g.m 4
chairman 1
executive 2
director 4
manager 2
d.g.m 2
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 occurrence of the subscript (kount[desig]). Note that you don’t need to sort the
input file to print the report!
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;
}
if(flag)
{
x[i]=$0;
printf "%s \n",x[i];
i++;
}
}
Run1:
BEGIN{
system(“tput clear”)
count =0
}
{
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:
Transpose
2 5
3 6
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:
Output:
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]
} ’ foo
----------------------------------------------------------------------------------
UNIT 8
Text Book
8. “UNIX – Concepts and Applications”, Sumitabha Das, 4th Edition, Tata McGraw
Hill, 2006.
Reference Books
UNIX and Shell Programming, Behrouz A. Forouzan and Richard F. Gilberg, Thomson,
2005.
Unix & Shell Programming, M.G. Venkateshmurthy, Pearson Education, 2005.
.
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
1. 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.
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 isn’t perl’s 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.
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 don’t have to use the interpreter line viz., #!/usr/bin/perl.
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.
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"
The following script will print all Gupta’s and Agarwal/Aggarwal’s 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/ ;
}
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.
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.
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.
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.
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
Example: To iterate through the command line arguments (that are specified as numbers)
and find their square roots,
foreach $number (@ARGV) {
print(“The square root of $number is ” .
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.
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.
$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
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
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.
Here, any character matched by the first pattern is replaced by the corresponding
character in the second pattern.
[A-Za-z0-9_].
\W doesn’t 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 didn’t escape the curly braces
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>) {
19. 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 = <>;
@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.
Conclusion
Perl is a programming language that allows you to write programs that manipulate files,
strings, integers, and arrays quickly and easily. perl is a superset of grep, tr, sed, awk and
the shell. perl also has functions for inter- process communication. perl helps in
developing minimal code for performing complex tasks. The UNIX spirit lives in perl.
perl is popularly used as a CGI scripting lan