The error message is coming from inside the script and it is, because where the script is there is no such file as "*.cell". Note that "*.cell" is meaning all the files in the current directory with a name ending in ".cell". But what "current directory" means depends on where you were when you started the script.

This is why you should always use absolute paths (paths starting from the root dir) in scripts. For instance:

Code:

#! /bin/bash
typeset WorkPath="/path/to/some/dir"
typeset File1="${WorkPath}/filename.ext"

echo "WorkPath is: $WorkPath"
echo "Filename is: $File1"

# now, notice the usage of the variable holding the path and the other
# variable holding the filename:
cp /etc/hosts "$WorkPath"
mv "$WorkPath/ls" "$File1"

# here we do something with the file. What we do doesn't matter, just to
# show the principle
wc -c "$File1" > "$File1".tmp
mv "$File1.tmp" "$File1"

exit 0

Notice, that the full path is only named once, then used throughout the script. Think about what content each of the variables holds at which time and what the complete commands with expanded variables would look like. I suggest you adapt the script a bit and play around with it.

Having said this, you cycle through all directories and call the script for each directory once, but the directories you cycle through are nowhere mentioned in your script. You probably should do something with the directory names you cycle through, otherwise there is no sense in doing this, no?

What you do is:

Code:

./dir1: script
./dir2: script
./dir2/dir1: script
./dir2/dir2: script
...

What you probably want to do is something like:

Code:

./dir1: script ./dir1
./dir2: script ./dir2
./dir2/dir1: script ./dir2/dir1
./dir2/dir2: script ./dir2/dir2
...

Supposing that the script can do something with the directory name it gets passed. To understand how to do something with passed parameters you should read the man page of your shell (mind you, "bash" or "ksh", but DEFINITELY NOT csh! Do not even consider to use csh for scripts, the damned thing is buggy to no end!).

Here is a short introduction:

Code:

#! /bin/bash
# demonstration script for parameters
typeset localvar=""

echo "my first passed parameter is: $1"

# using variables to take parameters:
localvar="$1"

echo "you see, localvar now holds the same value: $
localvar"

exit 0

save this to a file "myparam.sh", slap on the executable-bit and issue:

Code:

./myparam.sh abc
./myparam.sh abc def
./myparam.sh "abc def"
./myparam.sh ./path/to/some/file

You might want to change your script accordingly.

I hope this helps.

bakunin