Path: utzoo!utgpu!water!watmath!clyde!att-cb!att-ih!pacbell!ames!mailrus!umix!uunet!mcvax!ukc!warwick!cudcv From: cudcv@daisy.warwick.ac.uk (Rob McMahon) Newsgroups: comp.emacs Subject: Re: Changing major mode in server mode Message-ID: <510@sol.warwick.ac.uk> Date: 3 Apr 88 08:11:45 GMT References: <480@sol.warwick.ac.uk> <1894@mipos3.intel.com> Reply-To: cudcv@cu.warwick.ac.uk (Rob McMahon) Organization: Computing Services, Warwick University, UK Lines: 35 I did try to reply to this, but the mailer was having none of it ... In article <1894@mipos3.intel.com> pinkas@cadev4.UUCP (Israel Pinkas ~) writes: |[Re: problems with having the same socket name on multiple machines |when in and NFS environment] |I changed the name of the server file ... to /tmp/.emacs_server_, Thanks for the patches, but: |The NFS spec does not provide for special files to be accessed across NFS. |Thus, creating, reading, and writing a socket are not possible over NFS. |... |My reasoning [for moving the socket to /tmp] is that the /tmp directory |should be local. (... X10 puts a socket file in /tmp. I figured that |if /tmp is not local, we have bigger problems than emacs servers not |running.) Diskless nodes should be OK as they do not mount / via NFS. |(This is not tested, though.) I'm confused. I sit here now on my diskless machine using emacsclient, emacs version 18.50, with no patches, and with the socket in my home directory, NFS mounted. All works fine. Maybe Sun have changed the NFS spec since the VAX version ? After all, I can't think of any good reason for it to fail, all it wants from the socket is it's mode and filehandle. Rob -- UUCP: ...!mcvax!ukc!warwick!cudcv PHONE: +44 203 523037 JANET: cudcv@uk.ac.warwick.cu ARPA: cudcv@cu.warwick.ac.uk Rob McMahon, Computing Services, Warwick University, Coventry CV4 7AL, England -- UUCP: ...!mcvax!ukc!warwick!cudcv PHONE: +44 203 523037 JANET: cudcv@uk.ac.warwick.cu ARPA: cudcv@cu.warwick.ac.uk Rob McMahon, Computing Services, Warwick University, Coventry CV4 7AL, England