Documentation Corrections

Example 5 in the EXAMPLES section of the dsfmgr(8) reference page contains a syntax error in step b) and several typographical errors. The example should read as follows:

  5. The following steps show how to restore previous device special 
     file names after a configuration change. This example assumes 
     that you know the previous device names and hardware IDs (HWID).
   
     a. Assuming that the former device name was dsk0, and the new 
        device name is dsk5, use the /sbin/hwmgr command to delete 
        the old database entries for each device. Specify the former 
        HWID for a device as shown in the following example:
  
        # /sbin/hwmgr delete component -id 25 
  
      b. After the component is removed, you can delete the kernel's 
         record of its device special files as follows: 
  
         # /sbin/dsfmgr -R hwid 25 
         -dsk0a -dsk0b -dsk0c -dsk0d ... dsk0h 
  
      c. You can now move the existing device special files to their 
         new locations as follows: 
  
         # /sbin/dsfmgr -m dsk5 dsk0 

In the getrlimit(2) reference page, the description of the RLIMIT_DATA parameter incorrectly references the mmap() function. The correct text should read as follows:

RLIMIT_DATA
The maximum size, in bytes, of a process's data segment. Exceeding 
this limit causes the brk(), malloc(), and sbrk() functions to fail 
with errno set to [ENOMEM].

The gethostbyaddr(3) and gethostbyname(3) reference pages displayed on systems running Version 5.1B-1 (Patch Kit 3) or higher contain outdated information. The description for these functions should read, in part, as follows:

For systems not running Version 5.1B-1 or higher, the switches in the /etc/svc.conf are used.

The synopsis of the fread(3) reference page incorrectly indicates that the size and num_items parameters are pointers. The following synopsis shows the correct syntax:

size_t fread(
           void *pointer,
           size_t size,
           size_t num_items,
           FILE *stream );
 
   size_t fread_unlocked(
           void *pointer,
           size_t size,
           size_t num_items,
           FILE *stream );
 
   size_t fwrite(
           const void *pointer,
           size_t size,
           size_t num_items,
           FILE *stream );
 
   size_t fwrite_unlocked(
           const void *pointer,
           size_t size,
           size_t num_items,
           FILE *stream );

The sms.sme(4) reference page description says that the base.sme and clu.sme files should be edited. In fact, you should not edit any .sme file.

The vdump and vrestore commands were tuned to disallow block sizes greater than 64 KB blocks. Therefore the description of the -b option in the vdump(8) reference page should say “Specifies the number of 1024-byte blocks per record in the saveset. The valid range is 2 through 64 blocks; the default is 60 blocks per record.”

The first example in the examples section of the logger(1) reference page should included quotation marks around the argument as follows:

% logger -i "System rebooted"

The synopsis section of the class_disable(3) reference page contains an error. The section should read as follows:

SYNOPSIS  

     #include <apar_types.h>
     #include <sys/class.h>

     class_disable(    
             class_apar_handle_t handle );

The clu_get_info(3) reference page contains two errors in the Examples section under CLU_INF_MY_ID, where a zero (0) appears instead of a closing quotation mark. The correct text should read as follows:

switch (retval) {
	   case 0: break;
	   case CLU_NOT_MEMBER:
	   case CLU_NO_CLUSTER_NAME:
	   case CLU_NO_MEMBERID:
	   case CLU_CNX_ERROR:
	     fprintf(stderr, "clu_get_info error");
     exit(1);
	   default:
	     exit(1);
	   }

and

for (i = 0; i <= clugenptr->clu_num_of_members -1; i++) {
	   /* print or use the returned info; for example: */
	   printf("member hostname is %s", clugenptr->memblist[i].hostname);
	   }

The fopen(3) reference page states the following about the fopen() function:

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).

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:

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.

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)

In the ksh(1) reference page, the following statements are incorrect:

The correct statements are:

The ypset(8) reference page indicates that both V1 and V2 are allowed as options. This is incorrect. V2 is not a supported option.

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.

The following definition of the output from the disklabel command is missing from some versions of the disklabel(8) reference page:

An asterisk (*) is sometimes shown in the output from the disklabel command, under the column headed cylinders grouped for a partition (cpg).

This asterisk indicates that the start or the end of a cylinder does not fall exactly on a block boundary.

Since the release of Tru64 UNIX Version 5.0, the command /usr/bin/X11/dxshutdown is a wrapper shell script that runs the SysMan shutdown program. Prior to Version 5.0, dxshutdown was an X motif application. The X motif version of dxshutdown is shipped in an obsolete subset. The new dxshutdown shell script can run the old version when it is installed as /usr/bin/X11/dxshutdown_old. Use the following command:

# /usr/bin/X11/dxshutdown -old

The current OPTIONS section of the reference page is no longer applicable because suitlets use Tk and Tk uses X, not Xt. The only useful argument is focus hostname when running on a cluster.

The SysMan application is no longer called Shutdown Manager. If invoked from the SysMan menu, the leaf is labelled "Shutdown the system" and the application is labelled "Shutdown targeted on <hostname>".

In the EXAMPLES section, the /usr/dt/appconfig/help/C/DXshutdown.sdl help file is no longer used. In the FILES section, /usr/dt/appconfig/help/C/Dxshutdown.sdl and $HOME/Dxshutdown are no longer used.

The emx(7) reference page provides an example of how to turn off I/O limiting by using the following run-time configuration command:

# /sbin/sysconfig -r io NPort_Max_IOs = 0xFFFFFFFF

This example command should read as follows:

# /sbin/sysconfig -r emx NPort_Max_IOs=0xFFFFFFFF

Note 1 in the dd(1) reference page provides an example of zeroing a disk label. The syntax of the disklabel command used in that example is incorrect and should read as follows:

# disklabel -r /dev/rdisk/dsk1a
# disklabel -z  /dev/rdisk/dsk1a
# disklabel: Disk /dev/rdisk/dsk1a is unlabeled

The following information was omitted from the EvmEvent(5) reference page.

Reserved Component Names

The convention of reserved component names makes it possible to select related events, regardless of which subsystem or application posts them. See the Programmer's Guide for a description of reserved component names. The following table lists the reserved component names used by EVM:

The following notes apply to the sysman_menu(8) reference page:

Table 5.1 of the System Configuration and Tuning guide lists two tools to aid in detecting poor NFS performance that should have been removed from the table. Attempting to use these tools causes no harm, but does result in error messages being generated. Those tools and the error messages they generate are as follows:

(dbx) p nfs_sv_active_hist
"nfs_sv_active_hist" is not defined or not active

(dbx) p nchstats
can't evaluate a Block

The second paragraph of Section 1.1.2 of the Logical Storage Manager manual (September 2002 version), incorrectly states that the default private region size guarantees space for a configuration database that tracks 8192 objects (LSM disks, subdisks, plexes, and volumes). The statement assumes that the private region contains only the configuration database and does not account for the kernel change log and other LSM metadata.

To determine the size of the configuration database it is necessary to issue the voldg list diskgroupname command. For example:

# voldg list rootdg
Group:     rootdg
dgid:      1105649937.1026.hero
import-id: 0.1
flags:
copies:    nconfig=default nlog=default
config:    seqno=0.1171 permlen=2993 free=2987 templen=4 loglen=453
config disk dsk2 copy 1 len=2993 state=clean online
config disk dsk3 copy 1 len=2993 state=clean online
log disk dsk2 copy 1 len=453
log disk dsk3 copy 1 len=453

The output from this example shows that the configuration database length is 2993. The private region size for the disks in this example is the default size of 4096.

In Section 6.4.3 of the Logical Storage Manager manual — Recovering From Temporary Disk Failures — there is an extra step required before recovering the volumes. You must readd the failed disks to the affected disk group(s), using the option to restore the last-known disk media names.

The complete process to recover from temporary disk failures includes the following steps:

In Section 2.3.4.3 of the AdvFS Administration manual — Increasing Storage in Domains by Extending an Existing Volume — there is an extra step required when the underlying storage volume is a hardware RAID device. You must modify the volume's disk label information to reflect the new, increased size of the partition supporting the domain, and then apply the updated disk label to the volume before extending the file system.

The complete process to extend a domain by increasing the size of an underlying hardware RAID volume includes the following steps:

Section 4.2 provides an example demonstrating how to enable access to the system's real time clock. This example is incorrect. The correct command is:

# mknod /dev/timedev c 15 0

Section 4.4.8.4 states: The max_async_req attribute specifies the maximum number of sessions within any given RDG context table. The recommended value is at least the number of Oracle processes plus two. This is incorrect. The max_sessions specifies the maximum number of sessions within any given RDG context table.

Section 4.4.8.5 states that the max_async_req attribute specifies the maximum number of pages automatically wired in memory for message packets. This is incorrect. The rdg_max_auto_msg_wires attribute specifies the maximum number of pages automatically wired in memory for message packets. We recommend setting this attribute to 0.

In Section 6.2.2.2, it states that if you increase the value of the max_proc_per_user attribute, you increase the amount of wired memory.

This statement is false. Increasing this attribute value does not increase the amount of wired memory.

The Installation Guide states that Version 1.3.1-1 of Java™ is provided with Version 5.1B of the operating system. This is incorrect. Java Version 1.3.1-2 is provided with this release of the operating system.

In Section 7.4 of the Installation Guide — Advanced Topics, the second bullet explains that software patches are not cloned. There are typographical errors in the procedure to use if your model system has already been patched; the -f option is incorrect and should be -force. The following is the corrected text:

The Tru64 UNIX Version 5.1B Release Notes incorrectly announced the retirement of the HSZ70 storage array controller in conjunction with the release of Version 5.1B of the Tru64 UNIX operating system.

The HSZ70 is supported with Version 5.1B. The controller driver software is included on the kit, and the Version 5.1B documentation includes troubleshooting information for the HSZ70.

DEC Ada was retired in March, 2000. The Tru64 UNIX Version 5.1B Release Notes incorrectly states that DEC Ada (UPI - 0HM) and DEC Ada PDO (UPI - 0VS) will be retired in a future release of the operating system.

The README file included with the Motif 2.1 package inaccurately states that input methods that “currently work will not work with Motif 2.1.” In fact, input methods will work in most cases. When Motif 2.1 is installed, the README file is available at /usr/opt/motif2.1/READM.

Protecting Your System Against File Name Spoofing Attacks is an engineering practices document that describes how to address the problem of name space collisions (spoofing, or symlink attacks) by using system administration tools and safe coding practices in local scripts and programs.

The engineering practices described in the document focus on writing safe, privileged code and scripts. In particular, the document addresses the use of temporary files, which is a commonly exploited vulnerability. This document is available on the Tru64 UNIX Documentation Web page: http://www.tru64unix.compaq.com/docs/wpapers/spoof_wp/TITLE.HTM

The OpenLDAP Directory Server Installation and Administration guide is now available on the Tru64 UNIX Documentation Web page: http://www.tru64unix.compaq.com/docs/pub_page/V51B_DOCS/V51B_DOCLIST.HTM

This guide describes how to install and configure the Lightweight Directory Access Protocol (LDAP) Directory Server in a Tru64 UNIX environment.