| You might have got your terminology backwards.
The server is the thing with the display (the VAXstation hardware).
A client is any application program.
If this sounds backwards, consider that it's really the same
way round as "terminal server" !
--
OK, with that straightened out:
(1) Limiting access to servers (i.e. to VAXstations)
No problem. Each server has to have a list of node::user
pairs for permitted clients. If you're not authorized, you
can't create windows on that server.
The authorization is set up by a customization mechanism
under the session manager (thus it is specific to the logged-on
user, if you happen to share one VAXstation between several
people).
(2) Limiting the number of processes on the client machine.
Since you essentially have to log in a process on the client
in order to run an application, this is subject to the normal
resource usage rules on the client machine.
|
| Thank you for the explanation but, I understand the terminology.
That was probably unclear from my base note. I'll put the question(s) another
way.
1) In a cluster with a common authorization file, what's to prevent me from
creating a process on your station (set host, detached process, batch, etc...)
and doing something like the following:
$ SET DISPLAY/CREATE/NODE=MYNODE
$ RUN SYS$SYSTEM:DECW$MAIL
This would utilize your workstation as a CLIENT and send all output to
MYNODE (as long as I had authorized it). For batch this could be prevented
by ACL's of setting ownership on batch queue's but, that doesn't address the
set host or the detached method. What I'm looking for is a way to tell the
users that such and such nodes are the clients that you can utilize and I
also want to be able to enforce it.
2) I need a way to allocate X number of processes per user on a given CLIENT
and not allow them to start more.
Thanks,
Dave H.
|