Re: Error: *: Parameter not set
From: Chris F.A. Johnson (cfajohnson_at_gmail.com)
Date: 06/29/05
- Next message: Chris F.A. Johnson: "Re: Can ksh93 do 0..9 type of syntax for loop control?"
- Previous message: Chris F.A. Johnson: "Re: BASH help please??"
- In reply to: DozyRosy: "Error: *: Parameter not set"
- Next in thread: DozyRosy: "Re: Error: *: Parameter not set"
- Reply: DozyRosy: "Re: Error: *: Parameter not set"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 29 Jun 2005 08:51:10 -0400
On 2005-06-29, DozyRosy wrote:
> I have a shell script which acts as a wrapper to another script and I
> want to propagate all the passed parameters through to the inner script
> (even if there are none). But if I use $* or $@ and there are no
> parameters passed in the I get an error and the script terminates. How
> do I avoid this?
Without seeing your script, it can be no more than a wild guess.
This is probably not the cause of the problem, but you should use
"$@", not $@.
--
Chris F.A. Johnson <http://cfaj.freeshell.org>
==================================================================
Shell Scripting Recipes: A Problem-Solution Approach, 2005, Apress
<http://www.torfree.net/~chris/books/cfaj/ssr.html>
- Next message: Chris F.A. Johnson: "Re: Can ksh93 do 0..9 type of syntax for loop control?"
- Previous message: Chris F.A. Johnson: "Re: BASH help please??"
- In reply to: DozyRosy: "Error: *: Parameter not set"
- Next in thread: DozyRosy: "Re: Error: *: Parameter not set"
- Reply: DozyRosy: "Re: Error: *: Parameter not set"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|