Within my ksh script I am executing the following:

if [ -f *.pnr.* ]
then
.....
fi

if there exists one and only one file that satisifies this condition, the script runs successfully.

if there exists more than one file that satisifies this condition, I receive the following message:

./pnr.ksh[190]: [: /home/pnr/2004.03.10.1000.pnr.ready: unexpected operator/operand

The files that exist in the sub-directory include:

/home/pnr/2004.03.10.1000.pnr.file1
/home/pnr/2004.03.10.1000.pnr.ready

This script works on a solaris box but I'm not sure why it does not work on linux.

Any help is appreciated.

Thanks.

hmm. remember it's usually pdksh on linux rather than the full blown one.
perhaps the 'test' is a bit different on linux.

do:

so we can see what the test is evaluating.



billy

I've the same problem under Suse Linux Enterprise Server 8 for a script which works on sun.

> echo "*.env"
*.env
> if [ -f *.env ]
2> then
2> echo ja
2> fi
ksh: [: APPSORA.env: unexpected operator/operand

By the way the filename APPSORA.env one file matching to the pattern *.env.

What is wrong with that code which run under sun solaris?

Werner

weird.
Yes it worked on solaris.

???
try quotes around "*.env" ?

> if [ -f "*.env" ]
2> then
2> echo yes
2> else
2> echo no
2> fi
no

I tried with quotes. Then it echos "no" even though there exists file in the directory.

Werner

For my actual migrated code I quit using test operator with wildcards (unless someone has an idea or explanation). I use the workaround:

if (ls *.env >/dev/null)
then
..
fi

Werner