Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!mit-eddie!uw-beaver!tektronix!reed!psu-cs!qiclab!neighorn
From: neighorn@qiclab.UUCP (Steven C. Neighorn)
Newsgroups: comp.bugs.sys5
Subject: Re: Sys V handling of insufficient swap space.
Message-ID: <412@qiclab.UUCP>
Date: Tue, 17-Mar-87 00:05:19 EST
Article-I.D.: qiclab.412
Posted: Tue Mar 17 00:05:19 1987
Date-Received: Sat, 21-Mar-87 07:36:17 EST
References: <1035@wang7.UUCP> <1078@hoxna.UUCP> <444@vsedev.VSE.COM> <1083@hoxna.UUCP> <306@osiris.oz>
Sender: neighorn@qiclab.UUCP
Reply-To: neighorn@qiclab.UUCP (Steven C. Neighorn)
Organization: Qic Laboratories, Portland Oregon
Lines: 20

In article <306@osiris.oz> greg@osiris.oz (Greg Kable) writes:
>There seems to be a bit of confusion with regard to this.  Firstly, to the
>best of my knowledge all System V.2 implementations will hang when they run out
>of swap space.  A rough description of how this occurs follows....
>
> ... description of crash procedure ...

Microport V/AT, a port of SYSV2 for the 80286, crashes in flames. On my 80386
running in '286 mode, I had occasion to run a couple inews programs and
three batchers and an editor, and a DANGER OUT OF SWAP SPACE message
appreared on the system console. The system had to be warm booted, and the
associated fsck's run. I have since increased the swap space, but oh, for
a real demand-paged virtual memory system, at least that would cut down on
the massive swaps. Maybe someday...

--
Steven C. Neighorn                tektronix!{psu-cs,reed}!qiclab!neighorn
Portland Public Schools      "Where we train young Star Fighters to defend the
(503) 249-2000 ext 337           frontier against Xur and the Ko-dan Armada"
QUOTE OF THE DAY ->                'Dr. Ruth is no stranger to friction.'