Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!uunet!steinmetz!vdsvax!barnett From: barnett@vdsvax.UUCP Newsgroups: comp.unix.wizards Subject: Recovery from swap failure Message-ID: <2433@vdsvax.steinmetz.UUCP> Date: Tue, 1-Sep-87 11:37:59 EDT Article-I.D.: vdsvax.2433 Posted: Tue Sep 1 11:37:59 1987 Date-Received: Thu, 3-Sep-87 01:45:51 EDT Reply-To: barnett@steinmetz.UUCP (Bruce G Barnett) Organization: General Electric CRD, Schenectady, NY Lines: 27 We have a resource problem related to insufficient swap space. We plan to get additional disks, but I was wondering is anyone has any advice on the proper way to handle this. We have a machine (Sun 3/260) dedicated to simulations (HILO). Someone submits a large job that will take several hours and it allocated quite a bit of virtual memory. Now someone submits a small job on the same machine, which allocates some more memory. Now the large job runs out of swap space, and aborts after running for 20 hours. People scream, etc. I could write a queuing daemon, but people don't want to wait for a 24 hour job to complete until their 20 minute job starts. Assume only one machine. Assume no more disk space available. Should we complain to the vendor for writing software that can't recover from the swap limitation? Is there any scheme that we can use that will allow us to work around this problem in the short term? (Yes, we plan to purchase a Sun 4.) -- Bruce G. Barnett uunet!steinmetz!barnett