On Mon, May 7, 2012 at 3:57 PM, Mark Creamer <[email protected]> wrote:
> I was reading about how to update non-global zones, and found a
> Solaris document which says the following:
>
> 1. Update the Global Zone
> 2. Reboot
> 3. Halt the non-global zone (zoneadm -z myzone halt)
> 4. Detach the zone (zoneadm -z myzone detach)
> 5. Re-attach the zone with -u (zoneadm -z myzone attach -u)
>
> In my testing, this seems to go fine. My question is, what happens
> when you halt a zone - for example, if MySQL is running on that
> non-global zone, should you stop it first before halting the zone to
> avoid the risk of corrupting data? Or is a halt safe without stopping
> any running services first?
I normally do:
zlogin myzone init 5
This makes the zone shut down normally, running all the shutdown
procedures. "zoneadm halt" does not do that. Here's the help output
for "zoneadm halt":
Halts specified zone, bypassing shutdown scripts and removing
runtime resources of the zone.
--
Venlig hilsen / Kind regards
Jeppe Toustrup (aka. Tenzer)
_______________________________________________
OpenIndiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss
