This section summarizes the new features introduced in Novell Open Enterprise Server (OES) 2 SP2 that either involve multiple services or are not covered in service-specific documentation. For information on service-specific new features, see Section 1.8, Links to What's New Sections.
OES 2 SP2 includes support for third-party developers to create auditing products. For more information, see Section 22.1.2, NSS Auditing Engine.
With the release of OES 2 SP2, the Linux platform on which OES services run is changed from SUSE Linux Enterprise Server (SLES) 10 SP2 to SLES 10 SP3 and includes Tomcat 5.5.
This has been added in OES 2 SP2.
The Partitioner in the YaST Install offers an option to “Create an EVMS Proposal.”
For unpartitioned devices over 20 GB in size, this option creates a boot partition and a container for the swap and / (root) volumes in up to the first 20 GB, and leaves the remainder of the space on the device as unpartitioned free space. The default / partition size is 10 GB. The swap size is 1 GB or larger, depending on the amount of RAM the server has.
IMPORTANT:This option applies only if you are installing an NSS volume on the same disk as your Linux root (/) partition.
Starting with OES 2 SP2, cross-protocol file locking (CPL) is enabled by default as follows:
All new servers with NCP installed have CPL turned on.
If an upgraded server was not configured for CPL prior to the upgrade, CPL will be turned on.
If an upgraded server was configured for CPL prior to the upgrade, the CPL setting immediately preceding the upgrade is retained.
If a server is only accessed through NCP (AFP and CIFS are not installed), you can achieve an NCP performance gain of about 10%. However, there is a critical caveat. If you later install AFP or CIFS and you forget to re-enable CPL, data corruption can occur.
There are also obvious implications for clustering because the CPL settings for clustered nodes must match. For example, if an unmodified OES 2 SP1 node is clustered with an unmodified OES 2 SP2 node, their CPL settings will conflict and one of the nodes must be modified.
For more information about cross-protocol locking, see Configuring Cross-Protocol File Locks for NCP Server
in the OES 2 SP3: NCP Server for Linux Administration Guide.
The DSfW installation has been rearchitected with a focus on usability and simplicity.
The Java Console for DNS/DHCP management is now available for Linux.
AFP, NCP, and Samba all have improved performance in OES 2 SP2.
Gateway parity with NetWare.
Support for upgrading through the SP Channel is included. For more information, see Using the Patch Channel to Upgrade (Online)
in the OES 2 SP3: Installation Guide.
OES 2 SP2 service clients are supported on Windows 7.