Mike,
Per the linux doc for SLES10 it states that the following change be
made :
In each linux guest's /etc/inittab; I have changed the shutdown -r to
shutdown -h
Is there something else from a linux standpoint that needs to be done
?
Thank you,
Bob
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Mike Walter
Sent: Wednesday, June 03, 2009 2:00 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Clean Linux Guest Shutdown
Have you updated each Linux guest so that they are registered to receive
and respond to the SIGNAL SHUTDOWN service?
Check your Linux distribution for the proper means to register for the
SIGNAL SHUTDOWN service, and how to respond appropriately.
Mike Walter
Hewitt Associates
Any opinions expressed herein are mine alone and do not necessarily
represent the opinions or policies of Hewitt Associates.
"Robert J McCarthy" <bob.mccar...@custserv.com>
Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
06/03/2009 12:43 PM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Clean Linux Guest Shutdown
I am trying to develop a shutdown procedure to cleanly shutdown my linux
guests, prior to shutting down vm. Reading the documentation in the
virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have
setup the following :
1. In each linux guest's /etc/inittab; I have changed the shutdown -r to
shutdown -h
2. In my autolog1 exec I have placed the following command:
CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to
respond)
Note: I have also entered the command manually
When I issue the shutdown, vm shuts down before most if not all linux
guests have responded or completed shutdown; always within a minute or
two. As a result I end up with file corruption in some linux guests
after
vm is re-IPLed and the guests are brought back up.
Is there a better way to accomplish a clean linux shutdown.
Thank you,
Bob
The information contained in this e-mail and any accompanying documents
may contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if
this message has been addressed to you in error, please immediately
alert the sender by reply e-mail and then delete this message, including
any attachments. Any dissemination, distribution or other use of the
contents of this message by anyone other than the intended recipient is
strictly prohibited. All messages sent to and from this e-mail address
may be monitored as permitted by applicable law and regulations to
ensure compliance with our internal policies and to protect our
business. E-mails are not secure and cannot be guaranteed to be error
free as they can be intercepted, amended, lost or destroyed, or contain
viruses. You are deemed to have accepted these risks if you communicate
with us by e-mail.
