Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!amdcad!neptune!markl
From: markl@neptune.AMD.COM (Mark Luedtke)
Newsgroups: comp.sys.apollo
Subject: Re: some questions for the gurus.
Message-ID: <675@neptune.AMD.COM>
Date: 14 Sep 88 21:29:46 GMT
References: <8809081356.AA00196@caen.engin.umich.edu> <3e720dde.13422@apollo.COM>
Reply-To: markl@neptune.AMD.COM (Mark Luedtke)
Organization: Advanced Micro Devices, Inc., Austin, Texas
Lines: 15

I, for one, would (or will) not like to have to switch users to sigp someone's
remote process on my node.  In my environment noone generally crp's on a node
without knowing in advance that it will not be a problem or expressing that,
do to limited copies of software, it is a necessity.  However there have been
a few times where this has occured, and I see no reason to have to go through
contortions to kill this process.  (I REALLY wish that I could suspend such
processes, but I don't know any way to do this.  Does anyone else?)  Needless
to say, not everyone on our ring has a root id and those without have no way
to deal with this problem, especially if he is editing/etc and modifying 
priorities has no noticible effect.  Hopefully this is an optional feature
because it could cause the loss of a lot of work in my area.

Mark Luedtke  markl@neptune.amd.com

Note that these comments are only mine and do not necessarily reflect those of
AMD.