Hi, I think the best way to shutdown is to use the SIGNAL command with the maximum timeout value of 32767 and using the kernel 'vmpoff=LOGOFF' parameter in the /etc/zipl.conf. This way CP will try to logoff the machine only after about 9 hours (more than enough to fix any delays) and Linux kernel will automatically logoff itself before halting... So, you won’t have to login the Linux to shut him down and you are sure he will logoff as soon as the Linux is halted.
Hope this helps, Offer Baruch. -----הודעה מקורית----- מאת: Linux on 390 Port [mailto:[EMAIL PROTECTED] בשם Edmund R. MacKenty נשלח: ב 20 אוקטובר 2008 17:35 אל: [email protected] נושא: Re: The correct way to shutdown z/Linux Guest Softly On Monday 20 October 2008 09:35, van Sleeuwen, Berry wrote: >Indeed, if the application has the correct init scripts and the SIGNAL >is trapped to a "shutdown -h now" then a SIGNAL would correctly shutdown >the application and the guest. But only if the SIGNAL has been given >enough time to shutdown before CP will force the user. > >That would trigger my question, how to determine what the correct time >would be? We started with 300 seconds, and two years ago we increased >the time to 600 secs. But we have discovered that even 5 minutes could >well be too short to shutdown the database. I ran into this very problem on my product. Originally, we had written it to do a "shutdown -h now", wait until the network connection terminated (sshd was stopped), then wait a few minutes more before logging off the guest. But customers pointed out that this method did not ensure that everything was shut down before the logoff. If your filesystems haven't been sync'd before the logoff, you've got a possibility of corruption. So we now have Provisioning Expert monitor the console output from that guest, wait until it sees the message saying that the processor has halted, and then log off the guest. This is basically what Berry suggested: automating what we would do as admins. It's really the only way because you can't predict the timing of anything in a virtual environment because you don't control how much CPU you'll get. So the problem may not be that the Oracle shutdown sequence hasn't completed by the time CP logs your guest off. That might finish just fine, but unless your filesystems are sync'd and unmounted before the logoff, you haven't really saved the final state of the system. - MacK. ----- Edmund R. MacKenty Software Architect Rocket Software, Inc. Newton, MA USA ---------------------------------------------------------------------- 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 No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.8.1/1732 - Release Date: 10/18/2008 6:01 PM ---------------------------------------------------------------------- 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
