Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!ucbcad!ucbvax!TEMPLEVM.BITNET!V2002A
From: V2002A@TEMPLEVM.BITNET
Newsgroups: comp.os.vms
Subject: Strange system behavior with DISKQUOTA
Message-ID: <8712240047.AA25321@ucbvax.Berkeley.EDU>
Date: 23 Dec 87 14:00:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 33

Hello again,

    Having solved my hung logins problem by castrating the ALFMAINT
data file >:-) ...
    I installed ALL-IN-ONE and tried to run the Installation
Verification Procedure.  I got multiple "You are low on disk space"
messages and lo and behold my RD53 had only about 15000 free blocks.
(The Computer Based Training test explicitly told me that I needed
more disk space to complete the test and use CBI).
    This seemed plenty of space though.  So I deleted the
low (1000 block) entry for [1,4] in DISKQUOTA.  The IVP still insisted
that I was low on space so I went back into DISKQUOTA and:

        DISKQUOTA> ADD [1,4]/PERM=150000/OVER=10000
        DISKQUOTA> REBUILD

    Then the IVP for ALL_IN_ONE ran OK.  Also when I was "Low on
disk space" I got spurious <LF>s in the IVP.  They also showed up
in the log file [ALLIN1.IVPUSER]A1TRACE.LOG.  I think that somehow
DISKQUOTA interfered with the terminal characteristics, either
PASSTHRU or WRAP.  My reasoning on that point is based on a similar
problem on our PDP-11/44 (RSTS 9.4) in that if you exceed you
disk quota the system disables CONTROL_C!
    My questions are: 1) Is it necessary to have a DISKQ entry
for the system account? and 2) Why do both VMS and RSTS disk quota
managers interfere with the terminal settings?

                Andy Wing
     V2002A%TEMPLEVM.BITNET@CUNYVM.CUNY.EDU

     "Where have you gone WISCVM...
      BITNET sends its lonely mail to you, ooooh  ooooh ooooh..."

Disclaimer: Any disclaimers are subject to change without notice.