Path: utzoo!mnetor!uunet!husc6!hao!ames!pasteur!ucbvax!decvax!decwrl!pyramid!prls!philabs!ttidca!mb
From: mb@ttidca.TTI.COM (Michael Bloom)
Newsgroups: comp.emacs
Subject: Re: GnuEmacs 18.41 on Sun - Server question
Message-ID: <1738@ttidca.TTI.COM>
Date: 24 Jan 88 14:26:14 GMT
References: <309@surf.atexrd.UUCP>
Reply-To: mb@ttidca.tti.com (Michael Bloom)
Distribution: na
Organization: Citicorp/TTI, Santa Monica
Lines: 24
Keywords: server sun

In article <309@surf.atexrd.UUCP> jdw@atexrd.UUCP (John Williams) writes:

>Any suggestions as to how to let root (or anyone else) access the server on a
>workstation? 
>
>Thanks

Sure. Using adb on /vmunix, change the value of the variable "nobody"
from -2 to 0.  This may be unsafe if your site is subject to "root
wars" however.  We changed it in the code, but run an adb script to do
this from rc anyway, just in case someone boots a system built with
an earlier nfs_server.c delta. Something to watch out for here is that
between revisions, "nobody" changed from int to uid_t (short). 

A more serious problem is that if you run emacs on more than one
machine, you will have problems with emacs on one machine screwing up
the socket created by emacs on another machine.

I solved this at my site by renaming .emacs_server to
.emacs_server.<HOSTNAME> in the code.

Even better would be to rewrite the server code to use internet domain
sockets for the communication, so that emacsclient on one machine
could interact with a server on another.