Re: bash - bad interpreter: no such file og catalog

[Djm]

fm@sophia.inria.fr (Francis Montagnac) wrote in message 
news:<aiouj3$eg7$1@news-sop.inria.fr>...
> In article <c982dbde.0208060809.5ad08670@posting.google.com>,
>  dmuren@start.no (Djm) writes:
> ..
> >I get a syntax error when running /bin/bash ./ok.
> >: No such file or catalog
> >/ok: Checking: command not found
>    ^^^^^^^^
> >#!/bin/bash
> >/*
> >Checking cached mail
>  ^^^^^^^^
> You are using the C syntax for comments. This is not what bash
> expects: use instead # to comment till end of line.
> 
> -- 
> Francis.Montagnac@sophia.inria.fr, Tel: (33) 04 92 38 79 11, Bur: E106
> INRIA Sophia, 2004, rte des Lucioles, B.P.93 - 06902 Sophia Antipolis Cedex
> 
> PS: 
> 
>    if test x"$1" = x
> 
> could be written:
> 
>    if [ "$1" ]


If I am to use the "if [ "$1" ]" mentioned above, what will I have to
do where "test" appears other places in the script??
What does "test -f" mean? 
I have changed the comment signs to # and now the script is listing
out my pending_messages, but I get an ;
./ok: line 21: syntax error near unexpected token `elif'
'/ok: line 21: `        elif  test -f
$HOME/procmail/pending_messages/$1

Do you know why?

Djm