Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!dogie.macc.wisc.edu!uwvax!ub.d.umn.edu!cs.umn.edu!poincare.geom.umn.edu!slevy
From: slevy@poincare.geom.umn.edu (Stuart Levy)
Newsgroups: comp.sys.sgi
Subject: Re: one graphics terminal/many users
Message-ID: <1990Dec14.191848.26471@cs.umn.edu>
Date: 14 Dec 90 19:18:48 GMT
References: <18668@hydra.gatech.EDU>
Sender: news@cs.umn.edu (News administrator)
Organization: Geometry Group, University of Minnesota
Lines: 20
Nntp-Posting-Host: poincare.geom.umn.edu

In article <18668@hydra.gatech.EDU> gt3930c@prism.gatech.EDU (ZUCCOLA) writes:
>... Is there anyway to "lockout" other users so that if they accidentally try
> to start something "graphic" and they aren't the person using the machine
>their process won't start?
>
>			Just thought I'd ask,
>			H-----

We have a half-baked way of dealing with this... I hope there's a better one.
We modify our programs to test the $TERM variable.  If it's not "iris-ansi",
the program is probably not being run locally, prints a warning message & quits.
There's a conventional command-line option and environment variable
(-c and "COLLABORATE", both mentioned by the warning message) which defeat the
test -- it's not foolproof, just enough to prevent accidental interference.

Naturally you must either have source to the program or be able to embed it
in a shell script wrapper.  Definitely not ideal.

	Stuart Levy, Geometry Group, University of Minnesota
	slevy@geom.umn.edu