Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!ogicse!milton!mattf
From: mattf@cac.washington.edu (Matthew Freedman)
Newsgroups: comp.windows.x
Subject: Re: Help with MacX/Ultrix
Message-ID: <13902@milton.u.washington.edu>
Date: 7 Jan 91 22:01:27 GMT
References: <926@vtserf.cc.vt.edu> <11649@goofy.Apple.COM>
Sender: news@milton.u.washington.edu
Reply-To: mattf@cac.washington.edu (Matthew Freedman)
Organization: University of Washington, Seattle
Lines: 19

>[1] If you have Ultrix 4.0 you likely are experiencing a problem in which
>Ultrix "rexecd" daemon simply does not work.  MacX uses the "rexec"
>protocol to start remote commands.  DEC is aware of this and recommends
>you use "/etc/rexecd" from another Ultrix release as a workaround.

Under Ultrix 4.0 MacX's rexec will work only if you log into the
ultrix machine as root.  I believe they fixed rexecd in Ultrix 4.1,
or any of the pre-4.0 versions should work too.

Under multifinder you can also log into the ultrix machine with a
regular NCSA telnet window, and then start off your first xterm with the
display pointed to your MacX screen.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
= Matthew M. Freedman                                                 =
= U. of Washington Information Systems       mattf@cac.washington.edu =
= 4545 15th Ave. NE; 4th Floor               (206) 543-5593           =
= Seattle, WA  98105                                                  =
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-