Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!bu-cs!buengc!bph
From: bph@buengc.BU.EDU (Blair P. Houghton)
Newsgroups: comp.unix.questions
Subject: Re: more on unix swap space problem
Message-ID: <2760@buengc.BU.EDU>
Date: 3 May 89 18:07:48 GMT
References: <171@larry.sal.wisc.edu> <17245@mimsy.UUCP>
Reply-To: bph@buengc.bu.edu (Blair P. Houghton)
Followup-To: comp.unix.questions
Organization: Boston Univ. Col. of Eng.
Lines: 15

In article <17245@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
>
>The kernel has compiled into it the list of devices it *might ever*
>swap on.  Initially, it swaps/pages/allocates_backing_store_from only
>the first; the others are added with the vswapon() system call, made by
>/etc/swapon,[...]

I ran into the insufficient-memory bug, too.

My sysadmin (the fella sitting to my left) says that the swap space is
protected in such a way that an overlarge set of /usr/adm files won't
affect it.  I was attributing the problem to the fact that we've allowed
/usr/adm/acct to hit 17meg.  He says they're unrelated.  I don't buy it.

				--Blair