Home » Blogs » sandip's blog

Check for number of arguments in bash

Wed, 01/17/2007 - 11:49 — sandip

# Check for proper number of command line args.

EXPECTED_ARGS=1
E_BADARGS=65

if [ $# -ne $EXPECTED_ARGS ]
then
  echo "Usage: `basename $0` {arg}"
  exit $E_BADARGS
fi

Bookmark/Search this post with
  • del.icio.us
  • Digg
  • Facebook
  • identi.ca
  • LinkedIn
  • SlashDot
  • StumbleUpon
  • Technorati
  • Twitter

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Tue, 10/02/2007 - 16:36 — sandip bash args

An easier way would be via parameter substitution:

: ${1?"Usage: $0 ARGUMENT"}

If parameter set, use it, else print error message.

Thu, 07/26/2012 - 11:08 — Anonymous False?

Wouldn't that cause problems if the arguments passed were 0 and/or "" ?

Tue, 09/25/2007 - 18:57 — James Valentine (not verified) Your check for expected Bash script Args

Sandip,

your check doesn't seem to allow a * wildcard to pass the check as an argument - it simply seems not to be counted. Why is that? My script must be able to accept this.

Any ideas, or a possible fix?

Cheers,
J.

Wed, 09/26/2007 - 15:10 — sandip bash globbing

That is due to bash globbing.

Try prefixing the * with \ like \* or,

`set -f` to disable globbing and then run the script.

Comment