Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Administration: Basic Administration Oracle Solaris 10 1/13 Information Library |
1. Oracle Solaris Management Tools (Road Map)
2. Working With the Solaris Management Console (Tasks)
3. Working With the Oracle Java Web Console (Tasks)
4. Managing User Accounts and Groups (Overview)
5. Managing User Accounts and Groups (Tasks)
6. Managing Client-Server Support (Overview)
7. Managing Diskless Clients (Tasks)
8. Introduction to Shutting Down and Booting a System
9. Shutting Down and Booting a System (Overview)
10. Shutting Down a System (Tasks)
11. Modifying Oracle Solaris Boot Behavior (Tasks)
12. Booting an Oracle Solaris System (Tasks)
13. Managing the Oracle Solaris Boot Archives (Tasks)
14. Troubleshooting Booting an Oracle Solaris System (Tasks)
15. x86: GRUB Based Booting (Reference)
16. x86: Booting a System That Does Not Implement GRUB (Tasks)
17. Working With Oracle Configuration Manager
18. Managing Services (Overview)
20. Managing Software (Overview)
What's New in Software Management in the Oracle Solaris Operating System?
Oracle Solaris Auto Registration
Package and Patching Tools Enhancements to Support Oracle Solaris Zones
Common Agent Container Included in the Oracle Solaris OS
Improvements to How patchadd -M Command Handles Multiple Patches
Where to Find Software Management Tasks
Tools for Managing Software Packages
Adding or Removing a Software Package (pkgadd)
Key Points for Adding Software Packages (pkgadd)
Guidelines for Removing Packages (pkgrm)
Avoiding User Interaction When Adding Packages (pkgadd)
Using a Response File (pkgadd)
21. Managing Software With Oracle Solaris System Administration Tools (Tasks)
22. Managing Software by Using Oracle Solaris Package Commands (Tasks)
This section describes the new software management features in this Oracle Solaris release.
For a complete listing of new features and a description of Oracle Solaris releases, see the Oracle Solaris 10 1/13 What’s New.
Oracle Solaris 10 9/10: For information on auto registration, see Chapter 17, Working With Oracle Configuration Manager.
Oracle Solaris 10 10/09: Starting with this release, the following enhancements have been made to the package and patching tools to support systems that have multiple non-global zones installed:
Parallel Patching of Zones
The Parallel Patching of Zones feature introduces enhancements to the standard Oracle Solaris 10 patching tools to enable patching of non-global zones in parallel. This feature enhancement improves patching performance when multiple non-global zones are installed on a system by accelerating the time it takes to patch systems. Because zones are isolated environments, it is safe to patch multiple zones in parallel. This ability applies to both sparse zones and whole root zones.
These improvements primarily include changes to the patchadd and patchrm commands. A new configuration file, /etc/patch/pdo.conf, can be modified to specify a number that defines how many zones are patched in parallel.
Note - If you are not running at least the Solaris 10 10/09 release, the feature is implemented through patch 119254-66, or later revision (SPARC), and 119255-66, or later revision (x86). The global zone is still patched before the non-global zones are patched.
For more information, see the patchadd(1M) and the patchrm(1M) man pages.
Turbo-Charging of SVr4 Packaging Commands
This feature accelerates the time it takes to install the Solaris OS, use Solaris Live Upgrade, or install non-global zones by using SVr4 package commands. Note that this feature cannot be disabled.
For more details about these and other enhancements that support the use of package and patch tools in a zones environment, see the following documentation:
Patching tools have changed to handle larger patches. Starting with patch 119254-42 and 119255-42, the patch installation commands, patchadd and patchrm, have been modified to change the way in which certain patches that deliver new features are handled. This modification affects the installation of these patches on any Oracle Solaris OS. These deferred-activation patches are better equipped to handle the large scope of changes that are delivered in feature patches.
For more details, see http://www.oracle.com/technetwork/systems/index.html.
The Common Agent Container is a stand-alone Java program that implements a container for Java management applications. This program provides a management infrastructure that is designed for Java Management Extensions (JMX) and Java Dynamic Management Kit (Java DMK) based management functionality. The software is installed by the SUNWcacaort package and resides in the /usr/lib/cacao directory.
Typically, the container is not visible.
However, there are two instances when you might need to interact with the container daemon:
In the event that another application attempts to use a network port that is reserved for the Common Agent Container.
In the event that a certificate store is compromised. If this conflict occurs, you might have to regenerate the Common Agent Container certificate keys.
For information about how to troubleshoot these problems, see Troubleshooting Common Agent Container Problems in the Oracle Solaris OS in System Administration Guide: Advanced Administration.
Oracle Solaris 10: Starting with this release, the functionality of the patchadd -M command is improved to more effectively and efficiently handle multiple patches and any dependencies between patches. As a result, you no longer have to specify patch IDs in numerical order when using the patchadd command.
Note that if you use the patchadd -M command without specifying a patch ID or patch IDs, all the patches in the directory are automatically installed on the system. To install a specific patch, or patches, you must specify the patch ID when using the patchadd -M command.
For more information, see the patchadd(1M) man page.
Oracle Solaris 10: The package and patch tools were enhanced in Oracle Solaris 10 to provide improved performance and extended functionality.
As a part of these enhancements, the pkgchk command now provides a new option to assist you in mapping files to packages. To map files to packages, use the pkgchk -P option instead of grep pattern/var/sadm/install/contents. The -P option enables you to use a partial path. Use this option with the -l option to list the information about the files that contain the partial path. For more information see How to Check the Integrity of Installed Objects ( pkgchk -p, pkgchk -P) and the pkgchk(1M) man page.