John Carter wrote:

> The problem arises on the IF ststement.  The error is too many
> parameters.  It looks like the "-a" is something I have never seen in
> an IF statement and I can find no reference to it anywhere.

the open square bracket is usually

/usr/bin/[

which might be a hard or soft link to /usr/bin/test

> if [ ${GOV} = "ondemand" -a ${FORCE} = "1" ]

so that line expands to

if /usr/bin/test ${GOV} = "ondemand" -a ${FORCE} = "1"

the -a relates to the "test" command, not to the "if" statement.

the -a argmument to "test" can be used either to test for existence of a
file, or as in this case as a boolean "and" clause

I suspect your issue is that one of your bash variables is unset, or has
ended up with a special character in it, put echo ${GOV} and echo
${FORCE} statements in there for debugging ...

--- SoupGate-Win32 v1.05