Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!tank!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.questions
Subject: Re: more on unix swap space problem
Message-ID: <17287@mimsy.UUCP>
Date: 4 May 89 01:12:45 GMT
References: <171@larry.sal.wisc.edu> <17245@mimsy.UUCP> <2760@buengc.BU.EDU>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 17

In article <2760@buengc.BU.EDU> bph@buengc.BU.EDU (Blair P. Houghton) writes:
>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.

He is correct.  Swap space is allocated only as backing store for
processes.  It is completely unaffected by file sizes (although file
sizes may affect the amount of memory allocated by programs reading
or writing those files).

Under some systems (SunOS 4.x and Mach), you can swap on ordinary
files, so if you run out of VM, you can make a big file and add it
to the backing store pool.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris