comparison etc/PROBLEMS @ 36450:a5ae1f49b2ee

Document the problems with "Text file busy" due to buggy NFS servers.
author Eli Zaretskii <eliz@gnu.org>
date Thu, 01 Mar 2001 13:50:51 +0000
parents db153cee8704
children 0c82cdff9120
comparison
equal deleted inserted replaced
36449:76e6a6858e55 36450:a5ae1f49b2ee
183 find the jpeg library. 183 find the jpeg library.
184 184
185 (If you need the static version of the jpeg library as well, you can 185 (If you need the static version of the jpeg library as well, you can
186 configure libjpeg with both `--enable-static' and `--enable-shared' 186 configure libjpeg with both `--enable-static' and `--enable-shared'
187 options. 187 options.
188
189 * Building Emacs over NFS fails with ``Text file busy''.
190
191 This was reported to happen when building Emacs on RedHat GNU/Linux
192 using a build directory automounted from Solaris (v5.6) file server,
193 but it might not be limited to that configuration alone. Presumably,
194 the NFS server doesn't commit the files' data to disk quickly enough,
195 and the Emacs executable file is left ``busy'' for several seconds
196 after Emacs has finished dumping itself. This causes the subsequent
197 commands which invoke the dumped Emacs excutable to fail with the
198 above message.
199
200 If the NFS server runs on Solaris, apply the Solaris patch 105379-05
201 (Sunos 5.6: /kernel/misc/nfssrv patch). If that doesn't work, or if
202 you have a different version of the OS or the NFS server, you can
203 force the NFS server to use 1KB blocks, which was reported to fix the
204 problem albeit at a price of slowing down file I/O. You can force 1KB
205 blocks by specifying the "-o rsize=1024,wsize=1024" options to the
206 `mount' command, or by adding ",rsize=1024,wsize=1024" to the mount
207 options in the appropriate system configuration file, such as
208 `/etc/auto.home'.
209
210 Alternatively, when "make install" fails due to this problem, you
211 could wait for a few seconds and then type "make install" again. In
212 one particular case, waiting for 10 or more seconds seemed to work
213 around the problem.
188 214
189 * Some accented ISO-8859-1 characters or umlauts are displayed as | or _. 215 * Some accented ISO-8859-1 characters or umlauts are displayed as | or _.
190 216
191 Try other font set sizes (S-mouse-1). If the problem persists with 217 Try other font set sizes (S-mouse-1). If the problem persists with
192 other sizes as well, your text is corrupted, probably through software 218 other sizes as well, your text is corrupted, probably through software