[zones-discuss] correct procedure to shutdown zones
All, IHAC that created zones and wants the users to be able to reboot the zones.they put the following in their password file: bounce:x:0:1:Bounce Account:/:/usr/sbin/reboot this way a user can 'su bounce ' and reboot the zone..The zone hangs while coming down and customer wants to know why.. I checked with my escalation engineers and they mentioned that 'zoneadm -z ' was the correct proocedure to take down a zone.. Customer is stating there is no documentation that states that zoneadm is the only procedure to take down a zone and that reboot is not acceptable. So I am looking for docmentation that confirms the correct procedures to take down a zone and where reboot is not correct. It maybe that reboot is acceptable as root but not supported using the pasword file, but customer needs to see it in writing Thanks Peter -- = __ /_/\ /_\\ \Peter Wilk - OS/Security Support /_\ \\ / Sun Microsystems /_/ \/ / / 1 Network Drive, P.O Box 4004 /_/ / \//\ Burlington, Massachusetts 01803-0904 \_\//\ / / 1-800-USA-4SUN, opt 1, opt 1,case number# \_/ / /\ / Email: [EMAIL PROTECTED] \_/ \\ \ = \_\ \\ \_\/ = ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] correct procedure to shutdown zones
Peter Wilk wrote: All, IHAC that created zones and wants the users to be able to reboot the zones.they put the following in their password file: bounce:x:0:1:Bounce Account:/:/usr/sbin/reboot this way a user can 'su bounce ' and reboot the zone..The zone hangs while coming down and customer wants to know why.. I checked with my escalation engineers and they mentioned that 'zoneadm -z ' was the correct proocedure to take down a zone.. Customer is stating there is no documentation that states that zoneadm is the only procedure to take down a zone and that reboot is not acceptable. So I am looking for docmentation that confirms the correct procedures to take down a zone and where reboot is not correct. It maybe that reboot is acceptable as root but not supported using the pasword file, but customer needs to see it in writing Thanks Peter The only problem with reboot is that the shutdown scripts don't run. You would be better off with init 0 or shutdown -i0 -y. Using reboot or halt doesn't have applications gracefully shutdown, they just get killed. ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] correct procedure to shutdown zones
I'd suggest a role with the Maintenance and Repair profile. This will allow the authorized user(s) to assume that role and run /sbin/init. This can be set per zone, from within the zone. Something such as: # roleadd -u roleid -g group -P Maintenance and Repair userinit # usermod -u userid -P userinit Peter Wilk wrote On 08/25/06 10:36,: All, IHAC that created zones and wants the users to be able to reboot the zones.they put the following in their password file: bounce:x:0:1:Bounce Account:/:/usr/sbin/reboot this way a user can 'su bounce ' and reboot the zone..The zone hangs while coming down and customer wants to know why.. I checked with my escalation engineers and they mentioned that 'zoneadm -z ' was the correct proocedure to take down a zone.. Customer is stating there is no documentation that states that zoneadm is the only procedure to take down a zone and that reboot is not acceptable. So I am looking for docmentation that confirms the correct procedures to take down a zone and where reboot is not correct. It maybe that reboot is acceptable as root but not supported using the pasword file, but customer needs to see it in writing Thanks Peter ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] correct procedure to shutdown zones
Brian, Thanks and I agree with you, but customer wants to see documentation from SUN which states that ..any thoughts where that would be found Peter Brian Kolaci wrote On 08/25/06 10:52,: Peter Wilk wrote: All, IHAC that created zones and wants the users to be able to reboot the zones.they put the following in their password file: bounce:x:0:1:Bounce Account:/:/usr/sbin/reboot this way a user can 'su bounce ' and reboot the zone..The zone hangs while coming down and customer wants to know why.. I checked with my escalation engineers and they mentioned that 'zoneadm -z ' was the correct proocedure to take down a zone.. Customer is stating there is no documentation that states that zoneadm is the only procedure to take down a zone and that reboot is not acceptable. So I am looking for docmentation that confirms the correct procedures to take down a zone and where reboot is not correct. It maybe that reboot is acceptable as root but not supported using the pasword file, but customer needs to see it in writing Thanks Peter The only problem with reboot is that the shutdown scripts don't run. You would be better off with init 0 or shutdown -i0 -y. Using reboot or halt doesn't have applications gracefully shutdown, they just get killed. -- = __ /_/\ /_\\ \Peter Wilk - OS/Security Support /_\ \\ / Sun Microsystems /_/ \/ / / 1 Network Drive, P.O Box 4004 /_/ / \//\ Burlington, Massachusetts 01803-0904 \_\//\ / / 1-800-USA-4SUN, opt 1, opt 1,case number# \_/ / /\ / Email: [EMAIL PROTECTED] \_/ \\ \ = \_\ \\ \_\/ = ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] question on zones and OS level
Peter Wilk wrote: All, IHAC that is asking the following..( solaris 5.10) if the global zone is at 01/06 and there are 2 non root zones at 01/06 if the global zone is updated to 06/06 can the user update only 1 zone to 06/06 and leave the other zone at 01/06.. No. All zones using an instance of Solaris will be at the same update level. They all share the same OS kernel. if so is there any issues that I need to communicate Thanks Peter -- -- Jeff VICTOR Sun Microsystemsjeff.victor @ sun.com OS AmbassadorSr. Technical Specialist Solaris 10 Zones FAQ:http://www.opensolaris.org/os/community/zones/faq -- ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] question on zones and OS level
Jeff Victor wrote: Ihsan Zaghmouth wrote: Peter, What are the type of the Zones ? It would be interesting to try this with a Whole-root Zone, definitely not a Sparse. 1. Fully Backup the 01/06 Whole-Root and then update the GZ with 06/06. 2. You can't keep any zones for now during updates (Zulu initiative working on this ), so you have to unconfigure/delete them You *can* keep zones if you use standard upgrade. You cannot keep zones if you use Live Upgrade. Definitely, missed the differentiation. Thanks for pointing it out 3. After update, Restore the 01/06 Whole-Root and check it out ... 4. Check it out and hope for the best .. Sun would not support this. I agree 100%. This was a hypothesis/thought of desperation/adventure, which realisticaly Sun does not support . What would be the reason to stay behind on 01/06 if 06/06 comes with the best of 01/06 and more ! cheers Ihsan Peter Wilk wrote: All, IHAC that is asking the following..( solaris 5.10) if the global zone is at 01/06 and there are 2 non root zones at 01/06 if the global zone is updated to 06/06 can the user update only 1 zone to 06/06 and leave the other zone at 01/06.. if so is there any issues that I need to communicate -- My2Signature Ihsan Zaghmouth Sr. SAP Solution Architect SUN-SAP Business Applications Group (832) 859-2818 (Cell) (713) 784-2818 (Home) (713) 784-2818 (Fax) [EMAIL PROTECTED] ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] Re: correct procedure to shutdown zones
This procedure is used from the global zone. It is an alternate way to halt a zone that doesn't use the 'zoneadm halt' or 'zoneadm reboot' commands. How to Use zlogin to Shut Down a Zone http://docs.sun.com/app/docs/doc/819-2450/6n4o5mdfo?a=view - Penny This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
