🚀 go-pugleaf

emacs 19.25
SunOS 4.1 & Solaris 2.3 on SPARC stations
configure --prefix=/dme/software/gnu/solaris --with-x-toolkit

We have started making use of the file interlocking feature on emacs.
I have noticed that when the lock file is checked, emacs checks that
the process with the pid given in the lock file is running on that
machine.  This obviously falls down when we have a number of machines
accessing the same file over NFS.  I have temporarily worked around
this problem by changing src/filelock.c as follows:

jaws@hades(2335)$ diff filelock.c filelock.c.old
302,304c302
< /* jaws:19/9/94 Fixed so that this works across the network */
< /*  if (owner != 0 && (kill (owner, 0) >= 0 || errno == EPERM))*/
<   if (owner != 0)
---
>   if (owner != 0 && (kill (owner, 0) >= 0 || errno == EPERM))


This obviously posses the problem that old lock files lying around will
continue to lock the file.  But as emacs allows locks to be stolen with
relative ease this appears to be the lesser of two evils for our
particular system.

If this is not your preffered default behaviour, maybe it could be
offered as an installation option.

thanks
James