Unix Path Variable - Exercise

script names and PATH variable

Objective:Observe how the value of PATH affects which command is run

Exercise Scoring:

This exercise is autograded and worth 2 points.

Instructions

In this exercise you will use script names that will cause problems when creating your own scripts. This will show you what happens when you do this, so that you will not do it in the future. You will log into your shell account, create a script, give the script various names, and run it.

1) log into your UNIX account.

Create a sample script by performing the following actions.
Create a file called ls. This will be your script.

vi ls

Your script should look like the code below. Type in this script using vi.

#! /bin/sh
echo "This is my ls script"

Change permissions[[the chmod command]] on your script so that you can run it
Do people know that command yet? If not, I think we should briefly explain how/why it is being used?
This is a basics of UNIX command. I will insert a sidebar here to clarify this one command.

chmod +x ls

Try running your script.

ls

Do you see the problem here? The shell locates the regular ls command in your PATH before it looks in your current directory to find your script. Your script is not run.

Rename the script and
```
Rename itanything you want?
```
it again.

mv ls myscript
myscript

It should run with no problems.

Another problem you may encounter is that your PATH variable does not contain the current directory (the . directory). Let’s try changing PATH to see the problem this can cause.

a) Change the PATH variable to include only the /usr/bin directory, then try running your script.

<pre>[[delete break]]

PATH=/usr/bin[[delete break]]

myscript<pre>

Unix Path Variable - Exercise

script names and PATH variable

Exercise Scoring:

Instructions

Submitting your exercise