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: <2766@buengc.BU.EDU>
Date: 4 May 89 19:39:09 GMT
References: <171@larry.sal.wisc.edu> <17245@mimsy.UUCP> <2760@buengc.BU.EDU> <17287@mimsy.UUCP>
Reply-To: bph@buengc.bu.edu (Blair P. Houghton)
Followup-To: comp.unix.questions
Organization: Boston Univ. Col. of Eng.
Lines: 26

In article <17287@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
>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.[...]

I'll buy it.  It's been pointed out to me that excessive use of X
applications can fill up the swap space itself toot sweet, causing the
problem I get.

He may be correct, but the dozen xterms he runs from .login say he's being
a memory-hog.

				--Blair
				  "All I got is this one li'l window
				   for rn, and my login window, and
				   that spare, and that one with the
				   SPICE runs, and that xsplot with the
				   SPICE graphs, and the two artistically
				   arranged xclocks, and the bitmap of
				   Einstein, glaring at me all the time
				   to imagine more and know less, but
				   THAT's ALL... I swear... :-)"