nate@hobbes.intel.com (Nate Hess) (09/14/89)
Here is a suggestion for the lock files that Emacs creates:
How about prepending the hostname to the lock filename, so that locks
created in an NFS'ed, shared lock directory are unique across machines.
--woodstock
--
"What I like is when you're looking and thinking and looking
and thinking...and suddenly you wake up." - Hobbes
woodstock@hobbes.intel.com ...!{decwrl|hplabs!oliveb}!intelca!mipos3!nate pinkas@cadev5.intel.com (Israel Pinkas ~) (09/15/89)
In article <922@mipos3.intel.com> nate@hobbes.intel.com (Nate Hess) 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. I don't like this. I would rather have to break bogus locks for machine specific files (e.g /etc/motd) than have two people edit an NFS mounted file simultaneously (e.g. ~/.login). 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. If we implement what Nate suggests, two people could edit my .plan file without realizing it. On the other hand, Nate's suggestion will eliminate the bogus message about breaking a lock when two people attempt to modify /etc/motd on two machines that share a lock directory. Besides, I have run into a few problems with NFS shared lock directories due to the write buffering. -Israel -- -------------------------------------- Disclaimer: The above are my personal opinions, and in no way represent the opinions of Intel Corporation. In no way should the above be taken to be a statement of Intel. UUCP: {amdcad,decwrl,hplabs,oliveb,pur-ee,qantel}!intelca!mipos3!cadev4!pinkas ARPA: pinkas%cadev4.intel.com@relay.cs.net CSNET: pinkas@cadev4.intel.com