Chapter4 Documentation Issues

This chapter describes known documentation problems.

Document Affected: Sunscreen 3.2 Configuration Examples Manual

In the chapter, Using High Availability (HA), sections 1b and 4b, on pages 72 and 73, should read as follows:

Section 1b:

If it does not already exist, configure the HA heartbeat interface.

For bos-screen1 in this example, use the following command:
# echo "10.0.4.1" > /etc/hostname.hme3
Section 4b:

If it does not already exist, configure the HA heartbeat interface.

For bos-screen2 in this example, use the following command:
# echo "10.0.4.2" > /etc/hostname.hme3

Document Affected: System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)

The documentation issues in this section apply to different locations in the System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

The Name Service Switch (Overview)

At the end of the section, The Switch File and Password Information, the following text should be added:

Avoid maintaining multiple repositories for the same user. By maintaining centralized password management in a single repository for each user, you reduce the possibilities of confusion and error. If you choose to maintain multiple repositories per user, update password information by using the passwd -r command.

passwd -r repository

If no repository is specified with the -r option, passwd updates the list of repositories in nsswitch.conf in reverse order.

LDAP Naming Services Setup and Administration

In the LDAP Naming Services Setup and Administration section, references to the use of the ldapclient command options are incorrect. For all Solaris 9 releases, the command syntax should be changed to the following:

Incorrect Reference	Correct Reference
`ldapclient` `-l`	`ldapclient list`
`ldapclient` `-p`	`ldapclient init` [`-a` `attribute name`]
`ldapclient` `-m`	`ldapclient mod`

For more information, see the ldapclient(1M) man page.

Transitioning from NIS to LDAP (Overview/Tasks)

In the chapter Transitioning from NIS to LDAP (Overview/Tasks), Table 19-2 N2L Commands and Files should include the following additional information.

Table 41 Table 192 N2L Commands and Files


Command or File	Description
ageing.byname	A mapping used by yppasswdd to read and write password aging information to the DIT when the NIS-to-LDAP transition is implemented.

Network Information Service (NIS) (Overview)

In the chapter Network Information Service (NIS) (Overview), Table 7-3 NIS Map Descriptions should include the following additional NIS maps.

Table 42 Table 73 NIS Map Descriptions


Map Name	Corresponding NIS Admin File	Description
auth.attr	auth.attr	Authorization names and descriptions
exec.attr	exec.attr	Profile execution attributes
prof.attr	prof.attr	Attributes for execution profiles
user.attr	user.attr	Extended attributes for users and roles
audit.user	audit.user	User auditing preselection data

Document Affected: Administering DHCP (Task) in System Administration Guide: IP Services

The section, Creating DHCP Options and Macros for Solaris Installation Parameters, should include the following information about DHCP Vendor Options Size Limitations:

Note that the sum total of the values assigned to all the options in a macro must not exceed 255 bytes, including the option codes and length information. This limit is dictated by the DHCP protocol.

Generally, you should pass the minimum amount of vendor information needed. You should use short path names in options that require path names. If you create symbolic links to long paths, you can pass the shorter link names.

Document Affected: Using the CIM Object Manager in Solaris WBEM Developer's Guide

Several patches require that the CIM Object Manager be started manually, after the patches have been applied. The following is a list of those patches:

SPARC	x86
11294308	11419204
11450303	11450403
11294520	11419313
11471102	11471202

To restart the CIM Object Manager, follow these steps:

# /etc/init.d/init.wbem stop

# /etc/init.d/init.wbem start

For more information about stopping and restarting the CIM Object Manager, see Stopping and Restarting the CIM Object Manager, in the Solaris WBEM Developer's Guide.