Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!UTHSCSA.BITNET!MOORE
From: MOORE@UTHSCSA.BITNET.UUCP
Newsgroups: mod.computers.vax
Subject: Software installation
Message-ID: <8704100529.AA10793@ucbvax.Berkeley.EDU>
Date: Fri, 10-Apr-87 00:29:55 EST
Article-I.D.: ucbvax.8704100529.AA10793
Posted: Fri Apr 10 00:29:55 1987
Date-Received: Sat, 11-Apr-87 13:16:32 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 26
Approved: info-vax@sri-kl.arpa

Well its me again.  I have another question about policy at different sites.
My last question of this type netted one response, but I will try again.

We have four VAXen in a cluster with 9 RA81s that are dual ported with
two HSC50s.  When we install software on the cluster (eg. new versions of
FORTRAN or Datatrieve) we will disable logins on all four machines, since
anything the installation procedure touches is accessible to all of the
machines.  We don't have any real schedule for software installation.  We
will generally wait until two or three products have arrived so we can get
them all done at once.

Management is complaining that it is absurd to disable all four machines
for the installation of software.  And that at least some of the machines
should be up at all times.  I could take one machine down and install the
software, but...


I would like to establish a software installation policy and put this
one to bed.  You can help me do this.  Please tell me what your software
installation policy is.  A couple of lines will do.  I just want some
ideas.

Mark Moore
The University of Texas
Health Science Center
San Antonio, Texas