Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!samsung!munnari.oz.au!sirius.ucs.adelaide.edu.au!fang!itd0!agq
From: agq@itd0.dsto.oz (Ashley Quick)
Newsgroups: comp.sys.apollo
Subject: create remote process
Message-ID: <1147@fang.dsto.oz>
Date: 3 Aug 90 19:30:04 GMT
Sender: news@fang.dsto.oz
Reply-To: agq@dstos3.dsto.oz (Ashleigh Quick)
Organization: Defence Science and Technology Organisation
Lines: 35
Summary:
Expires:
Sender:
Followup-To:
Distribution:
Keywords:

A week or two ago, I posted an item about problems creating remote
(shell) processes on other nodes.

The problem:

on node A, try to create process on B:
   crp -on B -me

which would fail with an error similar to
  "cannot create rmeote process - no rights to server mailbox"
(I cannot remember the exact message but this is the gist of it)



The solution:

check in your /dev directory, and see what the crp devices look like.
In our case they were all sorts of different sizes.

Get your system administrator to re-create the crp devices with:
  mkdev /dev crp

And you will then be able to remote log in.

(Interesting note: when created, the crp devices have a type of 'mbx'.
After they have been used by a remote login, the type changes to 'spmio'.
Curious eh?)

The configuration is a DN4500 running SR10.1, though the same problem
has been seen on a diskless DN3500, also running SR10.1. This may not
be a problem under later SR's.... but what causes the devices to get
screwed up in the first place?

Ashleigh Quick
AGQ@dstos3.dsto.oz.au