home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.sysadmin
- Path: sparky!uunet!stanford.edu!leland.Stanford.EDU!news
- From: magnus@Fisher.Stanford.EDU (Magnus Nordborg)
- Subject: Re: Rebooting (was Re: help! /private/vm/swapfile 44MB. How to shrink it?)
- Message-ID: <1992Sep8.190721.4559@leland.Stanford.EDU>
- Sender: news@leland.Stanford.EDU (Mr News)
- Organization: DSO, Stanford University
- References: <BOB.92Sep8095726@volitans.MorningStar.Com>
- Date: Tue, 8 Sep 92 19:07:21 GMT
- Lines: 27
-
- In article <BOB.92Sep8095726@volitans.MorningStar.Com> bob@MorningStar.Com
- (Bob Sutterfield) writes:
-
- Deleted stuff
-
- > An ever-growing swap file is a bug that no user should tolerate, and
- > that any vendor should be embarassed to let out the door, even on its
- > first limited-circulation alpha prerelease of a new OS version.
- > Frequent rebooting is not an acceptable solution to an OS bug.
-
- The swapfile is *not* "ever growing" if you specify a maximum size in
- /etc/swaptab. Of course, doing so will not stop the system from running
- out of swapspace, but the alternative seems to be what one does on many
- other Unix machines: pre-allocate a couple of hundred megabytes for a swap
- partition. Then you will not have to see virtual memory eating your disk
- because, in essence, it already has!
-
- This is not to say that it wouldn't be nice if the swap file could shrink
- dynamically as well, but only to claim that it isn't as horrible as some
- postings seem to indicate. :-)
- --
-
-
- Magnus Nordborg
- Department of Biological Sciences
- Stanford University
- magnus@fisher.stanford.edu (NeXT mail preferred)
-