Well, now, there's an idea. That's a fairly recent trick with 5.3. You've got to remember I've been doing this stuff since at least z/VM 4.1.
Hey, now there's something that can go into that healthcheck thing we're supposed to come up with! Marcy Cortes Team Lead, Enterprise Virtualization - z/VM and z/Linux Enterprise Hosting Services w. (415) 243-6343 c. (415) 517-0895 "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Rob van der Heij Sent: Thursday, October 30, 2008 2:00 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Linux VM intermittently goes non-responsive On Thu, Oct 30, 2008 at 9:05 PM, Marcy Cortes <[EMAIL PROTECTED]> wrote: > Maybe I should have let them stare at the dumps for a few more weeks > ;) When you had your fun with it, you might want to put it as CP commands in the directory entry of AUTOLOG1 for example. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
