Event Monitoring Service Version A.04.00.01 Release Notes

Patches and Fixes in this Version

Chapter 1 17

Patches and Fixes in this Version

Required and Recommended Patches

The contents of Event Monitoring Service A.03.20.01 and A.03.40 has been incorporated into

A.04.00 and A.04.00.01 release.

Fixes and Changes

The following defects have been ﬁxed in Event Monitoring Service version A.04.00.01:

JAGae64347

Problem: EMS registrar may send a NULL Resource Name to the legacy monitor when there

is memory corruption. As a result,the legacy monitor dumps core.

Resolution: The memory corruption in handling dictionary objects in the EMS registrar has

been ﬁxed.

JAGae63196

Problem: When the clients try to connect to a remote machine, EMS clients like moncheck and

toggle_switch may fail with the message "EMS registrar inetd service not started. Start

registrar and retry.".

Resolution: EMS code has been modiﬁed to handle EINPROGRESS and EINTR errors.

JAGae54891

Problem: When an EMS client and registrar try to write data to a socket, the write system call

might fail with errno set to EAGAIN repeatedly. As a result the EMS client, e.g. p_client or

cmcld, process may consume high CPU.

Resolution: The EMS code has been modiﬁed such that the EMS client and registrar write

data to a socket successfully.

JAGae50732

Problem: The description for syslog in the online help does not contain information about

logging level and facility.

Resolution: The description for syslog in the online help has been modiﬁed to include

information about logging level and facility.

JAGae38359