In January 2010, a BCC 1.2.0 patch is available through the OES 2 SP1 Linux patch channel (oes2sp1-January-2010-Scheduled-Maintenance-6749). For information about applying the patch, see Section 6.0, Updating (Patching) BCC 1.2.0 on OES 2 SP1 Linux.
The major changes for BCC 1.2.0 are described in the following sections:
The BCC 1.2.0 patch includes the following major bug fixes for the BCC engine:
Improves the update process to wait for the adminfsd and bccd daemons to gracefully stop before running the BCC install scripts. (Bug 561055)
Modified the novell-bcc init.d script to wait up to 15 seconds when bccd is stopped. Typically, the wait is less than 10 seconds.
Modified the post-install script of the Novell BCC specification file to wait up to 5 seconds when adminfsd is stopped. Typically, the wait is about 1 second.
Improves memory management functions that might cause the bccd daemon to die. Overall, the code was simplified and clarified so that the shared memory functions now do exactly what their names describe. The bccd daemon was modified to generate unique keys to verify that the keys are not in use by other processes, then to use the verified unique keys for its processing threads. (Bug 553527)
Improves the detection and handling of No Memory exceptions. In addition, if an exception is not caught and handled where it occurs, the engine’s main thread detects the exception and gracefully shuts itself down. (Bug 428161)
The BCC 1.2.0 patch for OES 2 SP1 Linux includes a new BCC resource driver template for Identity Manager that offers the following new feature and bug fixes:
Uses a newer policy linking format so that you are no longer prompted to update the driver in iManager. (New)
Adds the host resource name and Novell Distributed File Services (DFS) GUID attributes to the Volume objects that are synchronized for a BCC-enabled volume resource. (Bug 535127)
No longer creates duplicate NCP Server, Volume, and Pool objects when the landing zone is not the same location as the cluster server’s container. (Found while debugging Bug 537981)
Ensures that a volume resource’s link to the virtual NCP Server object is updated to point to the cluster where the resource is mounted. (Found while debugging Bug 537981)
The event for the IsClusterEnabled policy in a BCC resource driver now allows a resource’s peer list to be synchronized to the peer clusters, even if the cluster is disabled, if the current cluster’s name is being removed from the peer list. Only this specific change is allowed; other changes to a resource are dropped (vetoed) by the driver after a cluster is disabled. (Bug 434243)
The new BCC resource driver template is compatible with the following combinations of Identity Manager and operating systems:
|
Identity Manager |
Operating System |
|---|---|
|
Identity Manager 3.6 (32-bit) |
OES 2 SP1 Linux (32-bit) |
|
Identity Manager 3.6.1 (32-bit or 64-bit) |
OES 2 SP1 Linux (32-bit or 64-bit) |
|
Identity Manager 3.6.1 (32-bit or 64-bit) |
OES 2 SP2 Linux (32-bit or 64-bit) |
|
Identity Manager 3.5.x |
NetWare 6.5 SP8 |
The new BCC resource driver template is not automatically applied to existing drivers. You can continue to use your existing BCC resource drivers, or you can re-create the BCC resource drivers with the new template in order to take advantage of the changes it offers. We recommend that you re-create the drivers with the new template, but it is not required.