Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!cmcl2!beta!unm-la!unmvax!hi!hc!ames!ucbcad!ucbvax!CAEN.ENGIN.UMICH.EDU!donp
From: donp@CAEN.ENGIN.UMICH.EDU (Don Peacock)
Newsgroups: comp.sys.apollo
Subject: remote processes
Message-ID: <8707011949.AA00653@caen.engin.umich.edu>
Date: Wed, 1-Jul-87 15:49:31 EDT
Article-I.D.: caen.8707011949.AA00653
Posted: Wed Jul  1 15:49:31 1987
Date-Received: Fri, 3-Jul-87 04:18:08 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 5

We are trying to keep our users from CRPing onto our fileservers
yet retain the ability to CRP onto them ourselves (as root).
Has anyone found a way to "ACL out" the CRP command for certain users
or some other effective way of selectively keeping users from
creating processes on critical nodes?