Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mandrill!gatech!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!iuvax!bsu-cs!cfchiesa
From: cfchiesa@bsu-cs.UUCP (Christopher Chiesa)
Newsgroups: comp.os.vms
Subject: Re: What resources does an idle process tie up ... or why have
Summary: Shutdown to install new stuff
Message-ID: <3199@bsu-cs.UUCP>
Date: 28 May 88 20:19:31 GMT
References: <8805270320.AA07440@ucbvax.Berkeley.EDU>
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 34

In article <8805270320.AA07440@ucbvax.Berkeley.EDU>, WHEELER@CC.UTAH.EDU writes:
> Posting-Version: unknown; site unknown
> Subject: What resources does an idle process tie up ... or why have
> 
> Here are a few reasons that I know of for having an idle process killer.
> (Please note, none of the system's I'm in charge of use an idle process
> killer)
> 
> [you've seen the list, so I'm omitting it]

> By the way, does anyone *really* make all the user's log off and shutdown
> the network to install new products?
> 
> Bob Wheeler
> bob%howard@cc.utah.edu

Here at Ball State University, the entire four-node Vaxcluster is completely
shut down from 5PM Friday night til 8AM Saturday morning for backups, main-
tenance, and who knows what else (I've been a student so I don't know the inner
arcane details).  Software installation is done either at THAT time, or in an
even MORE extended shutdown (this whole holiday weekend, for example) during
inter-quarter Breaks...

Of course, this is a HUGE system (comments on this next quote are solicited):
our system manager quotes a figure of about 25,000 users...  (Not all at the
same time, of course, but that's about right, in terms of the number of 
accounts living on the system, by my own experience.)

Chris Chiesa
 Ball State University

-- 
UUCP: <backbones>!{iuvax,pur-ee,uunet}!bsu-cs!cfchiesa 
cfchiesa@bsu-cs.UUCP