On Mon, Mar 31, 2008, Lachele Foley wrote:
>
> We put our common-area executables in a directory that is not writable by
> the compute nodes. This is important to us since we're likely to have
> homemade programs running about, and wish to minimize unintended overwrites.
> So... while $AMBERHOME is visible to all the nodes, any test that requires a
> node writing to $AMBERHOME/anything will fail for us, and the diff will be
> against an empty file. Programs that merely send output to the scheduler
> will work.
Why not just make a link between your (local) AMBERHOME/exe and the
common-area executables directory? Then you could write to $AMBERHOME, yet
still run jobs from the common area.
Just a thought...might not work. But the tests are run in the amber10/test
tree, and it's not easy to imagine how this can very easily be made into a
read-only location.
...dac
Received on Fri Apr 18 2008 - 21:15:44 PDT
