Path: utzoo!attcan!uunet!cs.utexas.edu!sdd.hp.com!mips!dimacs.rutgers.edu!rutgers!mit-eddie!bloom-beacon!eru!hagbard!sunic!mcsun!hp4nl!nikhefh!a89
From: a89@nikhefh.nikhef.nl (Gerard Leurs)
Newsgroups: comp.sys.apollo
Subject: problems with apollo's running mentor software
Summary: authorization problem / negative null proces
Message-ID: <1011@nikhefh.nikhef.nl>
Date: 5 Oct 90 12:42:30 GMT
Sender: G.Leurs@nikhef.nl (Gerard Leurs)
Reply-To: a89@nikhefh.nikhef.nl (Gerard Leurs)
Organization: Nikhef-H, Amsterdam (the Netherlands).
Lines: 39


I have 2 questions to all you netlanders :

question 1:
We are running mentor software on 8 machines in our apollo domain.
Occasionally there are problems with the authorization to run the
different programs (Neted, Symed etc.) of this mentor software.

Once in a while we get (on an authorized node) a message something
like "?Authorization problem: you are not authorized to run this
software on this node".
There can be no problem with expiration of our codes, because the
problem only appears on 1 of the 8 nodes (and not on all 8). And
there is also a "random pick" of this problem-node out of the 8.

What is going on here ?
How can it be prevented ?

Our "solution" is to shutdown and reboot the node.
After doing this everything works fine ! This is however not a
very nice way to solve the authorization problem.

question 2:
Sometimes a so-called "boardstation" becomes very slow / unpleasant
to work with. When using "/com/dspst" one gets a negative Null-
proces! All servers are OK on these nodes (at least they look like
they are).

What is going on ?
What can be done to solve this problem ?

For what it is worth: we are running SR10.2, with (BSD)-UNIX
as our environment. The mentor software is version 7.x.


Please email me directly for comments / suggestions :
G.Leurs@nikhef.nl (or a89@nikhapo.nikhef.nl).

Thanks.