Skip Navigation Links | |
Exit Print View | |
![]() |
System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones Oracle Solaris 10 1/13 Information Library |
1. Introduction to Solaris 10 Resource Management
2. Projects and Tasks (Overview)
3. Administering Projects and Tasks
4. Extended Accounting (Overview)
5. Administering Extended Accounting (Tasks)
6. Resource Controls (Overview)
7. Administering Resource Controls (Tasks)
8. Fair Share Scheduler (Overview)
9. Administering the Fair Share Scheduler (Tasks)
10. Physical Memory Control Using the Resource Capping Daemon (Overview)
11. Administering the Resource Capping Daemon (Tasks)
13. Creating and Administering Resource Pools (Tasks)
14. Resource Management Configuration Example
15. Resource Control Functionality in the Solaris Management Console
16. Introduction to Solaris Zones
17. Non-Global Zone Configuration (Overview)
18. Planning and Configuring Non-Global Zones (Tasks)
19. About Installing, Halting, Cloning, and Uninstalling Non-Global Zones (Overview)
20. Installing, Booting, Halting, Uninstalling, and Cloning Non-Global Zones (Tasks)
21. Non-Global Zone Login (Overview)
22. Logging In to Non-Global Zones (Tasks)
23. Moving and Migrating Non-Global Zones (Tasks)
24. Oracle Solaris 10 9/10: Migrating a Physical Oracle Solaris System Into a Zone (Tasks)
25. About Packages and Patches on an Oracle Solaris System With Zones Installed (Overview)
What's New in Packaging and Patching When Zones Are Installed
Packaging and Patch Tools Overview
Patches Generated for Packages
Package Operations Possible in the Global Zone
Package Operations Possible in a Non-Global Zone
How Zone State Affects Patch and Package Operations
About Adding Packages in Zones
Using pkgadd in the Global Zone
Adding a Package to the Global Zone and to All Non-Global Zones
Adding a Package to the Global Zone Only
Adding a Package Installed in the Global Zone to all Non-Global Zones
Using pkgadd in a Non-Global Zone
About Removing Packages in Zones
Using pkgrm in the Global Zone
Removing a Package From the Global Zone and From all Non-Global Zones
Using pkgrm in a Non-Global Zone
Setting Package Parameters for Zones
SUNW_PKG_ALLZONES Package Parameter
SUNW_PKG_HOLLOW Package Parameter
SUNW_PKG_THISZONE Package Parameter
Oracle Solaris 10 10/09: Zones Parallel Patching to Reduce Patching Time
Applying Patches on an Oracle Solaris System With Zones Installed
Using patchadd in the Global Zone
Using patchadd in a Non-Global Zone
Interaction of patchadd -G and the pkginfo Variable on a System With Zones
Removing Patches on an Oracle Solaris System With Zones Installed
Using patchrm in the Global Zone
Using patchrm in a Non-Global Zone
27. Oracle Solaris Zones Administration (Overview)
28. Oracle Solaris Zones Administration (Tasks)
29. Upgrading an Oracle Solaris 10 System That Has Installed Non-Global Zones
30. Troubleshooting Miscellaneous Oracle Solaris Zones Problems
31. About Branded Zones and the Linux Branded Zone
32. Planning the lx Branded Zone Configuration (Overview)
33. Configuring the lx Branded Zone (Tasks)
34. About Installing, Booting, Halting, Cloning, and Uninstalling lx Branded Zones (Overview)
35. Installing, Booting, Halting, Uninstalling and Cloning lx Branded Zones (Tasks)
36. Logging In to lx Branded Zones (Tasks)
37. Moving and Migrating lx Branded Zones (Tasks)
38. Administering and Running Applications in lx Branded Zones (Tasks)
Starting with patches 119254-41 and 119255-41, the patchadd and patchrm patch installation utilities have been modified to change the way in which certain patches delivering features are handled. This modification affects the installation of these patches on any Oracle Solaris 10 release. These deferred-activation patches better handle the large scope of change delivered in feature patches such as kernel patches associated with Oracle Solaris 10 releases after the Oracle Solaris 10 3/05 release.
Deferred-activation patching uses the loopback file system (lofs) to ensure the stability of the running system. When a patch is applied to the running system, the lofs preserves stability during the patching process. These large kernel patches have always required a reboot, but now the required reboot activates the changes made by the lofs. The patch README provides instructions on which patches require a reboot.
If you are running non-global zones or have lofs disabled, consider these points when installing or removing deferred-activation patches:
All non-global zones must be halted for this patch operation. You must halt the non-global zone before applying the patch.
Deferred-activation patching requires the loopback file system (lofs). Systems running Sun Cluster 3.1 or Sun Cluster 3.2 are likely to have lofs turned off because of restrictions on HA-NFS functionality when lofs is enabled. Therefore, before a deferred-activation patch is installed, you must re-enable the loopback file system by removing or commenting out the following line in the /etc/system file:
exclude:lofs
Then reboot your system and install the patch. After you have completed the patch installation operation, restore or uncomment the same line from the /etc/system file. You must then reboot to resume normal operations.
Note - Using Oracle Solaris Live Upgrade to manage patching can prevent the problems associated with patching a running system. Oracle Solaris Live Upgrade can reduce the amount of downtime involved in patching and limit risk by providing fallback capability if problems occur. You can patch an inactive boot environment while the system is still in production, and boot back to original boot environment (BE) if problems are discovered in the new BE. See Upgrading a System With Packages or Patches in Oracle Solaris 10 8/11 Installation Guide: Solaris Live Upgrade and Upgrade Planning.