home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!haven.umd.edu!wam.umd.edu!adhir
- From: adhir@wam.umd.edu (Al Dhir)
- Subject: Re: will this work for the swapfile growth problem?
- Message-ID: <1992Nov22.003244.11696@wam.umd.edu>
- Sender: usenet@wam.umd.edu (USENET News system)
- Nntp-Posting-Host: rac3.wam.umd.edu
- Organization: University of Maryland, College Park
- References: <By37LD.EKF@news.cso.uiuc.edu>
- Date: Sun, 22 Nov 1992 00:32:44 GMT
- Lines: 18
-
- In article <By37LD.EKF@news.cso.uiuc.edu> nap42487@uxa.cso.uiuc.edu (Nishith A. Patel) writes:
- >Seems like a lot of people who use the CSD experience swapfiles that grow huge.
- >How effective would this be: create a script that deletes whatever the swap
- >file is, and put that in the startup folder. Will OS/2 allocate a new one.
- >If so, what are the drawbacks to doing this?
- >
- This is not a solution to anything, it's a waste of time. The large swapfile
- problem surfaces after the machines been on for a while. When I first
- start up OS/2, it is ALWAYS at 4096. After working for a while, it starts
- growing.
-
- I am pretty sure it has to do with peices of screen memory being swapped out
- and forgotten. I need to report this to IBM.
- --
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Al Dhir Technical Consulting Staff
- Internet: adhir@cygnus.umd.edu University of Maryland, College Park
- Bitnet: adhir%cygnus.umd.edu@Interbit (301) 405-1500 * (301) 405-3014
-