HP Tru64 UNIX Technical Updates for the Version 5.1B and Higher Operating System and Patches (February 2010)

This statement is true only for local file systems such as UFS or AdvFS. However, data corruption
can occur when separate processes use fopen to access file systems that are NFS-mounted (or
through any other form of remote mount).
Stype Parameter Not Documented in ddr_config(8) (Oct. 2006)
The ddr_config Stype parameter is not documented in the help text (using ddr_config h)
or in the ddr_config(8) reference page.
When using the ddr_config s command to get information from the ddr database for Fibre
Channel devices, you can optionally specify a value identifying the Stype in one of the following
ways:
# ddr_config -s disk EMC SYMMETRIX "" 2
or
# ddr_config -s disk DEC HSG80 "" 2
In these examples, the "" parameter is the revision and the 2 parameter is the Stype.
There are two Stype values in use in ddr.dbase:
An Stype value of 1 identifies IDE/ATAPI devices
An Stype value of 2 identifies Fiber Channel devices
If you do not specify an Stype value, the entry will be used for all sim types.
The Stype value is also relevant when using the S option to display the DDR entry that will be
used for a particular device. Without this value, the S option will show just the default entry,
and not the sim-specific entry.
Correction to cfg_psm_memops(3) and cfg_psm_catops(3) (Oct. 2006)
The cfg_psm_memops(3) and cfg_psm_catops(3)(3) reference pages contain a pointer to PSM(4).
The pointer should be to psm.h(4)
ksh(1) Correction (June 2003)
In the ksh(1) reference page, the following statements are incorrect:
&& Causes the list following it to be executed only if the preceding pipeline returns a 0 (zero)
exit value.
|| Causes the list following it to be executed only if the preceding pipeline returns a nonzero
exit value.
The correct statements are:
&& Causes the list following it to be executed only if the preceding pipeline returns a nonzero
exit value.
|| Causes the list following it to be executed only if the preceding pipeline returns a 0 (zero) exit
value.
ypset(8) Correction (Feb. 2003)
The ypset(8) reference page indicates that both V1 and V2 are allowed as options. This is incorrect.
V2 is not a supported option.
aio_return(3) Correction (Feb. 2003)
The following information should be appended to the RETURN VALUES section of the
aio_return(3) reference page:
On an unsuccessful call, the value of -1 is returned and errno is set to indicate the error. If the
operation did not complete, but it terminated normally (because, for example, the call was
purposely interrupted by the aio_cancel function), errno is set to 0.
Documentation Corrections 41