CSC3320 Lab Assignment 5 - In-Lab Solution

Lab Assignment 5 - In-Lab
Purpose: Learn how to write basic shell script.
Write a report by answering the questions and upload the report (named as Lab5_P1_FirstNameLastName.pdf or
Lab5_P1_FirstNameLastName.doc) to google classroom. This lab assignment is related to the slides
#12 to #14 in chapter 4 Part 1:
Now it is your turn to create your first shell script file by following the steps below.
Step 1: Go to your home directory and create a new file named as simple.sh (vi simple.sh or nano simple.sh), then include following lines in your simple.sh.
Question 1) : What did you see in the output of step 3?
Step 4: Execute this file by adding ./ before the its name.
$ ./simple.sh
Question 2) : What did you see in the output of step 4? Step 5: Try following command to make simple.sh executable.
$chmod a+x simple.sh
Step 6: Execute this file again.
$ ./simple.sh
Note: you must type ./ before the name. This is because current working directory is not in PATH. However, you can modify the value of PATH variable and add current working directory into it by referring to next part.
Question 3): Attach a screenshot of the output in step 6.
Question 4): Describe the meaning of -n option in echo command.
Read the slides #13 in Chapter 4 and then answer the following two questions.
Question 5): Is "Simple Script" a comment? If not, what is the meaning of it or why we use it?
Question 6): Is "#!/bin/bash" a comment? If not, what is the meaning of it or why we use it in first line?
Part 2:
To discard the ./ before the script file name when executing it, we need to change the PATH variable's value and add current working directory into it.
Step 7: Print out the value stored in PATH variable.
Question 7) : How many directories you can find in the output? Note: the directories are separated by colon.
Step 8: Try command below to insert current working directory at the beginning of the string value stored in PATH variable. $PATH=.:$PATH
Step 9: Execute simple.sh again by trying following command. $simple.sh
$ simple.sh
Question 8) : Can you find errors prompted in step 9 ? If not, please briefly describe why there is no need to put ./ before the file name.
Step 10: Log out the connection to the snowball server and reconnect to it. Or simply close your terminal and then reopen your terminal.
Step 11: Print out the value stored in PATH variable again.
Question 9: Can you find the current working directory . in the PATH variable?
Step 11: Execute simple.sh again by trying following command. $simple.sh
$ simple.sh
Question 10) : Can you find errors prompted in step 11 ? If yes, please explain why?
Part 3 - Optional:
This part is optional, but you will find more questions about this part in your next lab.
Step 1:
Create a new file named as checkError.sh (vi checkError.sh or nano checkError.sh), then include following lines in your checkError.sh.
$#/bin/bash
/* Check Error Script */ echo "Try to find out some errors!!!"
# Seach for the words which can be matched by regex [^a]*ce
# And save the output to file "Result"
echo "The regex [^a]*ce can match the string(s):" > Result grep '^[^a]*ce$' << END >> Result lance ace brace decide piece -ENDHERE
# Check the existence of file "Result"
# Send the content in "Result" to your emailbox
# $1 is replaced by your campusID ls mail $1 < Result
# $1 is replaced by your campusID echo "The result has been sent to 1@student.gsu.edu" echo "Congratulations! You have corrected all the errors!"
Or you can directly copy this file from my public directory to your current working directory by following command and then skip step 2.
$cp /home/yye10/public/checkError.sh checkError.sh
Step 2: Save your file and exit editor.
Step 3: Try following command to make checkError.sh executable. $chmod a+x checkError.sh
Step 4: Execute this file by following command.
$./checkError.sh campusID
Note: Replace campusID with your own campus ID.
E.g. $./checkError.sh ylong4
Questions:
Can you find some errors when executing the command in step 4? If yes, please point out which lines contain errors. Think about the correction in your next lab. Before the correction, you could pre-view the slides #15 - #24 in Chapter 4.
Hints:
• Following is a sample of the output once all the errors are corrected
$ ./checkError.sh ylong4 Try to find out some errors!!! checkError.sh Result
The result has been sent to ylong4@student.gsu.edu Congratulations! You have corrected all the errors!
• You can use cat -n checkError.sh to check line numbers.