Received: by ATHENA-PO-2.MIT.EDU (5.45/4.7) id AA19156; Mon, 28 Aug 89 16:31:26 EDT
From: <bgardner@ATHENA.MIT.EDU>
Received: by ATHENA.MIT.EDU (5.45/4.7) id AA03247; Mon, 28 Aug 89 16:31:34 EDT
Received: by PINK.MIT.EDU (5.61/4.7) id AA00377; Mon, 28 Aug 89 16:31:04 -0400
Date: Mon, 28 Aug 89 16:31:04 -0400
Message-Id: <8908282031.AA00377@PINK.MIT.EDU>
To: don@ATHENA.MIT.EDU
Subject: and now the bad news
Cc: bgardner@ATHENA.MIT.EDU, bugs@ATHENA.MIT.EDU

   The re-boot *DID NOT* make the swap space problem go away for me.

   When I signed on originally, I was able to run both emacs and gcc
simultaneously. Later, I wasn't able to run emacs and gcc at the same time, but I could
independently. still later, I couldn't run gcc at all (without or without emacs
existing...tho I could still run emacs alone.)
   so, I tried your recommendation, and re-booted. (Doing a "pstat -s"
first from root with no window manager). Then I logged on and did another
"pstat -s" (this time from bgardner with a window manager running).
And I sent you a message about the pstat results.
Then I read afew messages, ran a program, and then tried to
run gcc, only to find that it wouldn't run (I had a new emacs window up).
I did all this within 15 mins of the reboot.
   So, I re-tried the re-boot...with the same results.
   basically, its gotten unbearably difficult to get any work done.
I can only use gcc or emacs at one time, and must alternate between them
to get my work done...and then, when the world breaks every 4 to 7 hours,
I must must re-boot my machine and log in again.
    -- Brian
