Path: utzoo!attcan!uunet!husc6!uwvax!vanvleck!uwmcsd1!ig!agate!helios.ee.lbl.gov!pasteur!ucbvax!CORNELLC.CCS.CORNELL.EDU.BITNET!ewilts%Ins.MRC.AdhocNet.CA%Stasis.MRC.AdhocNet.CA%UNCAEDU. From: ewilts%Ins.MRC.AdhocNet.CA%Stasis.MRC.AdhocNet.CA%UNCAEDU.@CORNELLC.CCS.CORNELL.EDU.BITNET (Ed Wilts) Newsgroups: comp.os.vms Subject: MPW_HILIMIT Message-ID: <880628153642.03o@Ins.MRC.AdhocNet.CA> Date: 28 Jun 88 21:36:41 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 17 Just a reminder to all people who want to play with the parameter MPW_HILIMIT. Ensure that MPW_WAITLIMIT is EXACTLY EQUAL to MPW_HILIMIT. If they are un- equal the following will happen: When a processes modifies a page and MPW_WAITLIMIT is reached, the process will enter a RWMPB state. It will stay that way until MPW_HILIMIT is reached at which point SWAPPER will write out the modified pages and normall processing continues. It is easy to see what happens if MPW_HILIMIT > MPW_WAITLIMIT: processes will enter the RWMPB state and stay there forever because MPW_HILIMIT will never be reached. I just spent the morning trying to figure out why my system kept hanging as soon as users starting to use it (I just know I shouldn't let users on). Why does SYSGEN not check for this obvious attempt to shoot yourself in the foot (VMS 5.0?) ? .../Ed