2
The ATLAS install process is heavily file-based, and this can cause major
3
reliability problems when interacting with an overloaded or malfunctioning
4
remotely mounted filesystem. ATLAS therefore has a mechanism in place to
5
allow for a delay before a file is declared to not be there, so that
6
slow NFS (i.e., waiting for amd timout) problems can be overcome, or for
7
handling slightly differing clocks between server/client. This problem is
8
magnified if doing cross-compilation. In the question below, we ask how
9
much of a delay, in seconds, ATLAS should tolerate between file creation
10
and appearance. If you are installing on a local filesystem (eg. /tmp) or
11
a smooth-running NFS system, answer 0; for a moderately loaded NFS server, you
12
may want a value in the 10 second range, and for cross-compiling systems or
13
NFS servers experiencing errors, you may want to go as high as a couple