Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

So I've written my first bash script:

#!/bin/bash
echo 'hello world!'
exit

I know it has the right location to bash and is executable:

$ which bash
/bin/bash
$ chmod +x myscript.sh

Now I want to run it from the command line, but I get an error:

$ myscript.sh
myscript.sh: command not found

So instead I try this and it works:

$ bash myscript.sh
hello world!

Is this how I will always need to execute it? I feel like I have executed other scripts without having to precede it with bash. How can I run myscript.sh without having to precede it with bash?

Update: Here is a good explanation of why and how to execute a bash script.

share|improve this question
add comment

2 Answers 2

up vote 25 down vote accepted

You have to make the file executable. You can do that with

chmod +x <filename>

where is the name of your script and then you have to prepend it with ./ to instruct the shell to run a file in the local directory, like:

./script.sh

You can only run files that are in your PATH or that you specify a path to them. ./, the local directory, is not in the PATH by default because someone may use it for nefarious purposes. Imagine a script called ls dropped in a directory, you go inside that directory, run ls and that script does something bad.

While you are at it you may want to make it more portable by running shell instead of bash by using:

#!/bin/sh

or by running bash no matter where it is installed as long as it is installed:

#!/usr/bin/env bash
share|improve this answer
    
I have already done that with chmod +x myscript.sh. Did I do it wrong? –  Andrew Dec 12 '09 at 19:28
    
You are probably missing ./ I've added it to the answer. –  Pablo Dec 12 '09 at 19:30
    
Makes sense. And it works. Thanks! –  Andrew Dec 12 '09 at 19:34
add comment

In addition to the advice by Fernández, precede it with a point, like this:

./myscript.sh

For security reasons the current directory is never included in the execution path.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.