Commit b4da93e1 authored by Eli Zaretskii's avatar Eli Zaretskii
Browse files

Minor wording changes in description of the Solaris NFS problems

resulting in "text file busy".
From Bill Richter <richter@math.northwestern.edu>.
parent 5b83f9c0
......@@ -177,13 +177,13 @@ libjpeg with both `--enable-static' and `--enable-shared' options.)
* Building Emacs over NFS fails with ``Text file busy''.
This was reported to happen when building Emacs on RedHat GNU/Linux
using a build directory automounted from Solaris (v5.6) file server,
but it might not be limited to that configuration alone. Presumably,
the NFS server doesn't commit the files' data to disk quickly enough,
and the Emacs executable file is left ``busy'' for several seconds
after Emacs has finished dumping itself. This causes the subsequent
commands which invoke the dumped Emacs excutable to fail with the
above message.
using a build directory automounted from Solaris (SunOS 5.6) file
server, but it might not be limited to that configuration alone.
Presumably, the NFS server doesn't commit the files' data to disk
quickly enough, and the Emacs executable file is left ``busy'' for
several seconds after Emacs has finished dumping itself. This causes
the subsequent commands which invoke the dumped Emacs excutable to
fail with the above message.
In some of these cases, a time skew between the NFS server and the
machine where Emacs is built is detected and reported by GNU Make
......@@ -200,10 +200,10 @@ blocks by specifying the "-o rsize=1024,wsize=1024" options to the
options in the appropriate system configuration file, such as
`/etc/auto.home'.
Alternatively, when "make install" fails due to this problem, you
could wait for a few seconds and then type "make install" again. In
one particular case, waiting for 10 or more seconds seemed to work
around the problem.
Alternatively, when Make fails due to this problem, you could wait for
a few seconds and then invoke Make again. In one particular case,
waiting for 10 or more seconds between the two Make invocations seemed
to work around the problem.
* Accented ISO-8859-1 characters are displayed as | or _.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment