Path: utzoo!mnetor!uunet!husc6!hao!ames!ptsfa!ihnp4!homxb!mtuxo!mtune!codas!ufcsv!beach.cis.ufl.edu!jdc From: jdc@beach.cis.ufl.edu (Jeff Capehart) Newsgroups: comp.os.vms Subject: Re: Re: Performance and batch jobs. Message-ID: <9889@ufcsv.cis.ufl.EDU> Date: 22 Dec 87 00:31:35 GMT References: Sender: news@ufcsv.cis.ufl.EDU Reply-To: jdc@beach.cis.ufl.edu (Jeff Capehart) Organization: UF CIS Department Lines: 21 In article WIZARD@RITA.ACS.WASHINGTON.EDU (The Bandit "." "." "." "", on" "RITA) writes: >the user was over his disk quota by quite a lot. Typically, our users >get a scant 750 to 1500 blocks of disk quota. This is because we have >many many users, and limited disk space. We don't have any disk with >plenty of disk space. > >Our approach is as follows. I mentioned in my earlier message that the >compilers are installed with EXQUOTA, but I failed to mention that our >editors are also installed with EXQUOTA. This allows the students to >edit and edit and edit (as well as to compile and compile and compile) On our vax, users are divided up into personal accounts and class accounts. We have a cluster with an 8600 and two 780's. There are 7 RA81's in use. Two system, 1 for personal , 2 for class, one backup, and one spare. Each personal user gets 300 blocks and each class account gets 400. The compilers and linker are installed with EXQUOTA. The editor is not. It was possible to use the EDITOR to exceed many many blocks of diskquota very easily just by including whatever file and then saving it. -- Jeff Capehart Internet: micronaut%oak.decnet@pine.circa.ufl.edu University of Florida UUCP: ..!ihnp4!codas!ufcsv!beach.cis.ufl.edu!jdc