Shell programming and simple menus - part 1
Any programmer or system administrator can
benefit from limiting end-user
access to the things that they actually need. For the timid, Unix offers
little help on how to start, and for the adventurous Unix offers too
many simple commands that can cause havoc.
A menu system is an almost mandatory add-on to any Unix system in the real
world. In saying "real world" Unix system, I mean one that doesn't involve
sitting in a dark room hunched over a glowing terminal trying to determine
the next highest prime number.
Commercial menu systems involve more than a simple prompt that dispatches
to some program based on a user selection. But often a simple approach will
get the job done. While I was creating EZMENU for Unix, one customer
required just such a simple solution.
The menu had to:
- Provide one or more prompts.
- Allow the user to select a prompt.
- Execute one or more commands associated with the selection.
The menu also had to provide a method for the user to exit the menu.
The design of the menu is simple, and it provides an excellent vehicle to
learn some shell programming tricks. The logic for a menu can be described
in the following simple steps:
- Display a menu.
- Get the user's menu pick.
- Check that the pick is valid and if not, display an error message and
return to step 1. - If the user's menu pick is to exit, then exit.
- Otherwise, execute the command(s) associated with the menu pick.
- Loop back to step 1.
The menu prompts can be displayed directly using the echo command as in:
echo "Please enter 1 to select Accounts Receivable"
or indirectly using a variable as in:
amenu="Please enter 1 to select Accounts Receivable" echo $amenu
A menu pick can be collected from the user by using the read command which
will read input from the keyboard as in:
echo "Please enter your choice" read answer
Defining functions
Another important feature of the shell (sh or ksh) is the ability to define
a function. A shell function is a collection of one or more shell commands
that are given a function name. A function can be executed by issuing the
name of the function in the shell script as if it were a Unix command.
However, a function must be defined before it can be executed. To define a
function, give it a name followed by an open and close parentheses,
followed by opening and closing curly braces. Within the curly braces place
the commands to be executed.
The following lines define a function
pagedir and then execute it. The function executes
an ls -l command and then pipes
the results through more to create a paging display.
#!/bin/sh
# Define a paged directory listing function
pagedir () { ls -l|more ; }
# and then execute it
pagedir
Repeating a command or set of commands can be done by enclosing the
commands within a while-do-done command.
In the following example the shell logic loops until the user enters
something other than "y."
#!/bin/sh
answer=y
while [ $answer = y ]
do
echo "Hello"
Symantec Backup Exec 12 and Backup Exec System Recovery 8 deliver industry leading Windows data protection and system recovery. Download this whitepaper to find out the top reasons to upgrade and how to get continuous data protection and complete system recovery.
Data and system loss — from a hard drive failure, malicious attack, natural disaster, or simple human error — can happen anytime. Don’t leave your business vulnerable. Make sure you have a secure recovery strategy in place. Symantec's latest backup and system recovery technology can efficiently restore critical applications, individual emails and documents and even restore your entire system in minutes in the event of a loss.
Businesses face a growing challenge to ensure that the IT environment is properly protected. Backup Exec 12 integrates with other applications in the Symantec family of products, to complement your current data protection strategy, keep your data securely backed up and make it recoverable when you need it most.







