Assuming you do not have access to the source of this application, you might try setting up a Bochs sandbox for it so that it won't interfere with the rest of the system and can be restarted at need more rapidly. On Tue, 13 May 2003, Jay Kline wrote: > On a server I admin there is a custom application that likes to consume large > ammounts of memory. Apparently, there are no checks within the application > when it allocates memory because it seems to kill the box occationally. the > kernel logger says it ran out of memory, then eventully the box stops > responding, except to pings. I need some suggestions for this, we cant throw > more memory at the box, but that wont solve the problem (this app WILL > consume anything you give it). I know there must be some way to limit a > process's memory usage- at least enough to protect the kernel better. We > have like 6 gig's of swap partitions thrown at it right now, but I am fairly > certain that it dosnt use much, if any, of it. I know its almost a flame war, > but in the situation where you have one app consuming most of the memory, > what is the best setup with swap? > > Jay > > -- Daniel Taylor dante at argle.org Forget diamonds, Copyright is forever. _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list