PROBLEM: (90973) (PATCH ID: OSF520-254)
********
On the first startup following a system panic, the kernel's error log
buffer is copied to a file so that events contained in the buffer can
be recovered and logged by the binary error log daemon, binlogd.  If
the contents of the buffer are invalid, it is possible for binlogd to
coredump while processing the buffer.  If this happens, the file
containing the buffer is not removed, and binlogd will attempt to
recover the events again the next time it is started.  It is most
likely that binlogd will coredump again, and continue to do so on each
subsequent startup until the file is removed.
This problem is fixed by application of this patch.


PROBLEM: (92167) (PATCH ID: OSF520-423)
********
In time zones that are east of the Prime Meridan (with a positive
offset from GMT) Compaq Analyze displays the offset value with a zero
(0) in place of the expected plus sign (+) in some display formats.  In
time zones with a negative offset the time is displayed correctly.
This patch produces the correct display for all time zones.


PROBLEM: (QAR:) (PATCH ID: OSF520-530)
********
If the system is brought down using the "init 0" command, it is possible
that the final binary error log entry may not be completely written to the 
disk, resulting in trailing logfile corruption.  This patch fixes the 
problem by syncing the logfile before closing it.


PROBLEM: (95787) (PATCH ID: OSF520-1043)
********
When the binlogd host authorization (/etc/binlog.auth) file content
exceeds 513 characters, the binlogd daemon can potentially core dump 
or hostnames corruption would occur in binlog.auth.  The result is 
either binlogd would core dump, or binlog events being forwarded from 
remote hosts would be rejected even though its hostname has been included 
into the authorization file.