PROBLEM:  (CLD: UVO106533, QAR: 72124)    (Patch ID: OSF440-102)
********

The strftime() function in libc was not compliant with the latest
UNIX95 corrigenda, dated 12 Mar 1999, concerning the %V format
specifier.  The previous description for this specifier was as
follows:

> %V is replaced by the week number of the year (Monday as the first
> day of the week) as a decimal number [01,53]. If the week containing
> 1 January has four or more days in the new year, then it is
> considered week 1. Otherwise, it is week 53 of the previous year,
> and the next week is week 1.

The new wording per the approved corrigenda is:

> %V is replaced by the week number of the year (Monday as the first
> day of the week) as a decimal number [01,53]. If the week containing
> 1 January has four or more days in the new year, then it is
> considered week 1. Otherwise, it is the last week of the previous
> year, and the next week is week 1.

The difference is in the last sentence.  The last week of the previous
year can be 52 or 53, depending on how many weeks are in the previous
year.  The previous code complied with the original published UNIX95
spec and returned the value 53 in this case.  However, the approved
corrigenda referenced above takes precedence and this patch implements
that change as required for releases branded for UNIX95.

PROBLEM:  (QAR 62835, QAR 70582)    (Patch ID: OSF440-151)
********

This patch fixes a problem of password error messages not being
displayed during installation of the security subsystem.

If a root password is not entered at the installation interface, then
it will be requested during the configuration phase. However, if the
user enters an unacceptable password the message explaining why the
password was not accepted is not displayed. Instead the message is
stored until the user enters a good password and then all of the
messages are displayed. 

PROBLEM:  (CLD MG0103887)    (Patch ID: OSF440-035)
********
The routines wprintf(), swprintf() and fwprintf() incorrectly handle the
'S' format. When printing, they count the number of bytes inthe same way
that printf() sprintf() and fprintf() do.  The standard indicates that the
wide char routines must count by logical characters.

After the patch is applies, the three routines will correctly calculate
and print the correct number of logical characters in all locales.

PROBLEM:  (MGO103748/QAR 67141)    (Patch ID: OSF440-093)
********
This patch fixes problems with rsh(1), rlogin(1), rcp(1) if netgroup names
are defined with capital letters.

PROBLEM:  (HPAQ50LK2/QAR 52404)    (Patch ID: OSF440-098)
********
This patch fixes a problem with portmap by allowing RPC select() timeouts
to occur when interrupted by signals.

PROBLEM: (QAR 64443, QAR 64472, QAR 64473, QAR 67374) (Patch ID: OSF440-115)
********

This patch fixes and enhances the quotacheck and fsck commands.

1) Add a -t option on quotacheck so that either AdvFS or UFS type devices may
   be selected for -a processing.

2) fsck and quotacheck will no longer try to attempt parallel processing of
   partitions on the same device or filesets in the same domain.

3) unique pass numbers are now being processed in numerical order during
  separate passes. This applies to both fsck and quotacheck

4) If an explicit AdvFS fileset is specified (without -a option) now always
   perform the quota check even if there is no /etc/fstab entry with
   quotauser and/or quotagroup specified.

5) Skip any file systems which are not currently mounted on their mount
   points.

6) Skip any /etc/fstab specified file system which are not mounted on their
   specified mount point.

7) A quotacheck command line can not have more than 64 arguments, if it does
   an error will be generated.

PROBLEM:  (QAR 68625)    (Patch ID: OSF440-094)
********

UFS file systems being checked by fsck may have conditions
that cause a dirscan() to end in a segmentation fault. This
patch adds a check to dirscan() that will return STOP if this
condition exists.This return will be detected by fsck and
the user will be queried for action to be taken.

PROBLEM:  (QARS 71007, 73965)
********

This patch fixes a problem in which `ufs_fsck` can get blocked while
attempting to flush nfs buffers for a service that has become suspended.

PROBLEM:  (CLD ZUO101615, QAR 71587)    (Patch ID: OSF440-223)
********

This patch fixes a problem that was causing the csh globbing function to
be extremely slow when accessing file information on NFS, AFS, or VMS file
systems.

PROBLEM:  (62211) (PATCH ID: OSF440-357)
********


This fix increases the length of the user names for rsh and rexec to allow for
NT interoperabilty.

PROBLEM:  (TKTR30011, 78909) (PATCH ID: OSF440-388)
********


If a code segment contained a gmtime() call between calls to tzset(),
or any function specified to call tzset() (such as localtime(), mktime(),
strftime(), etc) , the tzname[0] array could contain erroneous time
zone data referring to the "GMT" zone abbreviation instead of the local
time zone, as specified in the TZ environment variable or default time
zone for the system.


PROBLEM:  (QAR 69251)    (Patch ID: OSF440-054)
********
In the latest development version (version 52), Ladebug has has begun to
employ a "user thread hold" mechanism.  The initial testing of this mechanism
has revealed bugs in DECthreads code bases which might result in missed
breakpoints and watchpoints, as well as causing application hangs.

PROBLEM:  (CLD HPAQ21HQ9)    (Patch ID: OSF440-054)
********
Customer was encountering an invalid scheduling priority bugcheck, which
appears to be caused by incorrect referencing of scheduling data structures
inside DECthreads.

PROBLEM:  (QAR 69364)    (Patch ID: OSF440-054)
********
The manager thread is being scheduled to run in response to a system event
(nxm action, timer queue expiration, etc) but is not recognizing the event
as the reason it was scheduled to run.
  
The manager thread then goes back to sleep, only to wake up again in response
to the still unserviced system event.  An infinite loop results.

PROBLEM:  (QAR 70833)    (Patch ID: OSF440-111)
********
DECthreads turns synchronous signals into exceptions for processing
by the application program with TRY...ENTRY blocks.  If no application
TRY block exists, processing defaults to the DECthreads internal routine,
excLastChance.  Prior to this patch, excLastChance would only reset the
handler for the signal if the handler was the DECthreads-installed
sigRaiseException routine. Any application-installed handlers remained.
This caused a problem for applications whose signal handlers attempt to
pass control to previously installed signal handlers, because if the
previously installed handler was sigRaiseException, an infinite loop would
result.

PROBLEM:  (QARs 71019, 71358)    (Patch ID: OSF440-111)
********
A bug in the DECthreads two-level scheduler was causing Virtual Processors
(VPs) to go idle and never be scheduled to run.  This resulted in one or more
CPUs on SMP machines going unused by threaded applications.

PROBLEM:  (72100, 74961, 75971) (PATCH ID:)
********

Threaded applications which make extensive use of synchronization objects
(mutexes, condition variables) may encounter performance and scaling
regressions when run on an EV6 SMP machine.  Customers encountering these
regressions may observe negative scaling, decreased application throughput
and increased CPU utilitzation, as the number of EV6 CPUs is increased.
This version of DECthreads contains changes to the implementation of
synchronization objects and thread scheduling around those objects to
improve performance on EV6 SMP.  No functional or interface changes were
made.
PROBLEM: (79876) (PATCH ID: OSF440-431)
********
If the "where" or "t" ladebug command does not show all the currently active
functions, it may be because of this problem. The program being debugged had
to have been built with "split procedures", which is done via options in the
om and spike tools. For spike, split procedures are generated if profiling is
specified. For om, split procedures are generated if profiling AND the
-split_procedure option are specified.


PROBLEM: (79556) (PATCH ID: OSF440-423)
********
This patch adds functionality to termminate the resulting string from calls
to swprintf().


PROBLEM: (BCSM807S5) (PATCH ID: OSF440-479)
********
Some applications assume that initial allocations of memory from the C
run-time library's malloc() function will return zero-filled memory. The
problem is that malloc() and free() often write into the first 16 bytes of
the allocated memory.
This change to malloc() zeros out the first 16 bytes in the allocated memory.
The result is that memory allocated prior to any call to free() -- and prior
to any other run-time library function that might call free -- should be zero
filled.