How to Modify Capped-Memory of a Non-Global Zone Without Rebooting it
Last updated on JULY 29, 2016
Applies to:Solaris Operating System - Version 10 8/07 U4 and later
Information in this document applies to any platform.
For non-global zone, capped-memory is configured via zonecfg(1M). For example:
If the capped-memory limits are changed in zonecfg, the non-global zone must be rebooted for the changes to take effect.
Sometimes it is desirable to modify the capped-memory for a running non-global zone without having to reboot the non-global zone.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms