Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!alberta!auvax!rwa
From: rwa@auvax.UUCP (Ross Alexander)
Newsgroups: news.admin
Subject: Re: Forgeries: a suggestion for bringing them under control
Summary: rogue _can_ be bad for the system...
Message-ID: <512@auvax.UUCP>
Date: 2 Feb 88 02:56:47 GMT
References: <1861@epimass.EPI.COM> <14276@oddjob.UChicago.EDU> <1129@hao.ucar.edu> <784@brandx.rutgers.edu>
Organization: Athabasca U., Alberta, Canada
Lines: 18

In article <784@brandx.rutgers.edu>, webber@brandx.rutgers.edu (Webber) writes:
> However, if the playing of rogue were
> crashing the system, then it would clearly be something worth careful 
> investigation.

The playing of rogue, at least around here during 12pm to 4pm, is considered
antisocial.  Rogue is a cycles-and-communications hog.  I shoot rogue players
on sight, and make no apologies for it.  I also bump idle users and blow away
runaway processes.  What's the difference between a machine with a 20+ load
average and a crashed machine?  Precious little, if that machine is a VAX 780.

Of course, rogue at 2000 hours is a different thing entirely.

Ross Alexander,
Sr Systems Programmer
Athabasca University, Alberta

alberta!auvax!rwa