On Tue, Nov 24, 2009, Lachele Foley wrote:
>
> So, invoking "csh -f" on my system causes /bin/rm to behave unexpectedly
> (plain csh works as expected).
This is indeed odd, but some similar-sounding problems have been reported
before. What does "/bin/csh --version" report?
There are lots of test cases that begin with "#!/bin/csh -f" and later contain
a "/bin/rm -f ..." command. Maybe it has something to do with shell
globbing(?). [Most other /bin/rm commands don't use shell wild-cards.]
Your report is a little incomplete: what is the "trouble" that is caused
in the Run.tleap script? Also, what you show about the behavior of csh vs.
csh -f looks like what I would expect -- am I missing something there?
...thx...dave
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Wed Nov 25 2009 - 09:30:03 PST
