Re: Centos ISOs

2006-01-20 Thread Peter Webb, Toronto Transit Commission
The desire to download .iso images is because that is what the installation instructions are written for. It's been quite a while since I last did a Linux install, and I like having the crutch of written instructions. You did, however, tweak my memory, and I think that I used wget for my last

Linux Monitoring

2006-01-20 Thread Kreiter, Chuck
We are running four SUSE 9 Linux guests under z/VM 5.1. z/VM and Linux have all current maintenance and fixes applied. All 4 guests were cloned from the same base install. The problem we have is that occasionally, Linux will stop functioning. Our connection is via VNC. I haven't been able

Re: Linux Monitoring

2006-01-20 Thread Romanowski, John (OFT)
Sounds like our similar problem that was caused by developing scheduler Eligible lists, because we had not increased the CP default SRM STORBUF values of STORBUF: Q1=125% Q2=105% Q3=095% When problem recurs again do CP INDICATE to see if VM

2006-01-20 Recommended Linux on zSeries code drop to developerWorks

2006-01-20 Thread Gerhard Hiller
Please refer to: http://www.ibm.com/developerworks/linux/linux390/whatsnew.html for the 2006-01-20 change summary: New OCOs for Red Hat: - tape_3590 for Red Hat Enterprise Linux 4 Update 2 kernel security update (31-bit and 64-bit), kernel 2.6.9-22.0.2.EL (2006-01-17) - tape_3590 for

Re: IBM High Level Assembler for Linux on zSeries

2006-01-20 Thread Eddie Chen
Great! How about other high Level languages ... COBOL, PLI John R. Ehrman [EMAIL PROTECTED] com To Sent by: Linux on LINUX-390@vm.marist.edu 390 Port

Re: comments on mksles9root.sh for SP3

2006-01-20 Thread Nix, Robert P.
This is the first mention of IBM as a source of SuSE downloads that I've seen (even from IBMers). -- Robert P. Nix Mayo Foundation RO-OC-1-13 200 First Street SW 507-284-0844Rochester, MN 55905 - In theory, theory and practice are the same, but in

Re: comments on mksles9root.sh for SP3

2006-01-20 Thread John Schnitzler Jr
Step 5 below links you to the SUSE website which is where you can get your downloads. You are also prompted for your Novell Userid and password. Regards, John Schnitzler Jr Nix, Robert P. [EMAIL PROTECTED] edu

Re: comments on mksles9root.sh for SP3

2006-01-20 Thread Alan Altmark
On Friday, 01/20/2006 at 11:07 CST, Nix, Robert P. [EMAIL PROTECTED] wrote: This is the first mention of IBM as a source of SuSE downloads that I've seen (even from IBMers). The IBM website simply links to Novell's website. IBM is not distributing anything. You can get directly to SLES 9 at

Re: Linux Monitoring

2006-01-20 Thread Wolfe, Gordon W
Frequently this problem is caused by memory problems within linux. From VNC, launch top and watch it carefully over an extended period. if you see memory used creeping up or swap space used creeping up steadily, you might have an application with a memory leak. When memory and swap are used

Re: Linux Monitoring

2006-01-20 Thread Kreiter, Chuck
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. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Wolfe,

Re: Linux Monitoring

2006-01-20 Thread Gene Walters
We had the same problem a couple of years ago, and adjusting those buffers fixed ours. [EMAIL PROTECTED] 1/20/2006 10:06:44 AM Sounds like our similar problem that was caused by developing scheduler Eligible lists, because we had not increased the CP default SRM STORBUF values of STORBUF:

Re: comments on mksles9root.sh for SP3

2006-01-20 Thread Bernard Wu
Our support contract is with IBM. That's why we always start off at the IBM website first. Bernie Wu [EMAIL PROTECTED] Nix, Robert P. [EMAIL PROTECTED]To: LINUX-390@VM.MARIST.EDU edu cc:

Re: Linux Monitoring

2006-01-20 Thread Post, Mark K
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