My Oracle Support Banner

How to Modify Capped-Memory of a Non-Global Zone Without Rebooting it (Doc ID 1596434.1)

Last updated on JULY 23, 2018

Applies to:

Solaris Operating System - Version 10 8/07 U4 and later
Information in this document applies to any platform.

Goal

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.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.