Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!ginosko!usc!bbn!bbn.com!jr From: jr@bbn.com (John Robinson) Newsgroups: gnu.emacs.bug Subject: Re^2: Lock files Message-ID: <45625@bbn.COM> Date: 15 Sep 89 03:01:33 GMT References: <922@mipos3.intel.com> Sender: news@bbn.COM Lines: 25 pinkas@cadev5.intel.com (Israel Pinkas ~) writes: >> How about prepending the hostname to the lock filename, so that locks >> created in an NFS'ed, shared lock directory are unique across machines. >Most sites mount partitions so that they have the same name on all the >partitions. For example, my home directory is /usr/users/ccad/edend/pinkas >on all machines that mount it. >Besides, I have run into a few problems with NFS shared lock directories >due to the write buffering. I have always believed the best solution is to write the lock file right into the directory of the file you are locking. This avoids failing to lock when things are mounted funny (we always have an odd mount point like /mnt hanging around) or missing locks due to different symbolic link paths. The other problem we had here is that /usr/local/emacs/lock gets royally pounded when a lot of diskless wortstations share a server for emacs. I set lockdir to /tmp. The lockfile names are strange enough that they oughtn't cause trouble from collisions. /jr, nee John Robinson Life did not take over the globe by combat, jr@bbn.com or bbn!jr but by networking -- Lynn Margulis