This is probably _not_ a memory leak of any kind. It really sounds like your Linux guests are (perhaps) too large, and getting swapped out. (That's the eligible list stuff John Romanowski talked about.) The only thing that will fix it is: 1. Make sure your Linux guests are no bigger than they need to be. 2. Tune your SRM parameters so that they are more appropriate for a Linux workload. The defaults are longstanding ones that were intended for CMS users. 3. Make sure you have enough real and expanded storage to support the workload you intend to run.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kreiter, Chuck Sent: Friday, January 20, 2006 1:00 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Linux Monitoring Thanks for the suggestion. I will give that a try. On 2 of the images, we don't have anything other than base operating system components running so I'm wondering what would be leaking memory. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
