Path: utzoo!mnetor!uunet!husc6!uwvax!oddjob!ncar!ames!hc!beta!unm-la!unmvax!turing.UNM.EDU!mike
From: mike@turing.UNM.EDU (Michael I. Bushnell)
Newsgroups: comp.emacs
Subject: Re: Changing major mode in server mode
Message-ID: <894@unmvax.unm.edu>
Date: 21 Mar 88 21:05:01 GMT
References: <480@sol.warwick.ac.uk> <1894@mipos3.intel.com>
Sender: news@unmvax.unm.edu
Reply-To: mike@turing.UNM.EDU.UUCP (Michael I. Bushnell)
Organization: University of New Mexico, Albuquerque
Lines: 29

In article <1894@mipos3.intel.com> pinkas@cadev4.UUCP (Israel Pinkas ~) writes:

>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.
>In our environment, we have a large number of workstations mounting
>directories from a large VAX.  Almost all the users home directories are
>mounted in this way.  This means that ~/.emacs_server is not feasible to
>use unless emacs happens to be running on the file server, shich is not
>desirable.

The NFS spec does not dal with special files.  Correct.  But it does
deal with sockets (in a strange way).  Socket != Spec. file.  My
directory is on another machine.  All my processes are on this one,
and everything works fine.

The emacsclient must be started on the same machine as the emacs
itself.  This will also prevent the creation of another .emacs_server
from another client.  The socket is actually created on the server,
but the connect/accept/listen must all occur on the same machine.  But
NOT necessarily the server itself.

The "solution" is thus not necessary.
			Michael I. Bushnell
			HASA - "A" division
14308 Skyline Rd NE				Computer Science Dept.
Albuquerque, NM  87123		OR		Farris Engineering Ctr.
	OR					University of New Mexico
mike@turing.unm.edu				Albuquerque, NM  87131
{ucbvax,gatech}!unmvax!turing.unm.edu!mike