diff options
Diffstat (limited to 'usr/src/man/man5')
159 files changed, 742 insertions, 742 deletions
diff --git a/usr/src/man/man5/NISLDAPmapping.5 b/usr/src/man/man5/NISLDAPmapping.5 index 52ee0fb24d..d4c4317701 100644 --- a/usr/src/man/man5/NISLDAPmapping.5 +++ b/usr/src/man/man5/NISLDAPmapping.5 @@ -17,10 +17,10 @@ equivalent Directory Information Tree (DIT) entries. .sp .LP The presence of \fB/var/yp/NISLDAPmapping\fR on a NIS master server causes that -server to obtain NIS data from LDAP. See \fBypserv\fR(4). If +server to obtain NIS data from LDAP. See \fBypserv\fR(5). If \fB/var/yp/NISLDAPmapping\fR is present but the connection configuration file that is defined in \fB/etc/default/ypserv\fR cannot be found, a warning is -logged. See \fBypserv\fR(1M). +logged. See \fBypserv\fR(8). .sp .LP NIS slave servers always obtain their data from a NIS master server, whether or @@ -28,7 +28,7 @@ not that server is getting data from LDAP, and ignore the \fB/var/yp/NISLDAPmapping\fR file. .sp .LP -A simple \fBNISLDAPmapping\fR file is created using \fBinityp2l\fR(1M). You can +A simple \fBNISLDAPmapping\fR file is created using \fBinityp2l\fR(8). You can customize your \fBNISLDAPmapping\fR file as you require. .sp .LP @@ -644,7 +644,7 @@ nisLDAPcommentChar mapname : '' .RS 4n Indicates if \fBYP_INTERDOMAIN\fR or \fBYP_SECURE\fR entries should be created in a map. Using \fBnisLDAPmapFlags\fR is equivalent to running -\fBmakedbm\fR(1M) with the \fB-b\fR or the \fB-s\fR option. When a map is +\fBmakedbm\fR(8) with the \fB-b\fR or the \fB-s\fR option. When a map is created from the contents of the DIT, the mapping file attribute is the only source for the \fBYP_INTERDOMAIN\fR or \fBYP_SECURE\fR entries. .sp @@ -1469,7 +1469,7 @@ Mapping file used by the NIS server components .RE .SH ATTRIBUTES -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -1483,9 +1483,9 @@ Interface Stability Obsolete .TE .SH SEE ALSO -\fBinityp2l\fR(1M), \fBmakedbm\fR(1M), \fBypserv\fR(1M), +\fBinityp2l\fR(8), \fBmakedbm\fR(8), \fBypserv\fR(8), \fBber_printf\fR(3LDAP), \fBsprintf\fR(3C), \fBsscanf\fR(3C), -\fBypserv\fR(4), \fBattributes\fR(5) +\fBypserv\fR(5), \fBattributes\fR(7) .sp .LP \fISystem Administration Guide: Naming and Directory Services (DNS, NIS, and diff --git a/usr/src/man/man5/admin.5 b/usr/src/man/man5/admin.5 index 08b899cae1..0593ab4d17 100644 --- a/usr/src/man/man5/admin.5 +++ b/usr/src/man/man5/admin.5 @@ -19,7 +19,7 @@ being installed already exists on the system. with this release. The default file is not writable, so to assign values different from this file, create a new \fBadmin\fR file. There are no naming restrictions for \fBadmin\fR files. Name the file when installing a package -with the \fB-a\fR option of \fBpkgadd\fR(1M). If the \fB-a\fR option is not +with the \fB-a\fR option of \fBpkgadd\fR(8). If the \fB-a\fR option is not used, the default \fBadmin\fR file is used. .sp .LP @@ -32,7 +32,7 @@ parameter in the following form: .LP All of the parameters listed below can be defined in an \fBadmin\fR file, but it is not required to assign values to all of these. If a value is not -assigned, \fBpkgadd\fR(1M) asks the installer how to proceed. +assigned, \fBpkgadd\fR(8) asks the installer how to proceed. .sp .LP The valid parameters and their possible values are shown below except as noted. @@ -52,7 +52,7 @@ there is no \fBbasedir\fR entry in the file, the installer will be prompted for a path name, as if the file contained the entry \fBbasedir=ask\fR. This parameter can also be set to \fBdefault\fR (entry is \fBbasedir=default\fR). In this instance, the package is installed into the base directory specified by -the \fBBASEDIR\fR parameter in the \fBpkginfo\fR(4) file. +the \fBBASEDIR\fR parameter in the \fBpkginfo\fR(5) file. .RE .sp @@ -360,7 +360,7 @@ Abort installation if space requirements are not met. .ad .RS 30n Determines the user that will run request scripts. This parameter can have -either of the values described below. See \fBpkgadd\fR(1M) for details on the +either of the values described below. See \fBpkgadd\fR(8) for details on the conditions under which this parameter is useful. .sp .ne 2 @@ -370,7 +370,7 @@ conditions under which this parameter is useful. .RS 12n Run request script as user \fBinstall\fR, if such a user exists, with the privileges of that user. Otherwise, run script as user \fBroot\fR, with UID -equal to 0 and with all/zone privileges. (See \fBzones\fR(5).) +equal to 0 and with all/zone privileges. (See \fBzones\fR(7).) .RE .sp @@ -457,7 +457,7 @@ default \fBadmin\fR file .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -472,7 +472,7 @@ Interface Stability Evolving .SH SEE ALSO .LP -\fBpkgadd\fR(1M), \fBpkginfo\fR(4), \fBattributes\fR(5), \fBzones\fR(5) +\fBpkgadd\fR(8), \fBpkginfo\fR(5), \fBattributes\fR(7), \fBzones\fR(7) .SH NOTES .LP The value \fBask\fR should not be defined in an \fBadmin\fR file that will be diff --git a/usr/src/man/man5/alias.5 b/usr/src/man/man5/alias.5 index 82a63bf31e..e9b4a68a44 100644 --- a/usr/src/man/man5/alias.5 +++ b/usr/src/man/man5/alias.5 @@ -33,7 +33,7 @@ beginning with '#' is treated as a comment. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -50,4 +50,4 @@ Interface Stability Evolving .sp .LP \fBiconv\fR(3C), \fBiconv_close\fR(3C), \fBiconv_open\fR(3C), -\fBattributes\fR(5) +\fBattributes\fR(7) diff --git a/usr/src/man/man5/aliases.5 b/usr/src/man/man5/aliases.5 index 7c7cd25d38..02e01adb78 100644 --- a/usr/src/man/man5/aliases.5 +++ b/usr/src/man/man5/aliases.5 @@ -34,7 +34,7 @@ aliases, addresses, forward \- addresses and aliases for sendmail .SH DESCRIPTION .LP -These files contain mail addresses or aliases, recognized by \fBsendmail\fR(1M) +These files contain mail addresses or aliases, recognized by \fBsendmail\fR(8) for the local host: .sp .ne 2 @@ -65,7 +65,7 @@ add, update, or delete local mail aliases. .sp .6 .RS 4n The aliasing information from \fB/etc/mail/aliases\fR, in binary \fBndbm\fR(3C) -format for use by \fBsendmail\fR(1M). The program \fBnewaliases\fR(1M) +format for use by \fBsendmail\fR(8). The program \fBnewaliases\fR(8) maintains these files. .RE @@ -77,13 +77,13 @@ maintains these files. .sp .6 .RS 4n The aliasing information from \fB/etc/mail/aliases\fR, in binary, Berkeley -DataBase format for use by \fBsendmail\fR(1M). The program maintains these +DataBase format for use by \fBsendmail\fR(8). The program maintains these files. .sp Depending on the configuration of the AliasFile option in \fB/etc/mail/sendmail.cf\fR, either the single file \fBaliases.db\fR or the -pair of files \fBaliases.\fR{dir, pag} is generated by \fBnewaliases\fR(1M). As -shipped with Solaris, \fBsendmail\fR(1M) supports both formats. If neither is +pair of files \fBaliases.\fR{dir, pag} is generated by \fBnewaliases\fR(8). As +shipped with Solaris, \fBsendmail\fR(8) supports both formats. If neither is specified, the Berkeley DataBase format which generates the single \fB\&.db\fR file is used. .RE @@ -105,7 +105,7 @@ contains addresses and aliases available for use across the network. .SS "Addresses" .LP -As distributed, \fBsendmail\fR(1M) supports the following types of addresses: +As distributed, \fBsendmail\fR(8) supports the following types of addresses: .SS "Local Usernames" .in +2 .nf @@ -137,7 +137,7 @@ that file. .sp .LP If the first character of the address is a vertical bar (\fB\||\|\fR), -\fBsendmail\fR(1M) pipes the message to the standard input of the \fBcommand\fR +\fBsendmail\fR(8) pipes the message to the standard input of the \fBcommand\fR the bar precedes. .SS "Internet-standard Addresses" .in +2 @@ -181,7 +181,7 @@ remote copying of files. .sp .LP Other site-specific forms of addressing can be added by customizing the -\fBsendmail.cf\fR configuration file. See \fBsendmail\fR(1M) for details. +\fBsendmail.cf\fR configuration file. See \fBsendmail\fR(8) for details. Standard addresses are recommended. .SS "Aliases" .SS "Local Aliases" @@ -199,7 +199,7 @@ Standard addresses are recommended. \fIaliasname\fR is the name of the alias or alias group, and \fIaddress\fR is the address of a recipient in the group. Aliases can be nested. That is, an \fIaddress\fR can be the name of another alias group. Because of the way -\fBsendmail\fR(1M) performs mapping from upper-case to lower-case, an +\fBsendmail\fR(8) performs mapping from upper-case to lower-case, an \fIaddress\fR that is the name of another alias group must not contain any upper-case letters. .sp @@ -287,7 +287,7 @@ name of the \fBNIS\fR domain is \fBpodunk-u\fR. .SS "Automatic Forwarding" .LP When an alias (or address) is resolved to the name of a user on the local host, -\fBsendmail\fR(1M) checks for a ~/.forward file, owned by the intended +\fBsendmail\fR(8) checks for a ~/.forward file, owned by the intended recipient, in that user's home directory, and with universal read access. This file can contain one or more addresses or aliases as described above, each of which is sent a copy of the user's mail. @@ -320,14 +320,14 @@ the \fBvacation\fR program. The \fB~/.forward\fR file can be used to specify special "per user" extensions by creating a \fB\&.forward+extension\fR file in the home directory. For example, with an address like \fBjsmith+jerry@jsmachine\fR, the -\fBsendmail\fR(1M) utility recognizes everything before the "\fB+\fR" as the +\fBsendmail\fR(8) utility recognizes everything before the "\fB+\fR" as the actual username (\fBjsmith\fR) and everything after it, up to the "\fB@\fR" symbol, as the extension (\fBjerry\fR) which is passed to the mail delivery agent for local use. .sp .LP The default value of the \fBForwardPath\fR processing option in -\fBsendmail\fR(1M) is: +\fBsendmail\fR(8) is: .sp .in +2 .nf @@ -341,7 +341,7 @@ O ForwardPath=$z/.forward.$w+$h:$z/.forward+$h:$z/.forward.$w:$z \e where \fB$z\fR is the macro for the user's home directory, \fB$w\fR is the macro for the local machine name and \fB$h\fR is the extension. For example, for mail using the address, \fBjsmith+jerry@jsmachine\fR, the -\fBsendmail\fR(1M) utility checks each of the four following file names, in the +\fBsendmail\fR(8) utility checks each of the four following file names, in the order given, to see if it exists and if it has "safe" permissions, that is, that neither the file nor any of its parent directories are group- or world-writable: @@ -434,9 +434,9 @@ Forwarding information file .SH SEE ALSO .LP -\fBpasswd\fR(1), \fBuucp\fR(1C), \fBvacation\fR(1), \fBnewaliases\fR(1M), -\fBsendmail\fR(1M), \fBndbm\fR(3C), \fBgetusershell\fR(3C), \fBpasswd\fR(4), -\fBshells\fR(4), \fBattributes\fR(5) +\fBpasswd\fR(1), \fBuucp\fR(1C), \fBvacation\fR(1), \fBnewaliases\fR(8), +\fBsendmail\fR(8), \fBndbm\fR(3C), \fBgetusershell\fR(3C), \fBpasswd\fR(5), +\fBshells\fR(5), \fBattributes\fR(7) .SH NOTES .LP Because of restrictions in \fBndbm\fR(3C), a single alias cannot contain more diff --git a/usr/src/man/man5/au.5 b/usr/src/man/man5/au.5 index 71b7e691de..58c9dde9d0 100644 --- a/usr/src/man/man5/au.5 +++ b/usr/src/man/man5/au.5 @@ -188,7 +188,7 @@ void main(void) .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -204,7 +204,7 @@ Stability Level Evolving .SH SEE ALSO .sp .LP -\fBattributes\fR(5) +\fBattributes\fR(7) .SH NOTES .sp .LP diff --git a/usr/src/man/man5/audit.log.5 b/usr/src/man/man5/audit.log.5 index a07e4f23f8..fe5d41afac 100644 --- a/usr/src/man/man5/audit.log.5 +++ b/usr/src/man/man5/audit.log.5 @@ -22,7 +22,7 @@ audit.log \- audit trail file .LP \fBaudit.log\fR files are the depository for audit records stored locally or on an NFS-mounted audit server. These files are kept in directories as specified -by the \fBp_dir\fR attribute of the \fBaudit_binfile\fR(5) plugin. They are +by the \fBp_dir\fR attribute of the \fBaudit_binfile\fR(7) plugin. They are named to reflect the time they are created and are, when possible, renamed to reflect the time they are closed as well. The name takes the form .sp @@ -30,7 +30,7 @@ reflect the time they are closed as well. The name takes the form \fIyyyymmddhhmmss\fR\fB\&.not_terminated.\fR\fIhostname\fR .sp .LP -when open or if \fBauditd\fR(1M) terminated ungracefully, and the form +when open or if \fBauditd\fR(8) terminated ungracefully, and the form .sp .LP \fIyyyymmddhhmmss\fR\fB\&.\fR\fIyyyymmddhhmmss\fR\fB\&.\fR\fIhostname\fR @@ -42,7 +42,7 @@ in the month, \fBhh\fR hour in the day, \fBmm\fR minute in the hour, and .sp .LP Audit data is generated in the binary format described below; the default for -audit is binary format. See \fBaudit_syslog\fR(5) for an alternate data +audit is binary format. See \fBaudit_syslog\fR(7) for an alternate data format. .sp .LP @@ -768,7 +768,7 @@ creator UID 4 bytes .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -786,9 +786,9 @@ Interface Stability See below. The binary file format is Committed. The binary file contents is Uncommitted. .SH SEE ALSO .LP -\fBaudit\fR(1M), \fBauditd\fR(1M), \fBaudit\fR(2), +\fBaudit\fR(8), \fBauditd\fR(8), \fBaudit\fR(2), \fBauditon\fR(2), \fBau_to\fR(3BSM), -\fBaudit_binfile\fR(5), \fBaudit_remote\fR(5), \fBaudit_syslog\fR(5) +\fBaudit_binfile\fR(7), \fBaudit_remote\fR(7), \fBaudit_syslog\fR(7) .SH NOTES .LP Each token is generally written using the \fBau_to\fR(3BSM) family of function diff --git a/usr/src/man/man5/audit_class.5 b/usr/src/man/man5/audit_class.5 index 781d7f546e..00bbc741e3 100644 --- a/usr/src/man/man5/audit_class.5 +++ b/usr/src/man/man5/audit_class.5 @@ -16,7 +16,7 @@ audit_class \- audit class definitions .LP \fB/etc/security/audit_class\fR is a user-configurable ASCII system file that stores class definitions used in the audit system. Audit events in -\fBaudit_event\fR(4) are mapped to one or more of the defined audit classes. +\fBaudit_event\fR(5) are mapped to one or more of the defined audit classes. \fBaudit_event\fR can be updated in conjunction with changes to \fBaudit_class\fR. Programs can use the \fBgetauclassent\fR(3BSM) routines to access audit @@ -146,7 +146,7 @@ The following is an example of an \fBaudit_class\fR file: .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -165,7 +165,7 @@ The file format stability is Committed. The file content is Uncommitted. .SH SEE ALSO .LP \fBau_preselect\fR(3BSM), \fBgetauclassent\fR(3BSM), -\fBaudit_event\fR(4), \fBattributes\fR(5) +\fBaudit_event\fR(5), \fBattributes\fR(7) .SH NOTES .LP It is possible to deliberately turn on the \fBno\fR class in the kernel, in diff --git a/usr/src/man/man5/audit_event.5 b/usr/src/man/man5/audit_event.5 index b85c1e4a04..8f0cc7e4e0 100644 --- a/usr/src/man/man5/audit_event.5 +++ b/usr/src/man/man5/audit_event.5 @@ -17,7 +17,7 @@ audit_event \- audit event definition and class mapping \fB/etc/security/audit_event\fR is a user-configurable ASCII system file that stores event definitions used in the audit system. As part of this definition, each event is mapped to one or more of the audit classes defined in -\fBaudit_class\fR(4). +\fBaudit_class\fR(5). Programs can use the \fBgetauevent\fR(3BSM) routines to access audit event information. .sp @@ -141,7 +141,7 @@ The following is an example of some \fBaudit_event\fR file entries: .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -168,4 +168,4 @@ The file format stability is Committed. The file content is Uncommitted. .SH SEE ALSO .LP -\fBgetauevent\fR(3BSM), \fBaudit_class\fR(4) +\fBgetauevent\fR(3BSM), \fBaudit_class\fR(5) diff --git a/usr/src/man/man5/auth_attr.5 b/usr/src/man/man5/auth_attr.5 index 4de72b18e0..530c05536c 100644 --- a/usr/src/man/man5/auth_attr.5 +++ b/usr/src/man/man5/auth_attr.5 @@ -21,7 +21,7 @@ Programs use the \fBgetauthattr\fR(3SECDB) routines to access this information. .sp .LP The search order for multiple authorization sources is specified in the -\fB/etc/nsswitch.conf\fR file, as described in the \fBnsswitch.conf\fR(4) man +\fB/etc/nsswitch.conf\fR file, as described in the \fBnsswitch.conf\fR(5) man page. .sp .LP @@ -208,7 +208,7 @@ With the above authorizations, the administrator can assign to others the \fBsolaris.login.enable\fR authorization. If the administrator has both the grant authorization, \fBsolaris.admin.printmgr.grant\fR, and the wildcard authorization, \fBsolaris.admin.printmgr.*\fR, the administrator can grant to -others any of the printer authorizations. See \fBuser_attr\fR(4) for more +others any of the printer authorizations. See \fBuser_attr\fR(5) for more information about how wildcards can be used to assign multiple authorizations whose names begin with the same components. @@ -254,8 +254,8 @@ auth_attr:files nis .SH SEE ALSO .LP \fBgetauthattr\fR(3SECDB), \fBgetexecattr\fR(3SECDB), -\fBgetprofattr\fR(3SECDB), \fBgetuserattr\fR(3SECDB), \fBexec_attr\fR(4), -\fBnsswitch.conf\fR(4), \fBuser_attr\fR(4) +\fBgetprofattr\fR(3SECDB), \fBgetuserattr\fR(3SECDB), \fBexec_attr\fR(5), +\fBnsswitch.conf\fR(5), \fBuser_attr\fR(5) .SH NOTES .LP Because the list of legal keys is likely to expand, any code that parses this diff --git a/usr/src/man/man5/bart_manifest.5 b/usr/src/man/man5/bart_manifest.5 index 4ec56703b0..adacef22b3 100644 --- a/usr/src/man/man5/bart_manifest.5 +++ b/usr/src/man/man5/bart_manifest.5 @@ -7,7 +7,7 @@ .SH NAME bart_manifest \- system audit manifest file .SH DESCRIPTION -The \fBbart\fR(1M) command generates a manifest that describes the contents of +The \fBbart\fR(8) command generates a manifest that describes the contents of a managed host. A manifest consists of a header and entries. Each entry represents a single file. Entries are sorted in ascending order by file name. Any nonstandard file names, such as those that contain embedded newline or tab @@ -303,4 +303,4 @@ the encoded versions of the file names to correctly handle special characters. .in -2 .SH SEE ALSO -\fBdate\fR(1), \fBbart\fR(1M), \fBbart_rules\fR(4), \fBattributes\fR(5) +\fBdate\fR(1), \fBbart\fR(8), \fBbart_rules\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man5/bart_rules.5 b/usr/src/man/man5/bart_rules.5 index aa974bcee7..542a8ba3a3 100644 --- a/usr/src/man/man5/bart_rules.5 +++ b/usr/src/man/man5/bart_rules.5 @@ -9,7 +9,7 @@ bart_rules \- bart rules file .SH DESCRIPTION .sp .LP -The \fBbart_rules\fR file is a text file that is used by the \fBbart\fR(1M) +The \fBbart_rules\fR file is a text file that is used by the \fBbart\fR(8) command. The rules file determines which files to validate and which file attributes of those files to ignore. .sp @@ -423,4 +423,4 @@ subject to the last block. .SH SEE ALSO .sp .LP -\fBbart\fR(1M), \fBbart_manifest\fR(4), \fBattributes\fR(5) +\fBbart\fR(8), \fBbart_manifest\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man5/bootparams.5 b/usr/src/man/man5/bootparams.5 index 85c49add16..b03de6b67e 100644 --- a/usr/src/man/man5/bootparams.5 +++ b/usr/src/man/man5/bootparams.5 @@ -15,9 +15,9 @@ bootparams \- boot parameter data base .SH DESCRIPTION The \fBbootparams\fR file contains a list of client entries that diskless clients use for booting. Diskless booting clients retrieve this information by -issuing requests to a server running the \fBrpc.bootparamd\fR(1M) program. The +issuing requests to a server running the \fBrpc.bootparamd\fR(8) program. The \fBbootparams\fR file may be used in conjunction with or in place of other -sources for the \fBbootparams\fR information. See \fBnsswitch.conf\fR(4). +sources for the \fBbootparams\fR information. See \fBnsswitch.conf\fR(5). .sp .LP For each client the file contains an entry with the client's name and a list of @@ -133,7 +133,7 @@ then in "wildcard" entry. If none is found, the server's domain name is used. For the JumpStart installation of machines that do not have video displays, use the \fBterm\fR keyword to identify the terminal type of the boot server. Terminal types are listed in \fB/usr/share/lib/terminfo\fR (see -\fBterminfo\fR(4)). +\fBterminfo\fR(5)). .sp .LP An entry with the \fBns\fR keyword associates a server (a name server) with, @@ -214,7 +214,7 @@ ns=otis:nisplus(255.255.255.0) term=:xterms domain=eu.cte.example.com .RE .SH SEE ALSO -\fBrpc.bootparamd\fR(1M), \fBnsswitch.conf\fR(4) +\fBrpc.bootparamd\fR(8), \fBnsswitch.conf\fR(5) .SH NOTES The \fBNIS+\fR, \fBsysidtool\fR, and jumpstart facilities are not present in illumos. They are documented here solely for users who wish to use illumos as @@ -224,4 +224,4 @@ a jumpstart server for older Solaris releases. Solaris diskless clients use the keywords \fBroot\fR and \fBrootopts\fR to look up the pathname for the root filesystem and the mount options for the root filesystem, respectively. These are the only keywords meaningful for diskless -booting clients. See \fBmount_ufs\fR(1M). +booting clients. See \fBmount_ufs\fR(8). diff --git a/usr/src/man/man5/cardbus.5 b/usr/src/man/man5/cardbus.5 index 7930f45562..e00d71fc82 100644 --- a/usr/src/man/man5/cardbus.5 +++ b/usr/src/man/man5/cardbus.5 @@ -24,7 +24,7 @@ for these devices. .LP On some occasions, drivers for CardBus devices can use driver configuration files to provide driver private properties through the global property -mechanism. See \fBdriver.conf\fR(4) for further details. Driver configuration +mechanism. See \fBdriver.conf\fR(5) for further details. Driver configuration files can also be used to augment or override properties for a specific instance of a driver. .sp @@ -211,7 +211,7 @@ has the string value \fBon\fR) and \fBhba-dma-speed\fR (which has the value .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -227,7 +227,7 @@ Architecture SPARC, x86 .SH SEE ALSO .sp .LP -\fBdriver.conf\fR(4), \fBattributes\fR(5), \fBddi_intr_add_handler\fR(9F), +\fBdriver.conf\fR(5), \fBattributes\fR(7), \fBddi_intr_add_handler\fR(9F), \fBddi_prop_lookup\fR(9F), \fBddi_regs_map_setup\fR(9F) .sp .LP diff --git a/usr/src/man/man5/compver.5 b/usr/src/man/man5/compver.5 index 24d99a24b4..9b8d8f4508 100644 --- a/usr/src/man/man5/compver.5 +++ b/usr/src/man/man5/compver.5 @@ -44,7 +44,7 @@ Version 1.0\fR .SH SEE ALSO .sp .LP -\fBpkginfo\fR(4) +\fBpkginfo\fR(5) .sp .LP \fIApplication Packaging Developer\&'s Guide\fR @@ -57,4 +57,4 @@ be considered the same. .sp .LP The entries in the \fBcompver\fR file must match the values assigned to the -\fBVERSION\fR parameter in the \fBpkginfo\fR(4) files. +\fBVERSION\fR parameter in the \fBpkginfo\fR(5) files. diff --git a/usr/src/man/man5/contents.5 b/usr/src/man/man5/contents.5 index 7a4ea3bd3f..03e881655e 100644 --- a/usr/src/man/man5/contents.5 +++ b/usr/src/man/man5/contents.5 @@ -47,7 +47,7 @@ The following is the general format of a new-style entry: .sp .LP New-style entries differ for each \fBftype\fR. The \fBftype\fR designates the -entry type, as specified in \fBpkgmap\fR(4). The format for new-style entries, +entry type, as specified in \fBpkgmap\fR(5). The format for new-style entries, for each \fBftype\fR, is as follows: .sp .in +2 @@ -117,7 +117,7 @@ The relative path to the real file or linked-to directory name. \fB\fIftype\fR\fR .ad .RS 11n -A one-character field that indicates the entry type (see \fBpkgmap\fR(4)). +A one-character field that indicates the entry type (see \fBpkgmap\fR(5)). .RE .sp @@ -126,7 +126,7 @@ A one-character field that indicates the entry type (see \fBpkgmap\fR(4)). \fB\fIclass\fR\fR .ad .RS 11n -The installation class to which the file belongs (see \fBpkgmap\fR(4)). +The installation class to which the file belongs (see \fBpkgmap\fR(5)). .RE .sp @@ -145,7 +145,7 @@ more than one package can be present. \fB\fImode\fR\fR .ad .RS 11n -The octal mode of the file (see \fBpkgmap\fR(4)). +The octal mode of the file (see \fBpkgmap\fR(5)). .RE .sp @@ -154,7 +154,7 @@ The octal mode of the file (see \fBpkgmap\fR(4)). \fB\fIowner\fR\fR .ad .RS 11n -The owner of the file (see \fBpkgmap\fR(4)). +The owner of the file (see \fBpkgmap\fR(5)). .RE .sp @@ -163,7 +163,7 @@ The owner of the file (see \fBpkgmap\fR(4)). \fB\fIgroup\fR\fR .ad .RS 11n -The group to which the file belongs (see \fBpkgmap\fR(4)). +The group to which the file belongs (see \fBpkgmap\fR(5)). .RE .sp @@ -172,7 +172,7 @@ The group to which the file belongs (see \fBpkgmap\fR(4)). \fB\fImajor\fR\fR .ad .RS 11n -The major device number (see \fBpkgmap\fR(4)). +The major device number (see \fBpkgmap\fR(5)). .RE .sp @@ -181,7 +181,7 @@ The major device number (see \fBpkgmap\fR(4)). \fB\fIminor\fR\fR .ad .RS 11n -The minor device number (see \fBpkgmap\fR(4)). +The minor device number (see \fBpkgmap\fR(5)). .RE .sp @@ -190,7 +190,7 @@ The minor device number (see \fBpkgmap\fR(4)). \fB\fIsize\fR\fR .ad .RS 11n -The actual size of the file in bytes as reported by sum (see \fBpkgmap\fR(4)). +The actual size of the file in bytes as reported by sum (see \fBpkgmap\fR(5)). .RE .sp @@ -199,7 +199,7 @@ The actual size of the file in bytes as reported by sum (see \fBpkgmap\fR(4)). \fB\fIcksum\fR\fR .ad .RS 11n -The checksum of the file contents (see \fBpkgmap\fR(4)). +The checksum of the file contents (see \fBpkgmap\fR(5)). .RE .sp @@ -208,13 +208,13 @@ The checksum of the file contents (see \fBpkgmap\fR(4)). \fB\fImodtime\fR\fR .ad .RS 11n -The time of last modification (see \fBpkgmap\fR(4)). +The time of last modification (see \fBpkgmap\fR(5)). .RE .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -230,16 +230,16 @@ Interface Stability Unstable .SH SEE ALSO .sp .LP -\fBpkgadd\fR(1M), \fBpkgadm\fR(1M), \fBpkgchk\fR(1M), \fBpkgmap\fR(4), -\fBattributes\fR(5) +\fBpkgadd\fR(8), \fBpkgadm\fR(8), \fBpkgchk\fR(8), \fBpkgmap\fR(5), +\fBattributes\fR(7) .SH NOTES .sp .LP As shown above, the interface stability of \fB/var/sadm/install/contents\fR is -Unstable (see \fBattributes\fR(5)). It is common practice to use this file in a +Unstable (see \fBattributes\fR(7)). It is common practice to use this file in a read-only manner to determine which files belong to which packages installed on a system. While this file has been present for many releases of the Solaris operating system, it might not be present in future releases. The fully supported way to obtain information from the installed package database is -through \fBpkgchk\fR(1M). It is highly recommended that you use \fBpkgchk\fR +through \fBpkgchk\fR(8). It is highly recommended that you use \fBpkgchk\fR rather than relying on the \fBcontents\fR file. diff --git a/usr/src/man/man5/contract.5 b/usr/src/man/man5/contract.5 index 98caf9d60b..12efb0c289 100644 --- a/usr/src/man/man5/contract.5 +++ b/usr/src/man/man5/contract.5 @@ -22,7 +22,7 @@ available contract type. \fB/system/contract\fR can be mounted on any mount point, in addition to the standard \fB/system/contract\fR mount point, and can be mounted several places at once. Such additional mounts are allowed in order to facilitate the -confinement of processes to subtrees of the file system using \fBchroot\fR(1M) +confinement of processes to subtrees of the file system using \fBchroot\fR(8) and yet allow such processes to continue to use contract commands and interfaces. .sp @@ -33,7 +33,7 @@ A combination of standard system calls (for example, \fBopen\fR(2), .sp .LP Consumers of the contract file system must be large file aware. See -\fBlargefile\fR(5) and \fBlfcompile64\fR(5). +\fBlargefile\fR(7) and \fBlfcompile64\fR(7). .SS "DIRECTORY STRUCTURE" .LP At the top level, the \fB/system/contract\fR directory contains subdirectories @@ -130,7 +130,7 @@ following files: Opening this file returns a file descriptor for contract \fIid\fR's control file. The open fails if the opening process does not hold contract \fIid\fR and the contract has not been inherited by the process contract of which the -opening process is a member. See \fBprocess\fR(4). +opening process is a member. See \fBprocess\fR(5). .sp The following \fBlibcontract\fR(3LIB) calls can be made on a \fBctl\fR file descriptor if the contract is owned by the caller: @@ -599,7 +599,7 @@ Status info for contract ID .SH SEE ALSO .LP -\fBctrun\fR(1), \fBctstat\fR(1), \fBctwatch\fR(1), \fBchroot\fR(1M), +\fBctrun\fR(1), \fBctstat\fR(1), \fBctwatch\fR(1), \fBchroot\fR(8), \fBclose\fR(2), \fBioctl\fR(2), \fBopen\fR(2), \fBpoll\fR(2), \fBct_ctl_abandon\fR(3CONTRACT), \fBct_event_read\fR(3CONTRACT), \fBct_event_get_evid\fR(3CONTRACT), \fBct_event_get_flags\fR(3CONTRACT), @@ -613,4 +613,4 @@ Status info for contract ID \fBct_status_get_state\fR(3CONTRACT), \fBct_status_get_type\fR(3CONTRACT), \fBct_tmpl_set_cookie\fR(3CONTRACT), \fBct_tmpl_set_critical\fR(3CONTRACT), \fBct_tmpl_set_informative\fR(3CONTRACT), \fBlibcontract\fR(3LIB), -\fBprocess\fR(4), \fBlargefile\fR(5), \fBlfcompile\fR(5), \fBprivileges\fR(5) +\fBprocess\fR(5), \fBlargefile\fR(7), \fBlfcompile\fR(7), \fBprivileges\fR(7) diff --git a/usr/src/man/man5/crypt.conf.5 b/usr/src/man/man5/crypt.conf.5 index be86bfa4a1..f492dd19b3 100644 --- a/usr/src/man/man5/crypt.conf.5 +++ b/usr/src/man/man5/crypt.conf.5 @@ -82,7 +82,7 @@ rot13 /usr/lib/security/$ISA/crypt_rot13.so .in -2 .SH ATTRIBUTES -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -98,4 +98,4 @@ Interface Stability Evolving .SH SEE ALSO \fBpasswd\fR(1), \fBcrypt\fR(3C), \fBcrypt_genhash_impl\fR(3C), \fBcrypt_gensalt\fR(3C), \fBcrypt_gensalt_impl\fR(3C), \fBgetpassphrase\fR(3C), -\fBpasswd\fR(4), \fBattributes\fR(5), \fBcrypt_unix\fR(5) +\fBpasswd\fR(5), \fBattributes\fR(7), \fBcrypt_unix\fR(7) diff --git a/usr/src/man/man5/crypto_certs.5 b/usr/src/man/man5/crypto_certs.5 index dc5329dd11..980c0c21b6 100644 --- a/usr/src/man/man5/crypto_certs.5 +++ b/usr/src/man/man5/crypto_certs.5 @@ -50,7 +50,7 @@ revision of the product. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -66,4 +66,4 @@ Interface Stability Evolving .SH SEE ALSO .sp .LP -\fBelfsign\fR(1), \fBlibpkcs11\fR(3LIB), \fBattributes\fR(5) +\fBelfsign\fR(1), \fBlibpkcs11\fR(3LIB), \fBattributes\fR(7) diff --git a/usr/src/man/man5/d_passwd.5 b/usr/src/man/man5/d_passwd.5 index 6eb994a253..c3e30102d6 100644 --- a/usr/src/man/man5/d_passwd.5 +++ b/usr/src/man/man5/d_passwd.5 @@ -24,8 +24,8 @@ before the user is granted access to the computer. \fBd_passwd\fR is an \fBASCII\fR file which contains a list of executable programs (typically shells) that require a dial-up password and the associated encrypted passwords. When a user attempts to log in on any of the ports listed -in the \fBdialups\fR file (see \fBdialups\fR(4)), the login program looks at -the user's login entry stored in the \fBpasswd\fR file (see \fBpasswd\fR(4)), +in the \fBdialups\fR file (see \fBdialups\fR(5)), the login program looks at +the user's login entry stored in the \fBpasswd\fR file (see \fBpasswd\fR(5)), and compares the login shell field to the entries in \fBd_passwd\fR. These entries determine whether the user will be required to supply a dial-up password. @@ -111,9 +111,9 @@ Here is a sample \fBd_passwd\fR file: The \fBpasswd\fR (see \fBpasswd\fR(1)) utility can be used to generate the encrypted password for each login program. \fBpasswd\fR generates encrypted passwords for users and places the password in the \fBshadow\fR (see -\fBshadow\fR(4)) file. Passwords for the \fBd_passwd\fR file will need to be +\fBshadow\fR(5)) file. Passwords for the \fBd_passwd\fR file will need to be generated by first adding a temporary user id using \fBuseradd\fR (see -\fBuseradd\fR(1M)), and then using \fBpasswd\fR(1) to generate the desired +\fBuseradd\fR(8)), and then using \fBpasswd\fR(1) to generate the desired password in the \fBshadow\fR file. Once the encrypted version of the password has been created, it can be copied to the \fBd_passwd\fR file. .sp @@ -185,8 +185,8 @@ shadow password file .SH SEE ALSO .sp .LP -\fBpasswd\fR(1), \fBuseradd\fR(1M), \fBdialups\fR(4), \fBpasswd\fR(4), -\fBshadow\fR(4) +\fBpasswd\fR(1), \fBuseradd\fR(8), \fBdialups\fR(5), \fBpasswd\fR(5), +\fBshadow\fR(5) .SH WARNINGS .sp .LP diff --git a/usr/src/man/man5/dacf.conf.5 b/usr/src/man/man5/dacf.conf.5 index 45e9048f4b..4f3a3495b1 100644 --- a/usr/src/man/man5/dacf.conf.5 +++ b/usr/src/man/man5/dacf.conf.5 @@ -26,7 +26,7 @@ Solaris 8. .SH SEE ALSO .sp .LP -\fBattributes\fR(5) +\fBattributes\fR(7) .SH NOTES .sp .LP diff --git a/usr/src/man/man5/dat.conf.5 b/usr/src/man/man5/dat.conf.5 index adee8d390d..ef4508fa0e 100644 --- a/usr/src/man/man5/dat.conf.5 +++ b/usr/src/man/man5/dat.conf.5 @@ -16,13 +16,13 @@ dat.conf \- DAT static registry .sp .LP The DAT static registry, \fB/etc/dat/dat.conf\fR is a system-wide data resource -maintained by the system administrative command \fBdatadm\fR(1M). +maintained by the system administrative command \fBdatadm\fR(8). .sp .LP \fB/etc/dat/dat.conf\fR contains a list of interface adapters supported by uDAPL service providers. An interface adapter on Infiniband (IB) corresponds to an IPoIB device instance, for example, \fBibd0\fR. An IPoIB device name -represents an IP interface plumbed by \fBifconfig\fR(1M) on an IB +represents an IP interface plumbed by \fBifconfig\fR(8) on an IB partition/Host Channel Adapter port combination. .sp .LP @@ -161,7 +161,7 @@ ibd1 u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 "" .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -177,16 +177,16 @@ Interface Stability Standard .SH SEE ALSO .sp .LP -\fBdatadm\fR(1M), \fBifconfig\fR(1M), \fBlibdat\fR(3LIB), -\fBservice_provider.conf\fR(4), \fBattributes\fR(5) +\fBdatadm\fR(8), \fBifconfig\fR(8), \fBlibdat\fR(3LIB), +\fBservice_provider.conf\fR(5), \fBattributes\fR(7) .SH NOTES .sp .LP An empty \fBdat.conf\fR is created during the package \fBSUNWudaplr\fR installation if no file is present beforehand. Entries in the file are added or -removed by running \fBdatadm\fR(1M). +removed by running \fBdatadm\fR(8). .sp .LP The content of the platform specific string does not constitute an API. It is -generated by \fBdatadm\fR(1M) and might have a different content or +generated by \fBdatadm\fR(8) and might have a different content or interpretation in a future release. diff --git a/usr/src/man/man5/default_fs.5 b/usr/src/man/man5/default_fs.5 index 1e7a492bbd..9d8031e137 100644 --- a/usr/src/man/man5/default_fs.5 +++ b/usr/src/man/man5/default_fs.5 @@ -11,7 +11,7 @@ systems .sp .LP When file system administration commands have both specific and generic -components (for example, \fBfsck\fR(1M)), the file system type must be +components (for example, \fBfsck\fR(8)), the file system type must be specified. If it is not explicitly specified using the \fB-F\fR \fIFSType\fR command line option, the generic command looks in \fB/etc/vfstab\fR in order to determine the file system type, using the supplied raw or block device or mount @@ -66,4 +66,4 @@ the default remote file system type .SH SEE ALSO .sp .LP -\fBfsck\fR(1M), \fBfstypes\fR(4), \fBvfstab\fR(4) +\fBfsck\fR(8), \fBfstypes\fR(5), \fBvfstab\fR(5) diff --git a/usr/src/man/man5/defaultdomain.5 b/usr/src/man/man5/defaultdomain.5 index ad53851a3c..2c3a4e1c5f 100644 --- a/usr/src/man/man5/defaultdomain.5 +++ b/usr/src/man/man5/defaultdomain.5 @@ -16,10 +16,10 @@ defaultdomain \- specify host's domain name .LP The file \fB/etc/defaultdomain\fR determines a host's domain name for direct use by the \fBNIS\fR name service. The \fBdefaultdomain\fR file -is read at boot time and its contents used by the \fBdomainname\fR(1M) command. +is read at boot time and its contents used by the \fBdomainname\fR(8) command. Because of its use by \fBdomainname\fR, \fBdefaultdomain\fR is also used by the \fBLDAP\fR service (see \fBldap\fR(1)). Under certain, narrow circumstances -(see \fBresolv.conf\fR(4)), because \fBdomainname\fR uses \fBdefaultdomain\fR, +(see \fBresolv.conf\fR(5)), because \fBdomainname\fR uses \fBdefaultdomain\fR, a \fBDNS\fR client can use the contents of \fBdefaultdomain\fR. .sp .LP @@ -27,8 +27,8 @@ The contents of \fBdefaultdomain\fR consists of a single line containing a host's domain name. .SH SEE ALSO .LP -\fBuname\fR(1), \fBldapclient\fR(1M), -\fBypbind\fR(1M), \fBypinit\fR(1M), \fBresolv.conf\fR(4) +\fBuname\fR(1), \fBldapclient\fR(8), +\fBypbind\fR(8), \fBypinit\fR(8), \fBresolv.conf\fR(5) .SH NOTES .LP The \fBdefaultdomain\fR file is created and modified by Solaris installation diff --git a/usr/src/man/man5/defaultrouter.5 b/usr/src/man/man5/defaultrouter.5 index f9f7aa45a1..aa8f76950c 100644 --- a/usr/src/man/man5/defaultrouter.5 +++ b/usr/src/man/man5/defaultrouter.5 @@ -47,7 +47,7 @@ route added by the kernel to be deleted. .LP Use of a default route, whether received from a \fBDHCP\fR server or from \fB/etc/defaultrouter\fR, prevents a machine from acting as an IPv4 router. You -can use \fBrouteadm\fR(1M) to override this behavior. +can use \fBrouteadm\fR(8) to override this behavior. .SH FILES .sp .ne 2 @@ -62,4 +62,4 @@ default routers. .SH SEE ALSO .sp .LP -\fBin.rdisc\fR(1M), \fBin.routed\fR(1M), \fBrouteadm\fR(1M), \fBhosts\fR(4) +\fBin.rdisc\fR(8), \fBin.routed\fR(8), \fBrouteadm\fR(8), \fBhosts\fR(5) diff --git a/usr/src/man/man5/depend.5 b/usr/src/man/man5/depend.5 index 354ab7a127..062520c3cc 100644 --- a/usr/src/man/man5/depend.5 +++ b/usr/src/man/man5/depend.5 @@ -130,7 +130,7 @@ R SUNWftpu FTP Server, (Usr) .SH SEE ALSO .sp .LP -\fBpkginfo\fR(4) +\fBpkginfo\fR(5) .sp .LP \fIApplication Packaging Developer\&'s Guide\fR diff --git a/usr/src/man/man5/device_allocate.5 b/usr/src/man/man5/device_allocate.5 index cd40f6376e..d062985718 100644 --- a/usr/src/man/man5/device_allocate.5 +++ b/usr/src/man/man5/device_allocate.5 @@ -244,7 +244,7 @@ Contains list of allocatable devices .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -260,7 +260,7 @@ Interface Stability Uncommitted .SH SEE ALSO .LP \fBauths\fR(1), \fBallocate\fR(1), \fBdeallocate\fR(1), -\fBlist_devices\fR(1), \fBauth_attr\fR(4), \fBattributes\fR(5) +\fBlist_devices\fR(1), \fBauth_attr\fR(5), \fBattributes\fR(7) .SH NOTES .LP On systems configured with Trusted Extensions, the functionality is enabled by diff --git a/usr/src/man/man5/device_contract.5 b/usr/src/man/man5/device_contract.5 index 503b3a0728..112a732ef7 100644 --- a/usr/src/man/man5/device_contract.5 +++ b/usr/src/man/man5/device_contract.5 @@ -19,7 +19,7 @@ Device contracts allow processes to monitor events involving a device of interest and to react and/or block state changes involving such devices. .sp .LP -Device contracts are managed using the \fBcontract\fR(4) file system and the +Device contracts are managed using the \fBcontract\fR(5) file system and the \fBlibcontract\fR(3LIB) library. The process contract type directory is \fB/system/contract/device\fR. .SS "Creation" @@ -167,7 +167,7 @@ this synchronously with the breaking of the old contract via .SS "TERMS" .sp .LP -The following common contract terms, defined in \fBcontract\fR(4), have +The following common contract terms, defined in \fBcontract\fR(5), have device-contract specific attributes: .sp .ne 2 @@ -195,7 +195,7 @@ events. Use \fBct_tmpl_set_critical\fR(3CONTRACT) to set this term. .LP The following contract terms can be read from or written to a device contract template using the named \fBlibcontract\fR(3LIB) interfaces. These contract -terms are in addition to those described in \fBcontract\fR(4). +terms are in addition to those described in \fBcontract\fR(5). .sp .ne 2 .na @@ -371,4 +371,4 @@ Contains definitions of events, status fields and event fields \fBct_dev_status_get_dev_state\fR(3CONTRACT), \fBct_dev_status_get_aset\fR(3CONTRACT), \fBct_dev_status_get_minor\fR(3CONTRACT), \fBlibcontract\fR(3LIB), -\fBcontract\fR(4), \fBprivileges\fR(5) +\fBcontract\fR(5), \fBprivileges\fR(7) diff --git a/usr/src/man/man5/device_maps.5 b/usr/src/man/man5/device_maps.5 index 846af2f52e..793a97081e 100644 --- a/usr/src/man/man5/device_maps.5 +++ b/usr/src/man/man5/device_maps.5 @@ -115,7 +115,7 @@ Contains access control information for devices. .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -131,10 +131,10 @@ Interface Stability Uncommitted .SH SEE ALSO .LP \fBallocate\fR(1), \fBdeallocate\fR(1), -\fBlist_devices\fR(1), \fBdminfo\fR(1M), \fBdevice_allocate\fR(4), -\fBattributes\fR(5) +\fBlist_devices\fR(1), \fBdminfo\fR(8), \fBdevice_allocate\fR(5), +\fBattributes\fR(7) .SH NOTES .LP On systems configured with Trusted Extensions, the functionality is enabled by -default. On such systems, the \fBdevice_allocate\fR(4) file is updated +default. On such systems, the \fBdevice_allocate\fR(5) file is updated automatically by the system. diff --git a/usr/src/man/man5/devices.5 b/usr/src/man/man5/devices.5 index d4fb3e2b41..1e64b474ae 100644 --- a/usr/src/man/man5/devices.5 +++ b/usr/src/man/man5/devices.5 @@ -53,7 +53,7 @@ necessary. .SH SEE ALSO .sp .LP -\fBdevfsadm\fR(1M), \fBdev\fR(7FS), \fBddi_devid_compare\fR(9F), +\fBdevfsadm\fR(8), \fBdev\fR(4FS), \fBddi_devid_compare\fR(9F), \fBddi_devid_compare\fR(9F) .SH NOTES .sp diff --git a/usr/src/man/man5/dfstab.5 b/usr/src/man/man5/dfstab.5 index 70adabfc5b..23ddd09c08 100644 --- a/usr/src/man/man5/dfstab.5 +++ b/usr/src/man/man5/dfstab.5 @@ -15,14 +15,14 @@ sharing resources across a network. \fBdfstab\fR gives a system administrator a uniform method of controlling the automatic sharing of local resources. .sp .LP -Each line of the \fBdfstab\fR file consists of a \fBshare\fR(1M) command. The +Each line of the \fBdfstab\fR file consists of a \fBshare\fR(8) command. The \fBdfstab\fR file can be read by the shell to share all resources. System administrators can also prepare their own shell scripts to execute particular lines from \fBdfstab\fR. .sp .LP The contents of \fBdfstab\fR put into effect when the command shown below is -run. See \fBsvcadm\fR(1M). +run. See \fBsvcadm\fR(8). .sp .in +2 .nf @@ -33,7 +33,7 @@ run. See \fBsvcadm\fR(1M). .SH SEE ALSO .sp .LP -\fBshare\fR(1M), \fBshareall\fR(1M), \fBsharemgr\fR(1M), \fBsvcadm\fR(1M) +\fBshare\fR(8), \fBshareall\fR(8), \fBsharemgr\fR(8), \fBsvcadm\fR(8) .SH NOTES .sp .LP @@ -41,4 +41,4 @@ Do not modify this file directly. This file is reconstructed and only maintained for backwards compatibility. Configuration lines could be lost. .sp .LP -Use the \fBsharemgr\fR(1M) command for all share management. +Use the \fBsharemgr\fR(8) command for all share management. diff --git a/usr/src/man/man5/dhcp_inittab.5 b/usr/src/man/man5/dhcp_inittab.5 index c63465a922..89ce8d149f 100644 --- a/usr/src/man/man5/dhcp_inittab.5 +++ b/usr/src/man/man5/dhcp_inittab.5 @@ -53,7 +53,7 @@ The \fBVENDOR\fR options defined here are intended for use by the Solaris \fBDHCP\fR client and \fBDHCP\fR management tools. The \fBSUNW\fR vendor space is owned by Sun, and changes are likely during upgrade. If you need to configure the Solaris \fBDHCP\fR server to support the vendor options of a -different client, see \fBdhcptab\fR(4) for details. +different client, see \fBdhcptab\fR(5) for details. .sp .LP Each \fBDHCP\fR option belongs to a certain category, which roughly defines the @@ -566,7 +566,7 @@ pairs of \fBIP\fR addresses. .in -2 .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -581,8 +581,8 @@ Interface Stability Committed .SH SEE ALSO .LP -\fBdhcpinfo\fR(1), \fBdhcpagent\fR(1M), \fBisspace\fR(3C), \fBdhcptab\fR(4), -\fBattributes\fR(5), \fBdhcp\fR(5), \fBdhcp_modules\fR(5) +\fBdhcpinfo\fR(1), \fBdhcpagent\fR(8), \fBisspace\fR(3C), \fBdhcptab\fR(5), +\fBattributes\fR(7), \fBdhcp\fR(7), \fBdhcp_modules\fR(7) .sp .LP \fISystem Administration Guide: IP Services\fR diff --git a/usr/src/man/man5/dialups.5 b/usr/src/man/man5/dialups.5 index 8983598b60..1c54f3aa5d 100644 --- a/usr/src/man/man5/dialups.5 +++ b/usr/src/man/man5/dialups.5 @@ -89,4 +89,4 @@ list of dial-up ports requiring dial-up passwords .SH SEE ALSO .sp .LP -\fBd_passwd\fR(4) +\fBd_passwd\fR(5) diff --git a/usr/src/man/man5/dir_ufs.5 b/usr/src/man/man5/dir_ufs.5 index 16f104aebc..6b73603b80 100644 --- a/usr/src/man/man5/dir_ufs.5 +++ b/usr/src/man/man5/dir_ufs.5 @@ -55,7 +55,7 @@ struct direct { .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for a description of the following attributes: +See \fBattributes\fR(7) for a description of the following attributes: .sp .sp @@ -71,4 +71,4 @@ Interface Stability Unstable .SH SEE ALSO .sp .LP -\fBattributes\fR(5), \fBufs\fR(7FS) +\fBattributes\fR(7), \fBufs\fR(4FS) diff --git a/usr/src/man/man5/driver.conf.5 b/usr/src/man/man5/driver.conf.5 index 913ef1b9ee..6e03f837d5 100644 --- a/usr/src/man/man5/driver.conf.5 +++ b/usr/src/man/man5/driver.conf.5 @@ -34,7 +34,7 @@ file, where the generic node name and \fBcompatible\fR property associated with a self-identifying devices are typically not used, the node name must be a binding name. The binding name is the name chosen by the system to bind a driver to the device. The binding name is either an alias associated with the -driver established by \fBadd_drv\fR(1M) or the driver name itself. +driver established by \fBadd_drv\fR(8) or the driver name itself. .sp .LP The syntax of a single entry in a driver configuration file takes one of three @@ -184,7 +184,7 @@ debug-level=3; .LP This creates two \fBdevinfo\fR nodes called \fBACME,example\fR which attaches below the \fBpseudo\fR node in the kernel device tree. The \fBinstance\fR -property is only interpreted by the \fBpseudo\fR node, see \fBpseudo\fR(4) for +property is only interpreted by the \fBpseudo\fR node, see \fBpseudo\fR(5) for further details. A property called \fBdebug-level\fR is created on the first \fBdevinfo\fR node which has the value 1. The \fBexample\fR driver is able to fetch the value of this property using \fBddi_prop_get_int\fR(9F). @@ -202,7 +202,7 @@ the second node retrieves the value of the global \fBdebug-level\fR property .SH SEE ALSO .LP -\fBadd_drv\fR(1M), \fBpci\fR(4), \fBpseudo\fR(4), \fBsbus\fR(4), \fBscsi\fR(4), +\fBadd_drv\fR(8), \fBpci\fR(5), \fBpseudo\fR(5), \fBsbus\fR(5), \fBscsi\fR(5), \fBprobe\fR(9E), \fBddi_getlongprop\fR(9F), \fBddi_getprop\fR(9F), \fBddi_getproplen\fR(9F), \fBddi_prop_get_int\fR(9F), \fBddi_prop_lookup\fR(9F), \fBddi_prop_op\fR(9F) @@ -217,5 +217,5 @@ vendor-unique string. A reasonably compact and unique choice is the vendor over-the-counter stock symbol. .SH NOTES .LP -The \fBupdate_drv\fR(1M) command should be used to prompt the kernel to reread +The \fBupdate_drv\fR(8) command should be used to prompt the kernel to reread \fBdriver.conf\fR files. diff --git a/usr/src/man/man5/ethers.5 b/usr/src/man/man5/ethers.5 index 4639fa576d..ec1f7f1604 100644 --- a/usr/src/man/man5/ethers.5 +++ b/usr/src/man/man5/ethers.5 @@ -44,4 +44,4 @@ comment character. .SH SEE ALSO .LP -\fBethers\fR(3SOCKET), \fBhosts\fR(4), \fBnsswitch.conf\fR(4) +\fBethers\fR(3SOCKET), \fBhosts\fR(5), \fBnsswitch.conf\fR(5) diff --git a/usr/src/man/man5/exec_attr.5 b/usr/src/man/man5/exec_attr.5 index 26736b7e78..bc082a9e1d 100644 --- a/usr/src/man/man5/exec_attr.5 +++ b/usr/src/man/man5/exec_attr.5 @@ -23,15 +23,15 @@ to access this information. .sp .LP The search order for multiple execution profile sources is specified in the -\fB/etc/nsswitch.conf\fR file, as described in the \fBnsswitch.conf\fR(4) man -page. The search order follows the entry for \fBprof_attr\fR(4). +\fB/etc/nsswitch.conf\fR file, as described in the \fBnsswitch.conf\fR(5) man +page. The search order follows the entry for \fBprof_attr\fR(5). .sp .LP A profile is a logical grouping of authorizations and commands that is interpreted by a profile shell to form a secure execution environment. The shells that interpret profiles are \fBpfcsh\fR, \fBpfksh\fR, and \fBpfsh\fR. See the \fBpfsh\fR(1) man page. Each user's account is assigned zero or more -profiles in the \fBuser_attr\fR(4) database file. +profiles in the \fBuser_attr\fR(5) database file. .sp .LP Each entry in the \fBexec_attr\fR database consists of one line of text @@ -58,7 +58,7 @@ The name of the profile. Profile names are case-sensitive. .RS 10n The security policy that is associated with the profile entry. The valid policies are \fBsuser\fR (standard Solaris superuser) and \fBsolaris\fR. The -\fBsolaris\fR policy recognizes privileges (see \fBprivileges\fR(5)); the +\fBsolaris\fR policy recognizes privileges (see \fBprivileges\fR(7)); the \fBsuser\fR policy does not. .sp The \fBsolaris\fR and \fBsuser\fR policies can coexist in the same @@ -189,7 +189,7 @@ Control profile to execute with an effective user \fBID\fR of root (\fB0\fR): \fB/etc/security/exec_attr\fR .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -222,8 +222,8 @@ equals (\fB=\fR), and backslash (\fB\e\fR). .SH SEE ALSO .LP \fBauths\fR(1), \fBprofiles\fR(1), \fBroles\fR(1), -\fBsh\fR(1), \fBmakedbm\fR(1M), \fBgetauthattr\fR(3SECDB), +\fBsh\fR(1), \fBmakedbm\fR(8), \fBgetauthattr\fR(3SECDB), \fBgetexecattr\fR(3SECDB), \fBgetprofattr\fR(3SECDB), -\fBgetuserattr\fR(3SECDB), \fBkva_match\fR(3SECDB), \fBauth_attr\fR(4), -\fBprof_attr\fR(4), \fBuser_attr\fR(4), \fBattributes\fR(5), -\fBprivileges\fR(5) +\fBgetuserattr\fR(3SECDB), \fBkva_match\fR(3SECDB), \fBauth_attr\fR(5), +\fBprof_attr\fR(5), \fBuser_attr\fR(5), \fBattributes\fR(7), +\fBprivileges\fR(7) diff --git a/usr/src/man/man5/fdi.5 b/usr/src/man/man5/fdi.5 index ec31524121..9bbc43d1a3 100644 --- a/usr/src/man/man5/fdi.5 +++ b/usr/src/man/man5/fdi.5 @@ -15,7 +15,7 @@ fdi \- HAL device information file format .SH DESCRIPTION .LP -The hardware abstraction layer facility, described in \fBhal\fR(5), uses an +The hardware abstraction layer facility, described in \fBhal\fR(7), uses an \fBXML\fR-based file format to merge arbitrary properties onto device objects. The way device information files works is that once all physical properties are merged onto a device object, it is tried against the set of installed device @@ -429,7 +429,7 @@ Device information for specific devices. All device information files are matched for every \fBhal\fR device object. .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -444,5 +444,5 @@ Interface Stability Volatile .SH SEE ALSO .LP -\fBhald\fR(1M), \fBattributes\fR(5), \fBhal\fR(5), \fBlocale\fR(5), -\fBsmf\fR(5) +\fBhald\fR(8), \fBattributes\fR(7), \fBhal\fR(7), \fBlocale\fR(7), +\fBsmf\fR(7) diff --git a/usr/src/man/man5/format.dat.5 b/usr/src/man/man5/format.dat.5 index 2efd8a2134..ecce1ab053 100644 --- a/usr/src/man/man5/format.dat.5 +++ b/usr/src/man/man5/format.dat.5 @@ -10,7 +10,7 @@ format.dat \- disk drive configuration for the format command .sp .LP \fBformat.dat\fR enables you to use your specific disk drives with -\fBformat\fR(1M). On Solaris 2.3 and compatible systems, \fBformat\fR will +\fBformat\fR(8). On Solaris 2.3 and compatible systems, \fBformat\fR will automatically configure and label SCSI drives, so that they need not be defined in \fBformat.dat\fR. Three things can be defined in the data file: .RS +4 @@ -63,7 +63,7 @@ colon (:). .TP .ie t \(bu .el o -White space is ignored by \fBformat\fR(1M). If you want an assigned value to +White space is ignored by \fBformat\fR(8). If you want an assigned value to contain white space, enclose the entire value in double quotes ("). This will cause the white space within quotes to be preserved as part of the assignment value. @@ -78,7 +78,7 @@ values by a comma (,). .SS "Keywords" .sp .LP -The data file contains disk definitions that are read in by \fBformat\fR(1M) +The data file contains disk definitions that are read in by \fBformat\fR(8) when it starts up. Each definition starts with one of the following keywords: \fBsearch_path\fR, \fBdisk_type\fR, and \fBpartition\fR. .sp @@ -94,7 +94,7 @@ configuration file, add them to the \fBsearch_path\fR definition in your data file. The data file can contain only one \fBsearch_path\fR definition. However, this single definition lets you specify all the disks you have in your system. .sp -5.x: By default, \fBformat\fR(1M) understands all the logical devices that are +5.x: By default, \fBformat\fR(8) understands all the logical devices that are of the form \fB/dev/rdsk/cntndnsn\fR; hence \fBsearch_path\fR is not normally defined on a 5.x system. .RE @@ -112,7 +112,7 @@ environment supports. You need to add a new \fBdisk_type\fR only if you have an unsupported disk. You can add as many \fBdisk_type\fR definitions to the data file as you want. .sp -The following controller types are supported by \fBformat\fR(1M): +The following controller types are supported by \fBformat\fR(8): .sp .ne 2 .na @@ -151,7 +151,7 @@ IPI panther controller The keyword itself is assigned the name of the disk type. This name appears in the disk's label and is used to identify the disk type whenever -\fBformat\fR(1M) is run. Enclose the name in double quotes to preserve any +\fBformat\fR(8) is run. Enclose the name in double quotes to preserve any white space in the name. .sp Below are lists of identifiers for supported controllers. Note that an asterisk @@ -424,7 +424,7 @@ drive type (SMD) (just call this "xy450 drive type") .RS 15n Defines a partition table for a specific disk type. The partition table contains the partitioning information, plus a name that lets you refer to it in -\fBformat\fR(1M). The default data file contains default partition definitions +\fBformat\fR(8). The default data file contains default partition definitions for several kinds of disk drives. Add a partition definition if you repartitioned any of the disks on your system. Add as many partition definitions to the data file as you need. @@ -474,7 +474,7 @@ default data file if \fBformat\fR \fB-x\fR is not specified, nor is there a .SH SEE ALSO .sp .LP -\fBformat\fR(1M) +\fBformat\fR(8) .sp .LP \fISystem Administration Guide: Basic Administration\fR diff --git a/usr/src/man/man5/fstypes.5 b/usr/src/man/man5/fstypes.5 index ca7d23d58d..37332b32c7 100644 --- a/usr/src/man/man5/fstypes.5 +++ b/usr/src/man/man5/fstypes.5 @@ -27,5 +27,5 @@ any supported text editor. .SH SEE ALSO .sp .LP -\fBdfmounts\fR(1M), \fBdfshares\fR(1M), \fBshare\fR(1M), \fBshareall\fR(1M), -\fBunshare\fR(1M) +\fBdfmounts\fR(8), \fBdfshares\fR(8), \fBshare\fR(8), \fBshareall\fR(8), +\fBunshare\fR(8) diff --git a/usr/src/man/man5/ftp.5 b/usr/src/man/man5/ftp.5 index c0c301011f..8ccac720b4 100644 --- a/usr/src/man/man5/ftp.5 +++ b/usr/src/man/man5/ftp.5 @@ -42,4 +42,4 @@ specified in \fB/etc/default/ftp\fR. .SH SEE ALSO .sp .LP -\fBftp\fR(1), \fBattributes\fR(5) +\fBftp\fR(1), \fBattributes\fR(7) diff --git a/usr/src/man/man5/ftpusers.5 b/usr/src/man/man5/ftpusers.5 index 68dce83527..78dd91ebb8 100644 --- a/usr/src/man/man5/ftpusers.5 +++ b/usr/src/man/man5/ftpusers.5 @@ -28,7 +28,7 @@ name where \fBname\fR is the user's login name. .sp .LP -The FTP Server, \fBin.ftpd\fR(1M), reads the \fBftpusers\fR file. If the login +The FTP Server, \fBin.ftpd\fR(8), reads the \fBftpusers\fR file. If the login name of the user matches one of the entries listed, it rejects the login attempt. .sp @@ -55,7 +55,7 @@ nobody4 .sp .LP -These entries match the default instantiated entries from \fBpasswd\fR(4). The +These entries match the default instantiated entries from \fBpasswd\fR(5). The list of default entries typically contains the superuser \fBroot\fR and other administrative and system application identities. .sp @@ -72,11 +72,11 @@ security policy for remote login access by \fBroot\fR. Other default entries are administrative identities that are typically assumed by system applications but never used for local or remote login, for example \fBsys\fR and \fBnobody\fR. Since these entries do not have a valid password -field instantiated in \fBshadow\fR(4), no login can be performed. +field instantiated in \fBshadow\fR(5), no login can be performed. .sp .LP If a site adds similar administrative or system application identities in -\fBpasswd\fR(4) and \fBshadow\fR(4), for example, \fBmajordomo\fR, the site +\fBpasswd\fR(5) and \fBshadow\fR(5), for example, \fBmajordomo\fR, the site should consider including them in the \fBftpusers\fR file for a consistent security policy. .sp @@ -130,7 +130,7 @@ shadow password file .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -149,5 +149,5 @@ The interface stability for \fB/etc/ftpd/ftpusers\fR is Volatile. The interface stability for \fB/etc/ftpusers\fR is (Obsolete). .SH SEE ALSO .LP -\fBlogin\fR(1), \fBftphosts\fR(4), -\fBpasswd\fR(4), \fBshadow\fR(4), \fBattributes\fR(5), \fBenviron\fR(5) +\fBlogin\fR(1), \fBftphosts\fR(5), +\fBpasswd\fR(5), \fBshadow\fR(5), \fBattributes\fR(7), \fBenviron\fR(7) diff --git a/usr/src/man/man5/fx_dptbl.5 b/usr/src/man/man5/fx_dptbl.5 index 80e049acee..baccdf447c 100644 --- a/usr/src/man/man5/fx_dptbl.5 +++ b/usr/src/man/man5/fx_dptbl.5 @@ -49,7 +49,7 @@ described in the \fB/usr/include/sys/fx.h\fR header. The global scheduling priority associated with this priority level. The mapping between fixed-priority priority levels and global scheduling priorities is determined at boot time by the system configuration. \fBfx_globpri\fR can not -be changed with \fBdispadmin\fR(1M). +be changed with \fBdispadmin\fR(8). .RE .sp @@ -73,7 +73,7 @@ absolute time. An administrator can affect the behavior of the fixed priority portion of the scheduler by reconfiguring the \fBfx_dptbl\fR. There are two methods available for doing this: reconfigure with a loadable module at boot-time or by using -\fBdispadmin\fR(1M) at run-time. +\fBdispadmin\fR(8) at run-time. .RE .SS "fx_dptbl Loadable Module" @@ -86,7 +86,7 @@ priorities used by the fixed priority class. The relevant procedure and source code is described in Replacing the fx_dptbl Loadable Module below. .SS "dispadmin Configuration File" The \fBfx_quantum\fR values in the \fBfx_dptbl\fR can be examined and modified -on a running system using the \fBdispadmin\fR(1M) command. Invoking +on a running system using the \fBdispadmin\fR(8) command. Invoking \fBdispadmin\fR for the fixed-priority class allows the administrator to retrieve the current \fBfx_dptbl\fR configuration from the kernel's in-core table or overwrite the in-core table with values from a configuration file. The @@ -174,7 +174,7 @@ Replace the current \fBFX_DPTBL\fR in \fB/usr/kernel/sched\fR. .TP 5. Make changes in the \fB/etc/system\fR file to reflect the changes to the -sizes of the tables. See \fBsystem\fR(4). The variables affected is +sizes of the tables. See \fBsystem\fR(5). The variables affected is \fBfx_maxupri\fR. The syntax for setting this is as follows: .sp .in +2 @@ -387,7 +387,7 @@ fx_getmaxumdpri() .sp .SH SEE ALSO -\fBpriocntl\fR(1), \fBdispadmin\fR(1M), \fBpriocntl\fR(2), \fBsystem\fR(4) +\fBpriocntl\fR(1), \fBdispadmin\fR(8), \fBpriocntl\fR(2), \fBsystem\fR(5) .sp .LP \fISystem Administration Guide, Volume 1, System Interface Guide\fR diff --git a/usr/src/man/man5/gateways.5 b/usr/src/man/man5/gateways.5 index f6a9ca78c3..c5564eadeb 100644 --- a/usr/src/man/man5/gateways.5 +++ b/usr/src/man/man5/gateways.5 @@ -17,7 +17,7 @@ daemon .sp .LP The \fB/etc/gateways\fR file is used by the routing daemon, -\fBin.routed\fR(1M). When the daemon starts, it reads \fB/etc/gateways\fR to +\fBin.routed\fR(8). When the daemon starts, it reads \fB/etc/gateways\fR to find such distant gateways that cannot be located using only information from a routing socket, to discover if some of the local gateways are passive, and to obtain other parameters. @@ -63,7 +63,7 @@ Name of the destination network or host. It can be a symbolic network name or an Internet address specified in \fBdot\fR notation (see \fBinet\fR(3SOCKET)). If it is a name, then it must either be defined in \fB/etc/networks\fR or \fB/etc/hosts\fR, or a naming service must have been started before -\fBin.routed\fR(1M). +\fBin.routed\fR(8). .RE .sp @@ -108,7 +108,7 @@ One of these keywords must be present to indicate whether the gateway should be treated as passive or active, or whether the gateway is external to the scope of the RIP protocol. A passive gateway is not expected to exchange routing information, while gateways marked active should be willing to exchange RIP -packets. See \fBin.routed\fR(1M) for further details. +packets. See \fBin.routed\fR(8) for further details. .RE .sp @@ -494,7 +494,7 @@ used to set a broadcast type advertisement on a point-to-point link. .SH SEE ALSO .sp .LP -\fBin.routed\fR(1M), \fBroute\fR(1M), \fBrtquery\fR(1M), \fBinet\fR(3SOCKET), +\fBin.routed\fR(8), \fBroute\fR(8), \fBrtquery\fR(8), \fBinet\fR(3SOCKET), .sp .LP \fIInternet Transport Protocols, XSIS 028112, Xerox System Integration diff --git a/usr/src/man/man5/group.5 b/usr/src/man/man5/group.5 index c46bf39958..955eb5cede 100644 --- a/usr/src/man/man5/group.5 +++ b/usr/src/man/man5/group.5 @@ -75,14 +75,14 @@ to time. .sp .LP If the number of characters in an entry exceeds 2047, group maintenance -commands, such as \fBgroupdel\fR(1M) and \fBgroupmod\fR(1M), fail. +commands, such as \fBgroupdel\fR(8) and \fBgroupmod\fR(8), fail. .sp .LP Previous releases used a group entry beginning with a `\fB+\fR' (plus sign) or `\fB\(mi\fR\&' (minus sign) to selectively incorporate entries from a naming service source (for example, an NIS map or data from an LDAP server) for group. If still required, this is supported by specifying \fBgroup:compat\fR in -\fBnsswitch.conf\fR(4). The \fBcompat\fR source may not be supported in future +\fBnsswitch.conf\fR(5). The \fBcompat\fR source may not be supported in future releases. Possible sources are \fBfiles\fR followed by \fBldap\fR. This has the effect of incorporating information from an LDAP server after the \fBgroup\fR file. @@ -153,9 +153,9 @@ maps would be effectively incorporated after the entry for stooges. .SH SEE ALSO .LP -\fBgroups\fR(1), \fBgrpck\fR(1B), \fBnewgrp\fR(1), \fBgroupadd\fR(1M), -\fBgroupdel\fR(1M), \fBgroupmod\fR(1M), \fBgetgrnam\fR(3C), -\fBinitgroups\fR(3C), \fBnsswitch.conf\fR(4), \fBunistd.h\fR(3HEAD) +\fBgroups\fR(1), \fBgrpck\fR(1B), \fBnewgrp\fR(1), \fBgroupadd\fR(8), +\fBgroupdel\fR(8), \fBgroupmod\fR(8), \fBgetgrnam\fR(3C), +\fBinitgroups\fR(3C), \fBnsswitch.conf\fR(5), \fBunistd.h\fR(3HEAD) .sp .LP \fISystem Administration Guide: Basic Administration\fR diff --git a/usr/src/man/man5/gsscred.conf.5 b/usr/src/man/man5/gsscred.conf.5 index 1d10daf087..14dec967ef 100644 --- a/usr/src/man/man5/gsscred.conf.5 +++ b/usr/src/man/man5/gsscred.conf.5 @@ -44,7 +44,7 @@ Contains GSS credential information. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -60,5 +60,5 @@ Interface Stability Evolving .SH SEE ALSO .sp .LP -\fBgsscred\fR(1M), \fBgssd\fR(1M), \fBsyslog\fR(3C), \fBkrb5.conf\fR(4), -\fBattributes\fR(5), \fBkerberos\fR(5) +\fBgsscred\fR(8), \fBgssd\fR(8), \fBsyslog\fR(3C), \fBkrb5.conf\fR(5), +\fBattributes\fR(7), \fBkerberos\fR(7) diff --git a/usr/src/man/man5/hba.conf.5 b/usr/src/man/man5/hba.conf.5 index 5e39d77a92..4ba3d01f55 100644 --- a/usr/src/man/man5/hba.conf.5 +++ b/usr/src/man/man5/hba.conf.5 @@ -71,7 +71,7 @@ com.sun.fchba64 /usr/lib/sparcv9/libsun_fc.so.1 .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -91,7 +91,7 @@ T} .SH SEE ALSO .sp .LP -\fBHBA_LoadLibrary\fR(3HBAAPI), \fBlibhbaapi\fR(3LIB), \fBattributes\fR(5) +\fBHBA_LoadLibrary\fR(3HBAAPI), \fBlibhbaapi\fR(3LIB), \fBattributes\fR(7) .SH BUGS .sp .LP diff --git a/usr/src/man/man5/holidays.5 b/usr/src/man/man5/holidays.5 index 4ed377f8ac..4580c3a0e9 100644 --- a/usr/src/man/man5/holidays.5 +++ b/usr/src/man/man5/holidays.5 @@ -91,4 +91,4 @@ The following is an example of the \fB/etc/acct/holidays\fR file: .SH SEE ALSO .sp .LP -\fBacct\fR(1M) +\fBacct\fR(8) diff --git a/usr/src/man/man5/hosts.5 b/usr/src/man/man5/hosts.5 index 6d9b36d907..c20c9fe3a9 100644 --- a/usr/src/man/man5/hosts.5 +++ b/usr/src/man/man5/hosts.5 @@ -150,7 +150,7 @@ The following is an example of an IPv6 \fBhosts\fR entry: .SH SEE ALSO .LP \fBgethostbyname\fR(3NSL), \fBgetipnodebyname\fR(3SOCKET), \fBinet\fR(3SOCKET), -\fBnsswitch.conf\fR(4), \fBresolv.conf\fR(4) +\fBnsswitch.conf\fR(5), \fBresolv.conf\fR(5) .sp .LP Braden, B., editor, RFC 1123, \fIRequirements for Internet Hosts - Application diff --git a/usr/src/man/man5/hosts.equiv.5 b/usr/src/man/man5/hosts.equiv.5 index 3600dbf931..a5370aca10 100644 --- a/usr/src/man/man5/hosts.equiv.5 +++ b/usr/src/man/man5/hosts.equiv.5 @@ -93,7 +93,7 @@ system \fIas a different local user\fR. If this form is used in the the system as \fBany\fR local user. .sp .LP -\fBnetgroup\fR(4) can be used in either the \fIhostname\fR or \fIusername\fR +\fBnetgroup\fR(5) can be used in either the \fIhostname\fR or \fIusername\fR fields to match a number of hosts or users in one entry. The form: .sp .in +2 @@ -308,7 +308,7 @@ user's trusted hosts and users .SH SEE ALSO .LP \fBrcp\fR(1), \fBrlogin\fR(1), \fBrsh\fR(1), \fBrcmd\fR(3SOCKET), -\fBhosts\fR(4), \fBnetgroup\fR(4), \fBpasswd\fR(4) +\fBhosts\fR(5), \fBnetgroup\fR(5), \fBpasswd\fR(5) .SH WARNINGS .LP Positive entries in \fB/etc/hosts.equiv\fR that include a \fIusername\fR field diff --git a/usr/src/man/man5/hosts_access.5 b/usr/src/man/man5/hosts_access.5 index 1d6b55880d..d0349b5ce6 100644 --- a/usr/src/man/man5/hosts_access.5 +++ b/usr/src/man/man5/hosts_access.5 @@ -14,7 +14,7 @@ impatient reader is encouraged to skip to the EXAMPLES section for a quick introduction. .PP An extended version of the access control language is described in the -\fIhosts_options\fR(4) document. The extensions are turned on at +\fIhosts_options\fR(5) document. The extensions are turned on at program build time by building with -DPROCESS_OPTIONS. .PP In the following text, \fIdaemon\fR is the process name of a @@ -145,7 +145,7 @@ Shell commands should not rely on the PATH setting of the inetd. Instead, they should use absolute path names, or they should begin with an explicit PATH=whatever statement. .PP -The \fIhosts_options\fR(4) document describes an alternative language +The \fIhosts_options\fR(5) document describes an alternative language that uses the shell command field in a different and incompatible way. .SH % EXPANSIONS The following expansions are available within shell commands: @@ -183,7 +183,7 @@ Patterns like these can be used when the machine has different internet addresses with different internet hostnames. Service providers can use this facility to offer FTP, GOPHER or WWW archives with internet names that may even belong to different organizations. See also the `twist' -option in the hosts_options(4) document. Some systems (Solaris, +option in the hosts_options(5) document. Some systems (Solaris, FreeBSD) can have more than one internet address on one physical interface; with other systems you may have to resort to SLIP or PPP pseudo interfaces that live in a dedicated network address space. @@ -365,8 +365,8 @@ that shouldn\'t. All problems are reported via the syslog daemon. .fi .SH SEE ALSO .nf -tcpd(1M) tcp/ip daemon wrapper program. -tcpdchk(1M), tcpdmatch(1M), test programs. +tcpd(8) tcp/ip daemon wrapper program. +tcpdchk(8), tcpdmatch(8), test programs. .SH BUGS If a name server lookup times out, the host name will not be available to the access control software, even though the host is registered. diff --git a/usr/src/man/man5/hosts_options.5 b/usr/src/man/man5/hosts_options.5 index bdc3644907..ce570aa055 100644 --- a/usr/src/man/man5/hosts_options.5 +++ b/usr/src/man/man5/hosts_options.5 @@ -8,7 +8,7 @@ hosts_options \- host access control language extensions .SH DESCRIPTION This document describes optional extensions to the language described -in the hosts_access(4) document. The extensions are enabled at program +in the hosts_access(5) document. The extensions are enabled at program build time. For example, by editing the Makefile and turning on the PROCESS_OPTIONS compile-time option. .PP @@ -16,7 +16,7 @@ The extensible language uses the following format: .sp daemon_list : client_list : option : option ... .PP -The first two fields are described in the hosts_access(4) manual page. +The first two fields are described in the hosts_access(5) manual page. The remainder of the rules is a list of zero or more options. Any ":" characters within options should be protected with a backslash. .PP @@ -56,7 +56,7 @@ Notice the leading dot on the domain name patterns. .SH RUNNING OTHER COMMANDS .IP "spawn shell_command" Execute, in a child process, the specified shell command, after -performing the %<letter> expansions described in the hosts_access(4) +performing the %<letter> expansions described in the hosts_access(5) manual page. The command is executed with stdin, stdout and stderr connected to the null device, so that it won\'t mess up the conversation with the client host. Example: @@ -77,7 +77,7 @@ the data sent by the remote host. .IP "twist shell_command" Replace the current process by an instance of the specified shell command, after performing the %<letter> expansions described in the -hosts_access(4) manual page. Stdin, stdout and stderr are connected to +hosts_access(5) manual page. Stdin, stdout and stderr are connected to the client process. This option must appear at the end of a rule. .sp To send a customized bounce message to the client instead of @@ -125,7 +125,7 @@ Look for a file in `/some/directory' with the same name as the daemon process (for example in.telnetd for the telnet service), and copy its contents to the client. Newline characters are replaced by carriage-return newline, and %<letter> sequences are expanded (see -the hosts_access(4) manual page). +the hosts_access(5) manual page). .sp The tcp wrappers source code distribution provides a sample makefile (Banners.Makefile) for convenient banner maintenance. @@ -157,7 +157,7 @@ When a syntax error is found in an access control rule, the error is reported to the syslog daemon; further options will be ignored, and service is denied. .SH SEE ALSO -hosts_access(4), the default access control language +hosts_access(5), the default access control language .SH AUTHOR .nf Wietse Venema (wietse@wzv.win.tue.nl) diff --git a/usr/src/man/man5/ib.5 b/usr/src/man/man5/ib.5 index 4b65ca7121..37099e9673 100644 --- a/usr/src/man/man5/ib.5 +++ b/usr/src/man/man5/ib.5 @@ -10,7 +10,7 @@ ib \- InfiniBand device driver configuration files .sp .LP The InfiniBand (IB) bus is an I/O transport based on switched fabrics. IB -devices are managed by the \fBib\fR(7D) nexus driver. There are three +devices are managed by the \fBib\fR(4D) nexus driver. There are three categories of InfiniBand devices: .RS +4 .TP @@ -33,11 +33,11 @@ IB Pseudo devices .sp .LP The IB port/IB VPPA/IB HCA_SVC devices are enumerated by way of the -\fBib.conf\fR file. See \fBib\fR(7D). +\fBib.conf\fR file. See \fBib\fR(4D). .sp .LP The IB IOC devices are enumerated using the InfiniBand Device management class. -See \fBibdm\fR(7D). +See \fBibdm\fR(4D). .sp .LP For devices not in these two categories, most notably IB Pseudo devices, the @@ -50,14 +50,14 @@ value pairs you can retrieve using the DDI property interfaces. See Configuration files for IB device drivers must identify the parent driver explicitly as \fBib\fR, and must create a string array property called \fBunit-address\fR which is unique to this entry in the configuration file. -Drivers name \fBibport\fR and \fBioc\fR are reserved by \fBib\fR(7D) and should +Drivers name \fBibport\fR and \fBioc\fR are reserved by \fBib\fR(4D) and should not be used. .sp .LP Each entry in the configuration file creates a prototype \fBdevinfo\fR node. Each node is assigned a unit address which is determined by the value of the \fBunit-address\fR property. This property is only applicable to children of -the IB parent and is required. See \fBdriver.conf\fR(4) for further details on +the IB parent and is required. See \fBdriver.conf\fR(5) for further details on configuration file syntax. .SH EXAMPLES .sp @@ -83,4 +83,4 @@ that implements a generic IB driver. This file creates a node called .SH SEE ALSO .sp .LP -\fBdriver.conf\fR(4), \fBib\fR(7D), \fBibtl\fR(7D), \fBddi_prop_op\fR(9F) +\fBdriver.conf\fR(5), \fBib\fR(4D), \fBibtl\fR(4D), \fBddi_prop_op\fR(9F) diff --git a/usr/src/man/man5/ike.config.5 b/usr/src/man/man5/ike.config.5 index 1488b2debe..5166121430 100644 --- a/usr/src/man/man5/ike.config.5 +++ b/usr/src/man/man5/ike.config.5 @@ -18,7 +18,7 @@ requests. It also contains rules for preparing outbound \fBIKE\fR requests. .sp .LP You can test the syntactic correctness of an \fB/etc/inet/ike/config\fR file by -using the \fB-c\fR or \fB-f\fR options of \fBin.iked\fR(1M). You must use the +using the \fB-c\fR or \fB-f\fR options of \fBin.iked\fR(8). You must use the \fB-c\fR option to test a \fBconfig\fR file. You might need to use the \fB-f\fR option if it is not in \fB/etc/inet/ike/config\fR. .SS "Lexical Components" @@ -174,7 +174,7 @@ alternative names, the filename or \fBslot\fR of a certificate in Any \fIcert-sel\fR preceded by the character \fB!\fR indicates a negative match, that is, not matching this specifier. These are the same kind of strings -used in \fBikecert\fR(1M). +used in \fBikecert\fR(8). .RE .sp @@ -275,7 +275,7 @@ negotiation linger before deleting it. Default value: 300 seconds. .ad .sp .6 .RS 4n -If this keyword is present in the file, \fBin.iked\fR(1M) ignores Certificate +If this keyword is present in the file, \fBin.iked\fR(8) ignores Certificate Revocation Lists (\fBCRL\fRs) for root \fBCA\fRs (as given in \fBcert_root\fR) .RE @@ -299,16 +299,16 @@ A list of LDAP servers to query for certificates. The list can be additive. The string that follows is a name of a shared object (\fB\&.so\fR) that implements the PKCS#11 standard. The name is passed directly into \fBdlopen\fR(3C) for linking, with all of the semantics of that library call. -By default, \fBin.iked\fR(1M) runs the same ISA as the running kernel, so a +By default, \fBin.iked\fR(8) runs the same ISA as the running kernel, so a library specified using \fBpkcs11_path\fR and an absolute pathname \fBmust\fR match the same ISA as the kernel. One can use the start/exec SMF property (see -\fBsvccfg\fR(1M)) to change \fBin.iked\fR's ISA, but it is not recommended. +\fBsvccfg\fR(8)) to change \fBin.iked\fR's ISA, but it is not recommended. .sp If this setting is not present, the default value is set to \fBlibpkcs11.so\fR. Most cryptographic providers go through the default library, and this parameter should only be used if a specialized provider of IKE-useful cryptographic services cannot interface with the Solaris Cryptographic Framework. See -\fBcryptoadm\fR(1M). +\fBcryptoadm\fR(8). .sp This option is now deprecated, and may be removed in a future release. .RE @@ -383,7 +383,7 @@ The string following this keyword must be a URL for a SOCKS proxy, for example, .ad .sp .6 .RS 4n -If this keyword is present in the file, \fBin.iked\fR(1M) uses HTTP to retrieve +If this keyword is present in the file, \fBin.iked\fR(8) uses HTTP to retrieve Certificate Revocation Lists (\fBCRL\fRs). .RE @@ -648,7 +648,7 @@ aes-cbc}\fR .ad .sp .6 .RS 4n -An encryption algorithm, as in \fBipsecconf\fR(1M). However, of the ciphers +An encryption algorithm, as in \fBipsecconf\fR(8). However, of the ciphers listed above, only \fBaes\fR and \fBaes-cbc\fR allow optional key-size setting, using the "low value-to-high value" syntax. To specify a single AES key size, the low value must equal the high value. If no range is specified, all three @@ -664,10 +664,10 @@ AES key sizes are allowed. .RS 4n An authentication algorithm. .sp -Use \fBipsecalgs\fR(1M) with the \fB-l\fR option to list the IPsec protocols +Use \fBipsecalgs\fR(8) with the \fB-l\fR option to list the IPsec protocols and algorithms currently defined on a system. The \fBcryptoadm list\fR command displays a list of installed providers and their mechanisms. See -\fBcryptoadm\fR(1M). +\fBcryptoadm\fR(8). .RE .sp @@ -940,7 +940,7 @@ aes-cbc}\fR .ad .sp .6 .RS 4n -An encryption algorithm, as in \fBipsecconf\fR(1M). However, of the ciphers +An encryption algorithm, as in \fBipsecconf\fR(8). However, of the ciphers listed above, only \fBaes\fR and \fBaes-cbc\fR allow optional key-size setting, using the "low value-to-high value" syntax. To specify a single AES key size, the low value must equal the high value. If no range is specified, all three @@ -954,7 +954,7 @@ AES key sizes are allowed. .ad .sp .6 .RS 4n -An authentication algorithm, as specified in \fBipseckey\fR(1M). +An authentication algorithm, as specified in \fBipseckey\fR(8). .RE .sp @@ -996,7 +996,7 @@ The following is an example of an \fBike.config\fR file: ### certificate parameters... # Root certificates. I SHOULD use a full Distinguished Name. -# I must have this certificate in my local filesystem, see ikecert(1m). +# I must have this certificate in my local filesystem, see ikecert(8). cert_root "C=US, O=Sun Microsystems\\, Inc., CN=Sun CA" # Explicitly trusted certs that need no signatures, or perhaps @@ -1149,7 +1149,7 @@ p2_pfs 2 .in -2 .SH ATTRIBUTES -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -1163,9 +1163,9 @@ Interface Stability Committed .TE .SH SEE ALSO -\fBcryptoadm\fR(1M), \fBikeadm\fR(1M), \fBin.iked\fR(1M), \fBikecert\fR(1M), -\fBipseckey\fR(1M), \fBipsecalgs\fR(1M), \fBipsecconf\fR(1M), \fBsvccfg\fR(1M), -\fBdlopen\fR(3C), \fBattributes\fR(5), \fBrandom\fR(7D) +\fBcryptoadm\fR(8), \fBikeadm\fR(8), \fBin.iked\fR(8), \fBikecert\fR(8), +\fBipseckey\fR(8), \fBipsecalgs\fR(8), \fBipsecconf\fR(8), \fBsvccfg\fR(8), +\fBdlopen\fR(3C), \fBattributes\fR(7), \fBrandom\fR(4D) .sp .LP Harkins, Dan and Carrel, Dave. \fIRFC 2409, Internet Key Exchange (IKE)\fR. diff --git a/usr/src/man/man5/ike.preshared.5 b/usr/src/man/man5/ike.preshared.5 index 89cf98bcda..2795314a0c 100644 --- a/usr/src/man/man5/ike.preshared.5 +++ b/usr/src/man/man5/ike.preshared.5 @@ -43,8 +43,8 @@ key hex-string 1234567890abcdef Comment lines with \fB#\fR appearing in the first column are also legal. .sp .LP -Files in this format can also be used by the \fBikeadm\fR(1M) command to load -additional pre-shared keys into a running an \fBin.iked\fR(1M) process. +Files in this format can also be used by the \fBikeadm\fR(8) command to load +additional pre-shared keys into a running an \fBin.iked\fR(8) process. .SH EXAMPLES .LP \fBExample 1 \fRA Sample ike.preshared File @@ -91,5 +91,5 @@ secrets in this file will be compromised as well. The default permissions on .SH SEE ALSO .sp .LP -\fBod\fR(1), \fBikeadm\fR(1M), \fBin.iked\fR(1M), \fBipseckey\fR(1M), -\fBattributes\fR(5), \fBrandom\fR(7D) +\fBod\fR(1), \fBikeadm\fR(8), \fBin.iked\fR(8), \fBipseckey\fR(8), +\fBattributes\fR(7), \fBrandom\fR(4D) diff --git a/usr/src/man/man5/inet_type.5 b/usr/src/man/man5/inet_type.5 index 7d8607a19b..ca537a4f01 100644 --- a/usr/src/man/man5/inet_type.5 +++ b/usr/src/man/man5/inet_type.5 @@ -16,8 +16,8 @@ inet_type \- default Internet protocol type .sp .LP The \fBinet_type\fR file defines the default \fBIP\fR protocol to use. -Currently this file is only used by the \fBifconfig\fR(1M) and -\fBnetstat\fR(1M) commands. +Currently this file is only used by the \fBifconfig\fR(8) and +\fBnetstat\fR(8) commands. .sp .LP The \fBinet_type\fR file can contain a number of \fB<variable>=<value>\fR @@ -39,7 +39,7 @@ will be displayed: .ad .RS 15n Displays only IPv4 related information. The output displayed is backward -compatible with older versions of the \fBifconfig\fR(1M) and \fBnetstat\fR(1M) +compatible with older versions of the \fBifconfig\fR(8) and \fBnetstat\fR(8) commands. .RE @@ -98,4 +98,4 @@ DEFAULT_IP=IP_VERSION4 .SH SEE ALSO .sp .LP -\fBifconfig\fR(1M), \fBnetstat\fR(1M) +\fBifconfig\fR(8), \fBnetstat\fR(8) diff --git a/usr/src/man/man5/inetd.conf.5 b/usr/src/man/man5/inetd.conf.5 index 5a7488e34b..3cfa3c0bf6 100644 --- a/usr/src/man/man5/inetd.conf.5 +++ b/usr/src/man/man5/inetd.conf.5 @@ -20,16 +20,16 @@ inetd.conf \- Internet servers database In the current release of the Solaris operating system, the \fBinetd.conf\fR file is no longer directly used to configure \fBinetd\fR. The Solaris services which were formerly configured using this file are now configured in the -Service Management Facility (see \fBsmf\fR(5)) using \fBinetadm\fR(1M). Any +Service Management Facility (see \fBsmf\fR(7)) using \fBinetadm\fR(8). Any records remaining in this file after installation or upgrade, or later created -by installing additional software, must be converted to \fBsmf\fR(5) services -and imported into the SMF repository using \fBinetconv\fR(1M), otherwise the +by installing additional software, must be converted to \fBsmf\fR(7) services +and imported into the SMF repository using \fBinetconv\fR(8), otherwise the service will not be available. .sp .LP For Solaris operating system releases prior to the current release (such as Solaris 9), the \fBinetd.conf\fR file contains the list of servers that -\fBinetd\fR(1M) invokes when it receives an Internet request over a socket. +\fBinetd\fR(8) invokes when it receives an Internet request over a socket. Each server entry is composed of a single line of the form: .sp .in +2 @@ -235,8 +235,8 @@ Internet network services .SH SEE ALSO .LP -\fBrlogin\fR(1), \fBrsh\fR(1), \fBin.tftpd\fR(1M), \fBinetadm\fR(1M), -\fBinetconv\fR(1M), \fBinetd\fR(1M), \fBservices\fR(4), \fBsmf\fR(5) +\fBrlogin\fR(1), \fBrsh\fR(1), \fBin.tftpd\fR(8), \fBinetadm\fR(8), +\fBinetconv\fR(8), \fBinetd\fR(8), \fBservices\fR(5), \fBsmf\fR(7) .SH NOTES .LP \fB/etc/inet/inetd.conf\fR is the official SVR4 name of the \fBinetd.conf\fR @@ -247,4 +247,4 @@ compatibility. This man page describes \fBinetd.conf\fR as it was supported in Solaris operating system releases prior to the current release. The services that were configured by means of \fBinetd.conf\fR are now configured in the Service -Management Facility (see \fBsmf\fR(5)) using \fBinetadm\fR(1M). +Management Facility (see \fBsmf\fR(7)) using \fBinetadm\fR(8). diff --git a/usr/src/man/man5/init.d.5 b/usr/src/man/man5/init.d.5 index 34610a1234..5a6553a5d6 100644 --- a/usr/src/man/man5/init.d.5 +++ b/usr/src/man/man5/init.d.5 @@ -17,14 +17,14 @@ init.d \- initialization and termination scripts for changing init states \fB/etc/init.d\fR is a directory containing initialization and termination scripts for changing init states. These scripts are linked when appropriate to files in the \fBrc?.d\fR directories, where `\fB?\fR' is a single character -corresponding to the init state. See \fBinit\fR(1M) for definitions of the +corresponding to the init state. See \fBinit\fR(8) for definitions of the states. .sp .LP -The service management facility (see \fBsmf\fR(5)) is the preferred mechanism +The service management facility (see \fBsmf\fR(7)) is the preferred mechanism for service initiation and termination. The \fBinit.d\fR and \fBrc?.d\fR directories are obsolete, and are provided for compatibility purposes only. -Applications launched from these directories by \fBsvc.startd\fR(1M) are +Applications launched from these directories by \fBsvc.startd\fR(8) are incomplete services, and will not be restarted on failure. .sp .LP @@ -60,7 +60,7 @@ are not intended to be invoked from a command line. .sp .LP When changing to init state 2 (multi-user mode, network resources not -exported), \fB/sbin/rc2\fR is initiated by the \fBsvc.startd\fR(1M) process. +exported), \fB/sbin/rc2\fR is initiated by the \fBsvc.startd\fR(8) process. The following steps are performed by \fB/sbin/rc2\fR. .RS +4 @@ -88,20 +88,20 @@ and by \fB/etc/rc0.d/K67netdaemon stop\fR when shutting the system down. .SH SEE ALSO .LP -\fBsvcs\fR(1), \fBinit\fR(1M), \fBsvc.startd\fR(1M), \fBsvccfg\fR(1M), -\fBsmf\fR(5) +\fBsvcs\fR(1), \fBinit\fR(8), \fBsvc.startd\fR(8), \fBsvccfg\fR(8), +\fBsmf\fR(7) .SH NOTES .LP Solaris now provides an expanded mechanism, which includes automated restart, for applications historically started via the init script mechanism. The -Service Management Facility (introduced in \fBsmf\fR(5)) is the preferred +Service Management Facility (introduced in \fBsmf\fR(7)) is the preferred delivery mechanism for persistently running applications. Existing \fBinit.d\fR scripts will, however, continue to be executed according to the rules in this manual page. The details of execution in relation to managed services are -available in \fBsvc.startd\fR(1M). +available in \fBsvc.startd\fR(8). .sp .LP On earlier Solaris releases, a script named with a suffix of '.sh' would be sourced, allowing scripts to modify the environment of other scripts executed later. This behavior is no longer supported; for altering the environment in -which services are run, see the \fBsetenv\fR subcommand in \fBsvccfg\fR(1M). +which services are run, see the \fBsetenv\fR subcommand in \fBsvccfg\fR(8). diff --git a/usr/src/man/man5/inittab.5 b/usr/src/man/man5/inittab.5 index 6e8ad0973b..cc2e5718a6 100644 --- a/usr/src/man/man5/inittab.5 +++ b/usr/src/man/man5/inittab.5 @@ -16,12 +16,12 @@ processes most typically dispatched by \fBinit\fR are daemons. .LP It is no longer necessary to edit the \fB/etc/inittab\fR file directly. Administrators should use the Solaris Service Management Facility (SMF) to -define services instead. Refer to \fBsmf\fR(5) and the \fISystem Administration +define services instead. Refer to \fBsmf\fR(7) and the \fISystem Administration Guide: Basic Administration\fR for more information on SMF. .sp .LP -To modify parameters passed to \fBttymon\fR(1M), use \fBsvccfg\fR(1M) to modify -the SMF repository. See \fBttymon\fR(1M) for details on the available SMF +To modify parameters passed to \fBttymon\fR(8), use \fBsvccfg\fR(8) to modify +the SMF repository. See \fBttymon\fR(8) for details on the available SMF properties. .sp .LP @@ -75,7 +75,7 @@ There are three other values, \fBa\fR, \fBb\fR and \fBc\fR, which can appear in the \fIrstate\fR field, even though they are not true run levels. Entries which have these characters in the \fIrstate\fR field are processed only when an \fBinit\fR or \fBtelinit\fR process requests them to be run (regardless of the -current run level of the system). See \fBinit\fR(1M). These differ from run +current run level of the system). See \fBinit\fR(8). These differ from run levels in that \fBinit\fR can never enter run level \fBa\fR, \fBb\fR or \fBc\fR. Also, a request for the execution of any of these processes does not change the current run level. Furthermore, a process started by an \fBa\fR, @@ -230,9 +230,9 @@ with \fBexec\fR and passed to a forked \fBsh\fR as \fBsh \(mic 'exec\fR .SH SEE ALSO .sp .LP -\fBsh\fR(1), \fBwho\fR(1), \fBinit\fR(1M), \fBsvcadm\fR(1M), -\fBsvc.startd\fR(1M), \fBttymon\fR(1M), \fBexec\fR(2), \fBopen\fR(2), -\fBsignal\fR(3C), \fBsmf\fR(5) +\fBsh\fR(1), \fBwho\fR(1), \fBinit\fR(8), \fBsvcadm\fR(8), +\fBsvc.startd\fR(8), \fBttymon\fR(8), \fBexec\fR(2), \fBopen\fR(2), +\fBsignal\fR(3C), \fBsmf\fR(7) .sp .LP \fISystem Administration Guide: Basic Administration\fR @@ -243,8 +243,8 @@ With the introduction of the service management facility, the system-provided \fB/etc/inittab\fR file is greatly reduced from previous releases. .sp .LP -The \fBinitdefault\fR entry is not recognized in Solaris 10. See \fBsmf\fR(5) -for information on \fBSMF\fR milestones, and \fBsvcadm\fR(1M), which describes +The \fBinitdefault\fR entry is not recognized in Solaris 10. See \fBsmf\fR(7) +for information on \fBSMF\fR milestones, and \fBsvcadm\fR(8), which describes the "\fBsvcadm\fR \fBmilestone\fR \fB-d\fR" command; this provides similar functionality to modifying the \fBinitdefault\fR entry in previous versions of the Solaris OS. diff --git a/usr/src/man/man5/ipaddrsel.conf.5 b/usr/src/man/man5/ipaddrsel.conf.5 index 677fb45e39..51423a8432 100644 --- a/usr/src/man/man5/ipaddrsel.conf.5 +++ b/usr/src/man/man5/ipaddrsel.conf.5 @@ -19,7 +19,7 @@ The \fBipaddrsel.conf\fR file contains the IPv6 default address selection policy table used for IPv6 source address selection and the sorting of \fBAF_INET6\fR addresses returned from name to address resolution. The mechanism for loading the file, the file format, and the meaning of the -contents are described in \fBipaddrsel\fR(1M). +contents are described in \fBipaddrsel\fR(8). .SH EXAMPLES .LP \fBExample 1 \fRDefault \fB/etc/inet/ipaddrsel.conf\fR File @@ -48,7 +48,7 @@ The following is the default \fB/etc/inet/ipaddrsel.conf\fR file: .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -64,4 +64,4 @@ Interface Stability Evolving .SH SEE ALSO .sp .LP -\fBipaddrsel\fR(1M), \fBattributes\fR(5) +\fBipaddrsel\fR(8), \fBattributes\fR(7) diff --git a/usr/src/man/man5/ipf.5 b/usr/src/man/man5/ipf.5 index 5487fa9de4..29b8967dac 100644 --- a/usr/src/man/man5/ipf.5 +++ b/usr/src/man/man5/ipf.5 @@ -127,7 +127,7 @@ below). Filters are installed by default at the end of the kernel's filter lists, prepending the rule with \fB@n\fP will cause it to be inserted as the n'th entry in the current list. This is especially useful when -modifying and testing active filter rulesets. See \fBipf\fP(1M) for more +modifying and testing active filter rulesets. See \fBipf\fP(8) for more information. .SH ACTIONS The action indicates what to do with the packet if it matches the rest @@ -166,7 +166,7 @@ the filter. .B count causes the packet to be included in the accounting statistics kept by the filter, and has no effect on whether the packet will be allowed through -the filter. These statistics are viewable with ipfstat(1M). +the filter. These statistics are viewable with ipfstat(8). .TP .B call this action is used to invoke the named function in the kernel, which @@ -462,8 +462,8 @@ indicates what logging facility and priority, or just priority with the default facility being used, will be used to log information about this packet using ipmon's -s option. .PP -See ipl(4) for the format of records written -to this device. The ipmon(1M) program can be used to read and format +See ipl(5) for the format of records written +to this device. The ipmon(8) program can be used to read and format this log. .SH EXAMPLES The \fBquick\fP option is good for rules such as: @@ -547,4 +547,4 @@ qualifies all service/port names with the protocol specified. .br /etc/services .SH SEE ALSO -\fBipnat\fR(4), \fBipf\fR(1M), \fBipfstat\fR(1M), \fBipfilter\fR(5) +\fBipnat\fR(5), \fBipf\fR(8), \fBipfstat\fR(8), \fBipfilter\fR(7) diff --git a/usr/src/man/man5/ipmon.5 b/usr/src/man/man5/ipmon.5 index cba341f7ed..1b143ae030 100644 --- a/usr/src/man/man5/ipmon.5 +++ b/usr/src/man/man5/ipmon.5 @@ -69,4 +69,4 @@ compared for matches - there is no first or last rule match. .br /etc/ipmon.conf .SH SEE ALSO -\fBipmon\fR(1M), \fBipfilter\fR(5) +\fBipmon\fR(8), \fBipfilter\fR(7) diff --git a/usr/src/man/man5/ipnat.5 b/usr/src/man/man5/ipnat.5 index 8f61cf1bc2..85b3dd9853 100644 --- a/usr/src/man/man5/ipnat.5 +++ b/usr/src/man/man5/ipnat.5 @@ -291,5 +291,5 @@ IP address with the \fBmap\fP command. .br /etc/hosts .SH SEE ALSO -\fBhosts\fR(4), \fBipf\fR(4), \fBservices\fR(4), \fBipf\fR(1M), -\fBipnat\fR(1M), \fBipfilter\fR(5) +\fBhosts\fR(5), \fBipf\fR(5), \fBservices\fR(5), \fBipf\fR(8), +\fBipnat\fR(8), \fBipfilter\fR(7) diff --git a/usr/src/man/man5/ipnodes.5 b/usr/src/man/man5/ipnodes.5 index 9fae370974..4582bb746e 100644 --- a/usr/src/man/man5/ipnodes.5 +++ b/usr/src/man/man5/ipnodes.5 @@ -16,10 +16,10 @@ ipnodes \- symbolic link to hosts database .sp .LP The \fBipnodes\fR file is now a symbolic link to the \fB/etc/hosts\fR file. See -\fBhosts\fR(4). In prior releases of the Solaris operating system, +\fBhosts\fR(5). In prior releases of the Solaris operating system, \fBipnodes\fR was a local database distinct from \fBhosts\fR. The man page for a given Solaris release describes the \fBipnodes\fR file for that release. .SH SEE ALSO .sp .LP -\fBhosts\fR(4) +\fBhosts\fR(5) diff --git a/usr/src/man/man5/ippool.5 b/usr/src/man/man5/ippool.5 index 23101743ce..16aa939942 100644 --- a/usr/src/man/man5/ippool.5 +++ b/usr/src/man/man5/ippool.5 @@ -152,5 +152,5 @@ group-map out role = ipf number = 2010 group = 2020 .br /etc/hosts .SH SEE ALSO -\fBippool\fR(1M), \fBhosts\fR(4), \fBipf\fR(4), \fBipf\fR(1M), \fBipnat\fR(1M), -\fBipfilter\fR(5) +\fBippool\fR(8), \fBhosts\fR(5), \fBipf\fR(5), \fBipf\fR(8), \fBipnat\fR(8), +\fBipfilter\fR(7) diff --git a/usr/src/man/man5/issue.5 b/usr/src/man/man5/issue.5 index af155d1e80..ed55d03e75 100644 --- a/usr/src/man/man5/issue.5 +++ b/usr/src/man/man5/issue.5 @@ -26,4 +26,4 @@ the normal prompt. .SH SEE ALSO .sp .LP -\fBlogin\fR(1), \fBttymon\fR(1M) +\fBlogin\fR(1), \fBttymon\fR(8) diff --git a/usr/src/man/man5/kadm5.acl.5 b/usr/src/man/man5/kadm5.acl.5 index 3376ec1bfc..79e1b20967 100644 --- a/usr/src/man/man5/kadm5.acl.5 +++ b/usr/src/man/man5/kadm5.acl.5 @@ -15,15 +15,15 @@ kadm5.acl \- Kerberos access control list (ACL) file .SH DESCRIPTION .sp .LP -The \fBACL\fR file is used by the \fBkadmind\fR(1M) command to determine which +The \fBACL\fR file is used by the \fBkadmind\fR(8) command to determine which principals are allowed to perform Kerberos administration actions. For operations that affect principals, the \fBACL\fR file also controls which principals can operate on which other principals. The location of the \fBACL\fR file is determined by the \fBacl_file\fR configuration variable in the -\fBkdc.conf\fR(4) file. The default location is \fB/etc/krb5/kadm5.acl\fR. +\fBkdc.conf\fR(5) file. The default location is \fB/etc/krb5/kadm5.acl\fR. .sp .LP -For incremental propagation, see \fBkadmind\fR(1M). The ACL file must contain +For incremental propagation, see \fBkadmind\fR(8). The ACL file must contain the \fBkiprop\fR service principal with propagation privileges in order for the slave KDC to pull updates from the master's principal database. Refer to the EXAMPLES section for this case. @@ -374,7 +374,7 @@ KDC configuration information. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -390,6 +390,6 @@ Interface Stability Evolving .SH SEE ALSO .sp .LP -\fBkpasswd\fR(1), \fBkadmind\fR(1M), \fBkadmin.local\fR(1M), -\fBkdb5_util\fR(1M), \fBkdc.conf\fR(4), \fBattributes\fR(5), \fBkerberos\fR(5), -\fBpam_krb5_migrate\fR(5) +\fBkpasswd\fR(1), \fBkadmind\fR(8), \fBkadmin.local\fR(8), +\fBkdb5_util\fR(8), \fBkdc.conf\fR(5), \fBattributes\fR(7), \fBkerberos\fR(7), +\fBpam_krb5_migrate\fR(7) diff --git a/usr/src/man/man5/kdc.conf.5 b/usr/src/man/man5/kdc.conf.5 index 5575946bf4..9a4fe87f4a 100644 --- a/usr/src/man/man5/kdc.conf.5 +++ b/usr/src/man/man5/kdc.conf.5 @@ -518,7 +518,7 @@ Kerberos. .RS 4n This boolean specifies whether the list of transited realms for cross-realm tickets should be checked against the transit path computed from the realm -names and the \fB[capaths]\fR section of its \fBkrb5.conf\fR(4) file. +names and the \fB[capaths]\fR section of its \fBkrb5.conf\fR(5) file. .sp The default for \fBreject_bad_transit\fR is \fBtrue\fR. .RE @@ -1054,7 +1054,7 @@ Kerberos administration server logging file. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -1074,6 +1074,6 @@ All of the keywords, except for the \fBPKINIT\fR keywords are Committed. The .SH SEE ALSO .sp .LP -\fBkpasswd\fR(1), \fBkadmind\fR(1M), \fBkadmin.local\fR(1M), -\fBkdb5_util\fR(1M), \fBkpropd\fR(1M), \fBlibpkcs11\fR(3LIB), \fBsyslog\fR(3C), -\fBkadm5.acl\fR(4), \fBkrb5.conf\fR(4), \fBattributes\fR(5), \fBkerberos\fR(5) +\fBkpasswd\fR(1), \fBkadmind\fR(8), \fBkadmin.local\fR(8), +\fBkdb5_util\fR(8), \fBkpropd\fR(8), \fBlibpkcs11\fR(3LIB), \fBsyslog\fR(3C), +\fBkadm5.acl\fR(5), \fBkrb5.conf\fR(5), \fBattributes\fR(7), \fBkerberos\fR(7) diff --git a/usr/src/man/man5/krb5.conf.5 b/usr/src/man/man5/krb5.conf.5 index 049ccebbdd..e8e7a8695c 100644 --- a/usr/src/man/man5/krb5.conf.5 +++ b/usr/src/man/man5/krb5.conf.5 @@ -239,7 +239,7 @@ realm. This relation controls the encryption types for session keys permitted by server applications that use Kerberos for authentication. In addition, it controls the encryption types of keys added to a \fBkeytab\fR by means of the -\fBkadmin\fR(1M) \fBktadd\fR command. The default is: +\fBkadmin\fR(8) \fBktadd\fR command. The default is: \fBaes256-cts-hmac-sha1-96\fR, \fBaes128-cts-hmac-sha1-96\fR, \fBdes3-hmac-sha1-kd\fR, \fBarcfour-hmac-md5\fR, \fBarcfour-hmac-md5-exp\fR, \fBdes-cbc-md5\fR, \fBdes-cbc-crc\fR. @@ -731,7 +731,7 @@ Where: .fi .in -2 -Regular expressions are defined in \fBregex\fR(5). +Regular expressions are defined in \fBregex\fR(7). .sp For example: .sp @@ -1737,7 +1737,7 @@ Each server URI should be separated by whitespace. .RS 4n File containing stashed passwords used by the KDC when binding to the LDAP Directory Server. The default is \fB/var/krb5/service_passwd\fR. This file is -created using \fBkdb5_ldap_util\fR(1M). +created using \fBkdb5_ldap_util\fR(8). .RE .sp @@ -1829,7 +1829,7 @@ a Kerberos configuration file when the KDC is using the LDAP KDB plug-in. .RE .SH ATTRIBUTES -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -1848,8 +1848,8 @@ All of the keywords are Committed, except for the \fBPKINIT\fR keywords, which are Volatile. .SH SEE ALSO \fBkinit\fR(1), \fBrcp\fR(1), \fBrdist\fR(1), \fBrlogin\fR(1), \fBrsh\fR(1), -\fBtelnet\fR(1), \fBsyslog\fR(3C), \fBattributes\fR(5), \fBkerberos\fR(5), -\fBregex\fR(5) +\fBtelnet\fR(1), \fBsyslog\fR(3C), \fBattributes\fR(7), \fBkerberos\fR(7), +\fBregex\fR(7) .SH NOTES If the \fBkrb5.conf\fR file is not formatted properly, the \fBtelnet\fR command fails. However, the \fBdtlogin\fR and \fBlogin\fR commands still succeed, even diff --git a/usr/src/man/man5/ldapfilter.conf.5 b/usr/src/man/man5/ldapfilter.conf.5 index 176136db6c..dcb00d3c49 100644 --- a/usr/src/man/man5/ldapfilter.conf.5 +++ b/usr/src/man/man5/ldapfilter.conf.5 @@ -164,7 +164,7 @@ example1 .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for a description of the following attributes: +See \fBattributes\fR(7) for a description of the following attributes: .sp .sp @@ -179,4 +179,4 @@ Stability Level Evolving .SH SEE ALSO .sp .LP -\fBldap_getfilter\fR(3LDAP), \fBldap_ufn\fR(3LDAP), \fBattributes\fR(5) +\fBldap_getfilter\fR(3LDAP), \fBldap_ufn\fR(3LDAP), \fBattributes\fR(7) diff --git a/usr/src/man/man5/ldapsearchprefs.conf.5 b/usr/src/man/man5/ldapsearchprefs.conf.5 index d21491e04e..4ba2d5bed5 100644 --- a/usr/src/man/man5/ldapsearchprefs.conf.5 +++ b/usr/src/man/man5/ldapsearchprefs.conf.5 @@ -259,10 +259,10 @@ END .sp .LP In this example, the user may search for People. For "fewer choices" searching, -the tag for the \fBldapfilter.conf\fR(4) file is "x500-People". +the tag for the \fBldapfilter.conf\fR(5) file is "x500-People". .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for a description of the following attributes: +See \fBattributes\fR(7) for a description of the following attributes: .sp .sp @@ -276,4 +276,4 @@ Stability Level Evolving .SH SEE ALSO .LP -\fBldap_searchprefs\fR(3LDAP), \fBattributes\fR(5) +\fBldap_searchprefs\fR(3LDAP), \fBattributes\fR(7) diff --git a/usr/src/man/man5/ldaptemplates.conf.5 b/usr/src/man/man5/ldaptemplates.conf.5 index 8d4364a73d..52b7666d0a 100644 --- a/usr/src/man/man5/ldaptemplates.conf.5 +++ b/usr/src/man/man5/ldaptemplates.conf.5 @@ -414,7 +414,7 @@ people entries. .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for a description of the following attributes: +See \fBattributes\fR(7) for a description of the following attributes: .sp .sp @@ -428,4 +428,4 @@ Stability Level Evolving .SH SEE ALSO .LP -\fBldap_disptmpl\fR(3LDAP), \fBldap_entry2text\fR(3LDAP), \fBattributes\fR(5) +\fBldap_disptmpl\fR(3LDAP), \fBldap_entry2text\fR(3LDAP), \fBattributes\fR(7) diff --git a/usr/src/man/man5/logadm.conf.5 b/usr/src/man/man5/logadm.conf.5 index 58406cf426..38893f2332 100644 --- a/usr/src/man/man5/logadm.conf.5 +++ b/usr/src/man/man5/logadm.conf.5 @@ -16,7 +16,7 @@ logadm.conf \- configuration file for logadm command .sp .LP \fB/etc/logadm.conf\fR is the default configuration file for the log management -tool \fBlogadm\fR(1M). Comments are allowed using the pound character (\fB#\fR) +tool \fBlogadm\fR(8). Comments are allowed using the pound character (\fB#\fR) and extend to the end of line. Each non-comment line has the form: .sp .in +2 @@ -36,22 +36,22 @@ quotes may be used to protect spaces or alternate-style quotes in strings. .sp .LP The preferred method for changing \fB/etc/logadm.conf\fR is to use the -\fB-V\fR, \fB-w\fR, and \fB-r\fR options to the \fBlogadm\fR(1M) command, which +\fB-V\fR, \fB-w\fR, and \fB-r\fR options to the \fBlogadm\fR(8) command, which allow you to lookup an entry, write an entry, or remove an entry from \fB/etc/logadm.conf\fR. .sp .LP A full description of how and when \fB/etc/logadm.conf\fR is used and sample -entries are found in \fBlogadm\fR(1M). +entries are found in \fBlogadm\fR(8). .sp .LP -By default, \fBlogadm\fR(1M) works in \fBGMT\fR. Therefore, all entries in +By default, \fBlogadm\fR(8) works in \fBGMT\fR. Therefore, all entries in \fB/etc/logadm.conf\fR will have a \fBGMT\fR timestamp. Users can use the \fB-l\fR option to set \fBlogadm\fR to local time. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -67,4 +67,4 @@ Interface Stability Evolving .SH SEE ALSO .sp .LP -\fBlogadm\fR(1M), \fBattributes\fR(5) +\fBlogadm\fR(8), \fBattributes\fR(7) diff --git a/usr/src/man/man5/logindevperm.5 b/usr/src/man/man5/logindevperm.5 index fdd64b202d..ec1714e210 100644 --- a/usr/src/man/man5/logindevperm.5 +++ b/usr/src/man/man5/logindevperm.5 @@ -16,7 +16,7 @@ logindevperm, fbtab \- login-based device permissions .sp .LP The \fB/etc/logindevperm\fR file contains information that is used by -\fBlogin\fR(1) and \fBttymon\fR(1M) to change the owner, group, and permissions +\fBlogin\fR(1) and \fBttymon\fR(8) to change the owner, group, and permissions of devices upon logging into or out of a console device. By default, this file contains lines for the keyboard, mouse, audio, and frame buffer devices. .sp @@ -30,7 +30,7 @@ specified in \fB/etc/logindevperm\fR. If the console is \fB/dev/vt/active\fR, the owner of the devices is the first user logged in on the consoles (\fB/dev/console\fR or \fB/dev/vt/#\fR). Upon this first user's logout the owner and group of these devices is reset by -\fBttymon\fR(1M) to owner root and root's group as specified in +\fBttymon\fR(8) to owner root and root's group as specified in \fB/etc/passwd\fR. .sp .LP @@ -61,7 +61,7 @@ A fully qualified name, for example, \fBfbs\fR. .TP .ie t \(bu .el o -A regular expression, for example, \fB[a-z0-9.]+\fR. See \fBregexp\fR(5) for +A regular expression, for example, \fB[a-z0-9.]+\fR. See \fBregexp\fR(7) for more information on regular expressions. .RE .RS +4 @@ -86,7 +86,7 @@ Some examples of \fB/etc/logindevperm\fR file entries include: .sp .LP -Specify all \fBugen\fR(7D) endpoints and status nodes. +Specify all \fBugen\fR(4D) endpoints and status nodes. .sp .LP Drivers can also be specified to limit the permission changes to minor nodes @@ -101,7 +101,7 @@ driver=usb_mid,scsa2usb,usbprn # libusb devices .sp .LP -Due to the persistence of \fBdevfs\fR(7FS) minor node management, the user +Due to the persistence of \fBdevfs\fR(4FS) minor node management, the user should be logged in as root if the list of minor nodes will be reduced and the devices should all be plugged in. .sp @@ -111,7 +111,7 @@ changed using \fBchmod\fR(1) and \fBchown\fR(1), as with any other user-owned file. .sp .LP -Upon logout the owner and group of these devices are reset by \fBttymon\fR(1M) +Upon logout the owner and group of these devices are reset by \fBttymon\fR(8) to owner \fBroot\fR and root's group as specified in \fB/etc/passwd\fR (typically \fBother\fR). The permissions are set as specified in the \fB/etc/logindevperm\fR file. @@ -128,8 +128,8 @@ File that contains user group information. .SH SEE ALSO .sp .LP -\fBchmod\fR(1), \fBchown\fR(1), \fBlogin\fR(1), \fBttymon\fR(1M), -\fBpasswd\fR(4), \fBregexp\fR(5), \fBugen\fR(7D) +\fBchmod\fR(1), \fBchown\fR(1), \fBlogin\fR(1), \fBttymon\fR(8), +\fBpasswd\fR(5), \fBregexp\fR(7), \fBugen\fR(4D) .SH NOTES .sp .LP diff --git a/usr/src/man/man5/mnttab.5 b/usr/src/man/man5/mnttab.5 index 6411bd6cdc..0c21286739 100644 --- a/usr/src/man/man5/mnttab.5 +++ b/usr/src/man/man5/mnttab.5 @@ -82,7 +82,7 @@ The time at which the file system was mounted. Examples of entries for the \fIspecial\fR field include the pathname of a block-special device, the name of a remote file system in the form of \fIhost:pathname\fR, or the name of a \fBswap file\fR, for example, a file made -with \fBmkfile\fR(1M). +with \fBmkfile\fR(8). .SH IOCTLS .LP The following \fBioctl\fR(2) calls are supported: @@ -212,8 +212,8 @@ Header file that contains \fBIOCTL\fR definitions .SH SEE ALSO .LP -\fBmkfile\fR(1M), \fBmount_hsfs\fR(1M), \fBmount_nfs\fR(1M), -\fBmount_pcfs\fR(1M), \fBmount_ufs\fR(1M), \fBmount\fR(1M), +\fBmkfile\fR(8), \fBmount_hsfs\fR(8), \fBmount_nfs\fR(8), +\fBmount_pcfs\fR(8), \fBmount_ufs\fR(8), \fBmount\fR(8), \fBioctl\fR(2), \fBread\fR(2), \fBpoll\fR(2), \fBstat\fR(2), \fBgetmntent\fR(3C) .SH WARNINGS diff --git a/usr/src/man/man5/mpapi.conf.5 b/usr/src/man/man5/mpapi.conf.5 index 91b4ba6644..4bb60ee158 100644 --- a/usr/src/man/man5/mpapi.conf.5 +++ b/usr/src/man/man5/mpapi.conf.5 @@ -77,7 +77,7 @@ com.sun.mpapi64 /lib/64/libmpscsi_vhci.so .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -95,4 +95,4 @@ T} .SH SEE ALSO .LP \fBlibMPAPI\fR(3LIB), \fBMP_DeregisterPlugin\fR(3MPAPI), -\fBMP_RegisterPlugin\fR(3MPAPI), \fBattributes\fR(5) +\fBMP_RegisterPlugin\fR(3MPAPI), \fBattributes\fR(7) diff --git a/usr/src/man/man5/nca.if.5 b/usr/src/man/man5/nca.if.5 index cbf18e9798..f9db7b624a 100644 --- a/usr/src/man/man5/nca.if.5 +++ b/usr/src/man/man5/nca.if.5 @@ -25,7 +25,7 @@ backed by a \fBhostname.{interface_name}\fR, then list only an asterik .LP When the \fBncakmod\fR(1) initialization script is invoked during system boot, it will attempt to configure each physical interface specified in the -\fBnca.if\fR file by using \fBncaconfd\fR(1M). Note that there must be an +\fBnca.if\fR file by using \fBncaconfd\fR(8). Note that there must be an accompanying \fBhostname.{interface_name}\fR file and an entry in \fB/etc/hosts\fR for the contents of \fBhostname.{interface_name}\fR. .sp @@ -114,7 +114,7 @@ match with entries in \fB/etc/hostname.{}{0-9}\fR for \fBNCA\fR to function. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -130,8 +130,8 @@ Interface Stability Evolving .SH SEE ALSO .sp .LP -\fBnca\fR(1), \fBncab2clf\fR(1), \fBncakmod\fR(1), \fBifconfig\fR(1M), -\fBncakmod.conf\fR(4), \fBncalogd.conf\fR(4), \fBattributes\fR(5) +\fBnca\fR(1), \fBncab2clf\fR(1), \fBncakmod\fR(1), \fBifconfig\fR(8), +\fBncakmod.conf\fR(5), \fBncalogd.conf\fR(5), \fBattributes\fR(7) .sp .LP \fISystem Administration Guide: IP Services\fR diff --git a/usr/src/man/man5/ncad_addr.5 b/usr/src/man/man5/ncad_addr.5 index 2abbd58f7d..13fabd618c 100644 --- a/usr/src/man/man5/ncad_addr.5 +++ b/usr/src/man/man5/ncad_addr.5 @@ -52,7 +52,7 @@ LD_PRELOAD=/usr/lib/ncad_addr.so /usr/bin/httpd .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -68,7 +68,7 @@ Interface Stability Unstable .SH SEE ALSO .LP \fBnca\fR(1), \fBncab2clf\fR(1), \fBncakmod\fR(1), \fBsocket\fR(3SOCKET), -\fBnca.if\fR(4), \fBncakmod.conf\fR(4), \fBattributes\fR(5) +\fBnca.if\fR(5), \fBncakmod.conf\fR(5), \fBattributes\fR(7) .SH NOTES .LP Only applications that use the \fBNCA\fR feature, for example, web servers, diff --git a/usr/src/man/man5/ncakmod.conf.5 b/usr/src/man/man5/ncakmod.conf.5 index 1f9b6f9300..c5519c2d5e 100644 --- a/usr/src/man/man5/ncakmod.conf.5 +++ b/usr/src/man/man5/ncakmod.conf.5 @@ -42,7 +42,7 @@ to NCA. A web server that uses the sockets interface with \fBPF_NCA\fR or \fBncad_addr.so\fR cannot connect by means of \fBnca_active\fR. .sp .LP -NCA supports the logging of in-kernel cache hits. See \fBncalogd.conf\fR(4). +NCA supports the logging of in-kernel cache hits. See \fBncalogd.conf\fR(5). NCA stores logs in a binary format. Use the \fBncab2clf\fR(1) utility to convert the log from a binary format to the Common Log File format. .sp @@ -81,7 +81,7 @@ The NCA kernel module configuration file. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -98,7 +98,7 @@ Interface Stability Evolving .sp .LP \fBnca\fR(1), \fBncab2clf\fR(1), \fBncakmod\fR(1), \fBdoor_create\fR(3C), -\fBnca.if\fR(4), \fBncad_addr\fR(4), \fBncalogd.conf\fR(4), \fBattributes\fR(5) +\fBnca.if\fR(5), \fBncad_addr\fR(5), \fBncalogd.conf\fR(5), \fBattributes\fR(7) .sp .LP \fISystem Administration Guide: IP Services\fR diff --git a/usr/src/man/man5/ncalogd.conf.5 b/usr/src/man/man5/ncalogd.conf.5 index 7ef0b7b8c2..768666d179 100644 --- a/usr/src/man/man5/ncalogd.conf.5 +++ b/usr/src/man/man5/ncalogd.conf.5 @@ -89,7 +89,7 @@ Lists configuration parameters for \fBNCA\fRlogging. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -105,9 +105,9 @@ Interface Stability Evolving .SH SEE ALSO .sp .LP -\fBnca\fR(1), \fBncab2clf\fR(1), \fBncakmod\fR(1), \fBdd\fR(1M), -\fBdoor_create\fR(3C), \fBnca.if\fR(4), \fBncakmod.conf\fR(4), -\fBattributes\fR(5) +\fBnca\fR(1), \fBncab2clf\fR(1), \fBncakmod\fR(1), \fBdd\fR(8), +\fBdoor_create\fR(3C), \fBnca.if\fR(5), \fBncakmod.conf\fR(5), +\fBattributes\fR(7) .sp .LP \fISystem Administration Guide: IP Services\fR diff --git a/usr/src/man/man5/ncaport.conf.5 b/usr/src/man/man5/ncaport.conf.5 index 2e24b4dce4..b19f146997 100644 --- a/usr/src/man/man5/ncaport.conf.5 +++ b/usr/src/man/man5/ncaport.conf.5 @@ -27,7 +27,7 @@ which matches any IP address. A web server uses the environment variable \fBLD_PRELOAD\fR and the \fBncaport.conf\fR configuration file to convert an \fBAF_INET\fR socket to an \fBAF_NCA\fR socket. \fBLD_PRELOAD\fR enables the NCA socket utility library to -be loaded before \fBlibsocket.so.1\fR. See the \fBncad_addr\fR(4) for details. +be loaded before \fBlibsocket.so.1\fR. See the \fBncad_addr\fR(5) for details. When a web server issues the \fBbind\fR(3SOCKET) system call, it is intercepted by the interposition library \fBncad_addr.so\fR. If the bind address is in the \fBncaport.conf\fR file, the \fBAF_INET\fR socket is converted to a @@ -55,7 +55,7 @@ ncaport=*/9000 .SH SEE ALSO .LP \fBnca\fR(1), \fBbind\fR(3SOCKET), \fBinet_pton\fR(3C), -\fBncad_addr\fR(4), \fBattributes\fR(5) +\fBncad_addr\fR(5), \fBattributes\fR(7) .SH NOTES .LP For those web servers that use \fBAF_NCA\fR sockets, the NCA port configuration diff --git a/usr/src/man/man5/ndmp.5 b/usr/src/man/man5/ndmp.5 index 7afa7fe284..4b3d82a65a 100644 --- a/usr/src/man/man5/ndmp.5 +++ b/usr/src/man/man5/ndmp.5 @@ -12,10 +12,10 @@ ndmp \- configuration properties for Solaris Network Data Management Protocol .sp .LP The behavior of the Solaris NDMP server is specified by property values that -are stored in the Service Management Facility, \fBsmf\fR(5). +are stored in the Service Management Facility, \fBsmf\fR(7). .sp .LP -An authorized user can use the \fBndmpadm\fR(1M) command to set global values +An authorized user can use the \fBndmpadm\fR(8) command to set global values for these properties in SMF. .sp .LP @@ -154,7 +154,7 @@ values are \fBcram-md5\fR or \fBcleartext\fR. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -170,5 +170,5 @@ Interface Stability Committed .SH SEE ALSO .sp .LP -\fBdump\fR(1), \fBtar\fR(1), \fBndmpadm\fR(1M), \fBndmpd\fR(1M), -\fBattributes\fR(5), \fBsmf\fR(5) +\fBdump\fR(1), \fBtar\fR(1), \fBndmpadm\fR(8), \fBndmpd\fR(8), +\fBattributes\fR(7), \fBsmf\fR(7) diff --git a/usr/src/man/man5/ndpd.conf.5 b/usr/src/man/man5/ndpd.conf.5 index 7338bb978d..8098b66a94 100644 --- a/usr/src/man/man5/ndpd.conf.5 +++ b/usr/src/man/man5/ndpd.conf.5 @@ -16,7 +16,7 @@ ndpd.conf \- configuration file for IPv6 router autoconfiguration .sp .LP The \fBndpd.conf\fR file contains configuration information for -\fBin.ndpd\fR(1M). On a host, this file does not need to exist or can be empty. +\fBin.ndpd\fR(8). On a host, this file does not need to exist or can be empty. The file has one configuration entry per line; note that lines can be extended with a backslash (\fB\e\fR) followed by a NEWLINE. There are four forms of configuration entries which are identified by the first field on the line: @@ -282,7 +282,7 @@ Stateful Address Autoconfiguration mechanism, also known as DHCPv6, as described in RFC 3315. If enabled (the default), hosts automatically run DHCPv6 based on the "managed" and "other" flags sent by routers. If disabled, \fBin.ndpd\fR will not invoke DHCPv6 automatically. DHCPv6 can still be invoked -manually by using \fBifconfig\fR(1M), in which case \fBin.ndpd\fR automatically +manually by using \fBifconfig\fR(8), in which case \fBin.ndpd\fR automatically sets the prefix length as needed. .RE @@ -513,7 +513,7 @@ prefix fec0:0:0:9259::0/64 eri2 .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -529,8 +529,8 @@ Interface Stability Committed .SH SEE ALSO .sp .LP -\fBdhcpagent\fR(1M), \fBifconfig\fR(1M), \fBin.ndpd\fR(1M), \fBrouteadm\fR(1M), -\fBattributes\fR(5), \fBicmp6\fR(7P), \fBip6\fR(7P) +\fBdhcpagent\fR(8), \fBifconfig\fR(8), \fBin.ndpd\fR(8), \fBrouteadm\fR(8), +\fBattributes\fR(7), \fBicmp6\fR(4P), \fBip6\fR(4P) .sp .LP Narten, T., Nordmark, E., and Simpson, W. \fIRFC 2461, Neighbor Discovery for diff --git a/usr/src/man/man5/netconfig.5 b/usr/src/man/man5/netconfig.5 index 144a9178b4..4a028858cc 100644 --- a/usr/src/man/man5/netconfig.5 +++ b/usr/src/man/man5/netconfig.5 @@ -23,7 +23,7 @@ to store information about networks that are connected to the system. The Network Selection component also includes \fBgetnetpath\fR(3NSL) routines to provide application-specific network search paths. These routines access the \fBnetconfig\fR database based on the environment variable \fBNETPATH\fR. See -\fBenviron\fR(5). +\fBenviron\fR(7). .sp .LP \fBnetconfig\fR contains an entry for each network available on the system. @@ -406,7 +406,7 @@ The \fIname-to-address translation libraries\fR support a ``directory service'' field indicates the absence of any \fItranslation libraries\fR. This has a special meaning for networks of the protocol family \fBinet :\fR its name-to-address mapping is provided by the name service switch based on the -entries for \fBhosts\fR and \fBservices\fR in \fBnsswitch.conf\fR(4). For +entries for \fBhosts\fR and \fBservices\fR in \fBnsswitch.conf\fR(5). For networks of other families, a ``\fB\(mi\fR\&'' indicates non-functional name-to-address mapping. Otherwise, this field consists of a comma-separated list of pathnames to dynamically linked libraries. The pathname of the library @@ -578,7 +578,7 @@ ticots tpi_cots v loopback - /dev/ticots straddr.so .sp .LP \fBdlopen\fR(3C), \fBgetnetconfig\fR(3NSL), \fBgetnetpath\fR(3NSL), -\fBnsswitch.conf\fR(4) +\fBnsswitch.conf\fR(5) .sp .LP \fISystem Administration Guide: IP Services\fR diff --git a/usr/src/man/man5/netgroup.5 b/usr/src/man/man5/netgroup.5 index f5b00eed8c..43f62a5c10 100644 --- a/usr/src/man/man5/netgroup.5 +++ b/usr/src/man/man5/netgroup.5 @@ -19,10 +19,10 @@ restrict remote login and shell access. Network groups are usually stored in network information services, such as \fBLDAP\fR, or \fBNIS\fR, but may alternatively be stored in the local \fB/etc/netgroup\fR file. The \fBnetgroup\fR line of the -\fBnsswitch.conf\fR(4) file determines which of those sources are used. +\fBnsswitch.conf\fR(5) file determines which of those sources are used. .sp This manual page describes the format for a file that is used to supply input -to a program such as \fBldapaddent\fR(1M) for LDAP, or \fBmakedbm\fR(1M) for +to a program such as \fBldapaddent\fR(8) for LDAP, or \fBmakedbm\fR(8) for NIS. The same file format is used in the local \fB/etc/netgroup\fR file. .sp Each line of the file defines the name and membership of a network group. The @@ -85,9 +85,9 @@ is equivalent to .sp .sp You can also use netgroups to control \fBNFS\fR mount access (see -\fBshare_nfs\fR(1M)) and to control remote login and shell access (see -\fBhosts.equiv\fR(4)). You can also use them to control local login access (see -\fBpasswd\fR(4), \fBshadow\fR(4), and \fBcompat\fR in \fBnsswitch.conf\fR(4)). +\fBshare_nfs\fR(8)) and to control remote login and shell access (see +\fBhosts.equiv\fR(5)). You can also use them to control local login access (see +\fBpasswd\fR(5), \fBshadow\fR(5), and \fBcompat\fR in \fBnsswitch.conf\fR(5)). .sp When used for these purposes, a host is considered a member of a \fBnetgroup\fR if the \fBnetgroup\fR contains any triple in which the \fBhostname\fR field @@ -110,16 +110,16 @@ basis of host and user membership in separate netgroups. .ad .RS 17n Used by a network information service's utility to construct a map or table -that contains \fBnetgroup\fR information. For example, \fBldapaddent\fR(1M) +that contains \fBnetgroup\fR information. For example, \fBldapaddent\fR(8) uses \fB/etc/netgroup\fR to construct an LDAP container. Alternatively, the \fB/etc/netgroup\fR file may be used directly if the \fBfiles\fR -source is specified in \fBnsswitch.conf\fR(4) for the \fBnetgroup\fR +source is specified in \fBnsswitch.conf\fR(5) for the \fBnetgroup\fR database. .RE .SH SEE ALSO -\fBldapaddent\fR(1M), \fBmakedbm\fR(1M), -\fBshare_nfs\fR(1M), \fBinnetgr\fR(3C), \fBhosts\fR(4), \fBhosts.equiv\fR(4), -\fBnsswitch.conf\fR(4), \fBpasswd\fR(4), \fBshadow\fR(4) +\fBldapaddent\fR(8), \fBmakedbm\fR(8), +\fBshare_nfs\fR(8), \fBinnetgr\fR(3C), \fBhosts\fR(5), \fBhosts.equiv\fR(5), +\fBnsswitch.conf\fR(5), \fBpasswd\fR(5), \fBshadow\fR(5) .SH NOTES Applications may make general membership tests using the \fBinnetgr()\fR function. See \fBinnetgr\fR(3C). @@ -143,7 +143,7 @@ hostname will also suffice for this purpose. Use of placeholders will improve search performance. .sp When a machine with multiple interfaces and multiple names is defined as a -member of a \fBnetgroup\fR, one must list all of the names. See \fBhosts\fR(4). +member of a \fBnetgroup\fR, one must list all of the names. See \fBhosts\fR(5). A manageable way to do this is to define a \fBnetgroup\fR containing all of the machine names. For example, for a host "gateway" that has names "gateway-subnet1" and "gateway-subnet2" one may define the \fBnetgroup\fR: diff --git a/usr/src/man/man5/netid.5 b/usr/src/man/man5/netid.5 index 70b331ca1e..d58c682441 100644 --- a/usr/src/man/man5/netid.5 +++ b/usr/src/man/man5/netid.5 @@ -17,7 +17,7 @@ The \fBnetid\fR file is a local source of information on mappings between netnames (see \fBsecure_rpc\fR(3NSL)) and user ids or hostnames in the local domain. The \fBnetid\fR file can be used in conjunction with, or instead of, a network nameservice. The \fBpublickey\fR entry in -the \fBnsswitch.conf\fR (see \fBnsswitch.conf\fR(4)) file determines which of +the \fBnsswitch.conf\fR (see \fBnsswitch.conf\fR(5)) file determines which of these sources will be queried by the system to translate netnames to local user ids or hostnames. .sp @@ -78,7 +78,7 @@ domain name. \fB\fIuid\fR\fR .ad .RS 12n -The numerical id of the user (see \fBpasswd\fR(4)). When specifying a host +The numerical id of the user (see \fBpasswd\fR(5)). When specifying a host name, \fIuid\fR is always zero. .RE @@ -88,7 +88,7 @@ name, \fIuid\fR is always zero. \fB\fIgroup\fR\fR .ad .RS 12n -The numerical id of the group the user belongs to (see \fBgroup\fR(4)). +The numerical id of the group the user belongs to (see \fBgroup\fR(5)). Several groups, separated by commas, may be listed for a single \fIuid\fR. .RE @@ -98,7 +98,7 @@ Several groups, separated by commas, may be listed for a single \fIuid\fR. \fB\fBhostname\fR\fR .ad .RS 12n -The local hostname (see \fBhosts\fR(4)). +The local hostname (see \fBhosts\fR(5)). .RE .sp @@ -167,5 +167,5 @@ public key database .RE .SH SEE ALSO -\fBnetname2user\fR(3NSL), \fBsecure_rpc\fR(3NSL), \fBgroup\fR(4), -\fBhosts\fR(4), \fBnsswitch.conf\fR(4), \fBpasswd\fR(4), \fBpublickey\fR(4) +\fBnetname2user\fR(3NSL), \fBsecure_rpc\fR(3NSL), \fBgroup\fR(5), +\fBhosts\fR(5), \fBnsswitch.conf\fR(5), \fBpasswd\fR(5), \fBpublickey\fR(5) diff --git a/usr/src/man/man5/netmasks.5 b/usr/src/man/man5/netmasks.5 index 7b6fdae96a..d4f7dbdcbf 100644 --- a/usr/src/man/man5/netmasks.5 +++ b/usr/src/man/man5/netmasks.5 @@ -57,7 +57,7 @@ sixteen bits in the network field. When using variable length subnetting, the format is identical. However, there should be a line for each subnet with the first field being the subnet and the second field being the netmask that applies to that subnet. The users of the -database, such as \fBifconfig\fR(1M), perform a lookup to find the longest +database, such as \fBifconfig\fR(8), perform a lookup to find the longest possible matching mask. It is possible to combine the \fIRFC-950\fR and \fIRFC-1519\fR form of subnet masks in the netmasks file. For example, .sp @@ -109,7 +109,7 @@ Invalid entries are ignored. .SH SEE ALSO .sp .LP -\fBifconfig\fR(1M), \fBinet\fR(7P) +\fBifconfig\fR(8), \fBinet\fR(4P) .sp .LP Postel, Jon, and Mogul, Jeff, \fIInternet Standard Subnetting Procedure\fR, diff --git a/usr/src/man/man5/networks.5 b/usr/src/man/man5/networks.5 index 54f7b84934..61aca509b2 100644 --- a/usr/src/man/man5/networks.5 +++ b/usr/src/man/man5/networks.5 @@ -49,12 +49,12 @@ it up to date regarding unofficial aliases and/or unknown networks. .LP Network numbers may be specified in the conventional dot (`\fB\&.\fR') notation using the \fBinet_network\fR routine from the Internet address manipulation -library, \fBinet\fR(7P). Network names may contain any printable character +library, \fBinet\fR(4P). Network names may contain any printable character other than a field delimiter, \fBNEWLINE\fR, or comment character. .SH SEE ALSO .LP \fBgetnetbyaddr\fR(3SOCKET), \fBgetnetbyname\fR(3SOCKET), \fBinet\fR(3SOCKET), -\fBnsswitch.conf\fR(4), \fBinet\fR(7P) +\fBnsswitch.conf\fR(5), \fBinet\fR(4P) .SH NOTES .LP The official SVR4 name of the \fBnetworks\fR file is \fB/etc/inet/networks\fR. @@ -67,5 +67,5 @@ address \fB24.132.47.86\fR that has a mask of \fBfffffe00\fR, its network number is \fB803351\fR. This is obtained when the address is shifted right by 9 bits. The address maps to \fB12.66.23\fR. The trailing 0 bits should not be specified. The network number here is different from that described in -\fBnetmasks\fR(4). For this example, the entry in \fBnetmasks\fR would be +\fBnetmasks\fR(5). For this example, the entry in \fBnetmasks\fR would be \fB24.132.46.0 fffffe00\fR. diff --git a/usr/src/man/man5/nfs.5 b/usr/src/man/man5/nfs.5 index b9c88871f2..d53d7bfe98 100644 --- a/usr/src/man/man5/nfs.5 +++ b/usr/src/man/man5/nfs.5 @@ -36,7 +36,7 @@ and daemons and .Xr mount_nfs 8 command is controlled by property values that are stored in the Service -Management Facility, smf(5). +Management Facility, smf(7). The .Xr sharectl 8 command should be used to query or change values for these properties. diff --git a/usr/src/man/man5/nfslog.conf.5 b/usr/src/man/man5/nfslog.conf.5 index ba21bab32e..8f4e475811 100644 --- a/usr/src/man/man5/nfslog.conf.5 +++ b/usr/src/man/man5/nfslog.conf.5 @@ -17,14 +17,14 @@ nfslog.conf \- NFS server logging configuration file .LP The \fBnfslog.conf\fR file specifies the location of the \fBNFS\fR server logs, as well as the location of the private work files used by the \fBNFS\fR server -and \fBnfslogd\fR(1M) daemon during logging. Each entry in the file consists of +and \fBnfslogd\fR(8) daemon during logging. Each entry in the file consists of a mandatory tag identifier and one or more parameter identifiers. The parameter identifier specifies the value or location of the specific parameter. For instance, the parameter identifier "\fBlog=/var/nfs/logs/serverLog\fR" specifies the location of the \fBNFS\fR server activity log. The mandatory tag identifier serves as an index into the \fB/etc/nfs/nfslog.conf\fR file to identify the various parameters to be used. At export time, the -\fBshare_nfs\fR(1M) command specifies the \fBNFS\fR server logging parameters +\fBshare_nfs\fR(8) command specifies the \fBNFS\fR server logging parameters to use by associating a tag from the \fB/etc/nfs/nfslog.conf\fR file to the exported file system. It is legal for more than one file system to be exported using the same logging tag identifier. @@ -83,7 +83,7 @@ Specifies the location of the private file handle to path mapping database files. These database files are for the private use of the \fBNFS\fR server kernel module and the \fBnfslog\fRd daemon. These files will be located in the \fBdefaultdir\fR, unless \fB<path>\fR is an absolute path. These database files -are permanently stored in the file system. Consult \fBnfslogd\fR(1M) for +are permanently stored in the file system. Consult \fBnfslogd\fR(8) for information on pruning the database files. .RE @@ -168,11 +168,11 @@ global settings. .SH SEE ALSO .sp .LP -\fBnfslogd\fR(1M), \fBshare_nfs\fR(1M), \fBattributes\fR(5) +\fBnfslogd\fR(8), \fBshare_nfs\fR(8), \fBattributes\fR(7) .SH NOTES .sp .LP Logs, work files, and file handle to path mapping database can become very large. Be aware of appropriate placement within the file system name space. See -\fBnfslogd\fR(1M)) for information on pruning the database files and cycling +\fBnfslogd\fR(8)) for information on pruning the database files and cycling logs. diff --git a/usr/src/man/man5/nfssec.conf.5 b/usr/src/man/man5/nfssec.conf.5 index 5262da34ae..1cb5cf9b61 100644 --- a/usr/src/man/man5/nfssec.conf.5 +++ b/usr/src/man/man5/nfssec.conf.5 @@ -16,11 +16,11 @@ nfssec.conf \- list NFS security modes .sp .LP The \fBnfssec.conf\fR file lists the NFS security modes supported on a system. -These modes are defined in \fBnfssec\fR(5). +These modes are defined in \fBnfssec\fR(7). .sp .LP The \fBnfssec.conf\fR file should not be edited by a user. .SH SEE ALSO .sp .LP -\fBnfssec\fR(5) +\fBnfssec\fR(7) diff --git a/usr/src/man/man5/nodename.5 b/usr/src/man/man5/nodename.5 index 0157819ae4..b77d4d4668 100644 --- a/usr/src/man/man5/nodename.5 +++ b/usr/src/man/man5/nodename.5 @@ -56,8 +56,8 @@ myhost .SH SEE ALSO .LP -\fBuname\fR(1), \fBnamed\fR(1M), \fBypbind\fR(1M), -\fBattributes\fR(5) +\fBuname\fR(1), \fBnamed\fR(8), \fBypbind\fR(8), +\fBattributes\fR(7) .SH NOTES .LP The \fBnodename\fR file is modified by Solaris installation and de-installation diff --git a/usr/src/man/man5/nologin.5 b/usr/src/man/man5/nologin.5 index 4e050cbe50..45fc852f08 100644 --- a/usr/src/man/man5/nologin.5 +++ b/usr/src/man/man5/nologin.5 @@ -37,4 +37,4 @@ typical \fBnologin\fR file contains a message similar to: .SH SEE ALSO .sp .LP -\fBlogin\fR(1), \fBrlogin\fR(1), \fBtelnet\fR(1), \fBshutdown\fR(1M) +\fBlogin\fR(1), \fBrlogin\fR(1), \fBtelnet\fR(1), \fBshutdown\fR(8) diff --git a/usr/src/man/man5/notrouter.5 b/usr/src/man/man5/notrouter.5 index 4643d7b1ae..0689a809e5 100644 --- a/usr/src/man/man5/notrouter.5 +++ b/usr/src/man/man5/notrouter.5 @@ -17,8 +17,8 @@ notrouter \- flag to turn off IPv4 routing .LP The \fB/etc/notrouter\fR file is no longer used as of the current release of the Solaris operating system. IPv4 forwarding is disabled by default and can be -enabled using \fBrouteadm\fR(1M). +enabled using \fBrouteadm\fR(8). .SH SEE ALSO .sp .LP -\fBrouteadm\fR(1M) +\fBrouteadm\fR(8) diff --git a/usr/src/man/man5/nscd.conf.5 b/usr/src/man/man5/nscd.conf.5 index 38b647cd18..6e96ca1cb8 100644 --- a/usr/src/man/man5/nscd.conf.5 +++ b/usr/src/man/man5/nscd.conf.5 @@ -15,7 +15,7 @@ nscd.conf \- name service cache daemon configuration .SH DESCRIPTION .LP The \fBnscd.conf\fR file contains the configuration information for -\fBnscd\fR(1M). Each line specifies either an \fIattribute\fR and a +\fBnscd\fR(8). Each line specifies either an \fIattribute\fR and a \fIvalue\fR, or an \fIattribute\fR, \fIcachename\fR, and a \fIvalue\fR. Fields are separated either by SPACE or TAB characters. A `\fB#\fR' (number sign) indicates the beginning of a comment; characters up to the end of the line are @@ -52,7 +52,7 @@ particularly over \fBNFS\fR. \fIvalue\fR may be either \fByes\fR or \fBno\fR. .sp .6 .RS 4n Sets the debug level desired. \fIvalue\fR may range from \fB0\fR (the default) -to \fB10\fR. Use of this option causes \fBnscd\fR(1M) to run in the foreground +to \fB10\fR. Use of this option causes \fBnscd\fR(8) to run in the foreground and not become a daemon. Note that the output of the debugging command is not likely to remain the same from release-to-release; scripts should \fInot\fR rely on its format. @@ -91,7 +91,7 @@ this attribute can be either \fByes\fR or \fBno\fR. .sp .6 .RS 4n This attribute allows the administrator to set the number of entries -\fBnscd\fR(1M) is to keep current in the specified cache. \fIvalue\fR is an +\fBnscd\fR(8) is to keep current in the specified cache. \fIvalue\fR is an integer number which should approximate the number of entries frequently used during the day. .RE @@ -178,7 +178,7 @@ automatically adjusts the hash table size. .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -195,8 +195,8 @@ Interface Stability Committed .SH SEE ALSO .LP -\fBnscd\fR(1M), \fBauth_attr\fR(4), \fBbootparams\fR(4), -\fBethers\fR(4), \fBexec_attr\fR(4), \fBgroup\fR(4), \fBhosts\fR(4), -\fBnetmasks\fR(4), \fBnetworks\fR(4), \fBpasswd\fR(4), \fBprinters\fR(4), -\fBprof_attr\fR(4), \fBproject\fR(4), \fBprotocols\fR(4), \fBrpc\fR(4), -\fBservices\fR(4), \fBuser_attr\fR(4), \fBattributes\fR(5) +\fBnscd\fR(8), \fBauth_attr\fR(5), \fBbootparams\fR(5), +\fBethers\fR(5), \fBexec_attr\fR(5), \fBgroup\fR(5), \fBhosts\fR(5), +\fBnetmasks\fR(5), \fBnetworks\fR(5), \fBpasswd\fR(5), \fBprinters\fR(5), +\fBprof_attr\fR(5), \fBproject\fR(5), \fBprotocols\fR(5), \fBrpc\fR(5), +\fBservices\fR(5), \fBuser_attr\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man5/nsmbrc.5 b/usr/src/man/man5/nsmbrc.5 index 05e4c99d60..6554199874 100644 --- a/usr/src/man/man5/nsmbrc.5 +++ b/usr/src/man/man5/nsmbrc.5 @@ -21,12 +21,12 @@ security implications. .sp .LP An authorized user can use the \fBsharectl\fR command to set global values for -these properties in SMF. See \fBsharectl\fR(1M). +these properties in SMF. See \fBsharectl\fR(8). .sp .LP A regular user can change the global values when granted the "SMBFS Management" -rights profile in the \fB/etc/user_attr\fR file. See \fBuser_attr\fR(4) and -\fBrbac\fR(5). +rights profile in the \fB/etc/user_attr\fR file. See \fBuser_attr\fR(5) and +\fBrbac\fR(7). .sp .LP The SMBFS library first reads from SMF and then the \fB$HOME/.nsmbrc\fR file @@ -195,7 +195,7 @@ be set in the default section. Valid values are \fByes\fR, \fBtrue\fR, .sp .6 .RS 4n Specifies whether to perform NetBIOS/WINS name lookups. To force all lookups to -be done through the name service switch (see \fBnsswitch.conf\fR(4)), set the +be done through the name service switch (see \fBnsswitch.conf\fR(5)), set the value to \fBno\fR. This property can \fBonly\fR be set by an administrator by using the \fBsharectl\fR command. This property can only be set in the default section. Valid values are \fByes\fR, \fBtrue\fR, \fBno\fR, and \fBfalse\fR. The @@ -393,7 +393,7 @@ connection. .RE .SH ATTRIBUTES -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -407,9 +407,9 @@ Interface Stability Committed .TE .SH SEE ALSO -\fBsmbutil\fR(1), \fBmount_smbfs\fR(1M), \fBsharectl\fR(1M), -\fBnsswitch.conf\fR(4), \fBuser_attr\fR(4), \fBattributes\fR(5), \fBrbac\fR(5), -\fBsmbfs\fR(7FS) +\fBsmbutil\fR(1), \fBmount_smbfs\fR(8), \fBsharectl\fR(8), +\fBnsswitch.conf\fR(5), \fBuser_attr\fR(5), \fBattributes\fR(7), \fBrbac\fR(7), +\fBsmbfs\fR(4FS) .SH NOTES By default, passwords stored in the \fB\&.nsmbrc\fR file are ignored unless \fBonly\fR the file owner has read and write permission. diff --git a/usr/src/man/man5/nss.5 b/usr/src/man/man5/nss.5 index ca2fdb9b4c..7ac96f5ccf 100644 --- a/usr/src/man/man5/nss.5 +++ b/usr/src/man/man5/nss.5 @@ -60,7 +60,7 @@ By default, address sorting is enabled. .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -77,4 +77,4 @@ Interface Stability Evolving .LP \fBgetaddrinfo\fR(3SOCKET), \fBgethostbyname\fR(3NSL), \fBgetipnodebyname\fR(3SOCKET), \fBinitgroups\fR(3C), -\fBnetdir_getbyname\fR(3NSL), \fBnsswitch.conf\fR(4), \fBattributes\fR(5) +\fBnetdir_getbyname\fR(3NSL), \fBnsswitch.conf\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man5/nsswitch.conf.5 b/usr/src/man/man5/nsswitch.conf.5 index e7762dbd71..2ea41a6e67 100644 --- a/usr/src/man/man5/nsswitch.conf.5 +++ b/usr/src/man/man5/nsswitch.conf.5 @@ -15,7 +15,7 @@ nsswitch.conf \- configuration file for the name service switch .SH DESCRIPTION .LP The operating system uses a number of databases of information about hosts, -ipnodes, users (\fBpasswd\fR(4), \fBshadow\fR(4), and \fBuser_attr\fR(4)), and +ipnodes, users (\fBpasswd\fR(5), \fBshadow\fR(5), and \fBuser_attr\fR(5)), and groups. Data for these can come from a variety of sources: hostnames and host addresses, for example, can be found in \fB/etc/hosts\fR, \fBNIS\fR, \fBLDAP\fR, \fBDNS\fR or Multicast \fBDNS\fR. Zero or more sources @@ -31,10 +31,10 @@ The following databases use the \fBswitch\fR file: c c l l . Database Used By -\fBaliases\fR \fBsendmail\fR(1M) +\fBaliases\fR \fBsendmail\fR(8) \fBauth_attr\fR \fBgetauthnam\fR(3SECDB) -\fBautomount\fR \fBautomount\fR(1M) -\fBbootparams\fR \fBrpc.bootparamd\fR(1M) +\fBautomount\fR \fBautomount\fR(8) +\fBbootparams\fR \fBrpc.bootparamd\fR(8) \fBethers\fR \fBethers\fR(3SOCKET) \fBgroup\fR \fBgetgrnam\fR(3C) \fBhosts\fR T{ @@ -42,13 +42,13 @@ Database Used By T} \fBipnodes\fR Same as \fBhosts\fR. \fBnetgroup\fR \fBinnetgr\fR(3C) -\fBnetmasks\fR \fBifconfig\fR(1M) +\fBnetmasks\fR \fBifconfig\fR(8) \fBnetworks\fR \fBgetnetbyname\fR(3SOCKET) \fBpasswd\fR T{ \fBgetpwnam\fR(3C), \fBgetspnam\fR(3C), \fBgetusernam\fR(3SECDB) T} \fBprinters\fR T{ -\fBlp\fR(1), \fBlpstat\fR(1), \fBcancel\fR(1), \fBlpr\fR(1B), \fBlpq\fR(1B), \fBlprm\fR(1B), \fBin.lpd\fR(1M), \fBlpadmin\fR(1M), \fBlpget\fR(1M), \fBlpset\fR(1M) +\fBlp\fR(1), \fBlpstat\fR(1), \fBcancel\fR(1), \fBlpr\fR(1B), \fBlpq\fR(1B), \fBlprm\fR(1B), \fBin.lpd\fR(8), \fBlpadmin\fR(8), \fBlpget\fR(8), \fBlpset\fR(8) T} \fBprof_attr\fR \fBgetprofnam\fR(3SECDB), \fBgetexecprof\fR(3SECDB) \fBproject\fR T{ @@ -215,7 +215,7 @@ In order to ensure that they all return consistent results, \fBgetservbyname\fR(3SOCKET), and \fBnetdir_getbyname\fR(3NSL) functions are all implemented in terms of the same internal library function. This function obtains the system-wide source lookup policy for \fBhosts\fR, \fBipnodes\fR, -and \fBservices\fR based on the \fBinet\fR family entries in \fBnetconfig\fR(4) +and \fBservices\fR based on the \fBinet\fR family entries in \fBnetconfig\fR(5) and uses the switch entries only if the \fBnetconfig\fR entries have a \fB-\fR (hyphen) in the last column for \fBnametoaddr\fR libraries. See the Notes section in \fBgethostbyname\fR(3NSL) and \fBgetservbyname\fR(3SOCKET) for @@ -304,7 +304,7 @@ often \fBeverything in the file followed by everything in NIS\fR, expressed by a solitary \fB+\fR at the end of \fB/etc/passwd\fR. The switch provides an alternative for this case (\fBpasswd: files nis\fR) that does not require \fB+\fR entries in \fB/etc/passwd\fR and \fB/etc/shadow\fR (the latter is a new -addition to SunOS 5.0, see \fBshadow\fR(4)). +addition to SunOS 5.0, see \fBshadow\fR(5)). .sp .LP If this is not sufficient, the \fBNIS/YP\fR compatibility source provides full @@ -589,7 +589,7 @@ ldap In order to get information from the Internet Domain Name Service for hosts that are not listed in the enterprise level name service, such as \fBLDAP\fR, use the following configuration and set up the -\fB/etc/resolv.conf\fR file (see \fBresolv.conf\fR(4) for more details): +\fB/etc/resolv.conf\fR file (see \fBresolv.conf\fR(5) for more details): .sp .ne 2 .na @@ -766,8 +766,8 @@ Sample configuration file that uses \fBfiles\fR, \fBdns\fR and \fBmdns\fR .SH SEE ALSO .LP \fBkpasswd\fR(1), \fBldap\fR(1), \fBnewtask\fR(1), -\fBpasswd\fR(1), \fBautomount\fR(1M), \fBifconfig\fR(1M), \fBmdnsd\fR(1M), -\fBrpc.bootparamd\fR(1M), \fBsendmail\fR(1M), +\fBpasswd\fR(1), \fBautomount\fR(8), \fBifconfig\fR(8), \fBmdnsd\fR(8), +\fBrpc.bootparamd\fR(8), \fBsendmail\fR(8), \fBgetgrnam\fR(3C), \fBgetnetgrent\fR(3C), \fBgetpwnam\fR(3C), \fBgetspnam\fR(3C), \fBgethostbyname\fR(3NSL), \fBgetpublickey\fR(3NSL), \fBgetrpcbyname\fR(3NSL), \fBnetdir\fR(3NSL), @@ -777,9 +777,9 @@ Sample configuration file that uses \fBfiles\fR, \fBdns\fR and \fBmdns\fR \fBgetexecprof\fR(3SECDB), \fBgetprofnam\fR(3SECDB), \fBgetuserattr\fR(3SECDB), \fBgetusernam\fR(3SECDB), \fBethers\fR(3SOCKET), \fBgetaddrinfo\fR(3SOCKET), \fBgetnetbyname\fR(3SOCKET), \fBgetprotobyname\fR(3SOCKET), -\fBgetservbyname\fR(3SOCKET), \fBauth_attr\fR(4), \fBhosts\fR(4), -\fBnetconfig\fR(4), \fBproject\fR(4), \fBresolv.conf\fR(4), \fBuser_attr\fR(4), -\fBypfiles\fR(4), \fBad\fR(5) +\fBgetservbyname\fR(3SOCKET), \fBauth_attr\fR(5), \fBhosts\fR(5), +\fBnetconfig\fR(5), \fBproject\fR(5), \fBresolv.conf\fR(5), \fBuser_attr\fR(5), +\fBypfiles\fR(5), \fBad\fR(7) .SH NOTES .LP Within each process that uses \fBnsswitch.conf\fR, the entire file is read only @@ -797,4 +797,4 @@ Misspelled names of sources and databases are treated as legitimate names of .LP The following functions do \fBnot\fR use the switch: \fBfgetgrent\fR(3C), \fBfgetprojent\fR(3PROJECT), \fBfgetpwent\fR(3C), \fBfgetspent\fR(3C), -\fBgetpw\fR(3C), \fBputpwent\fR(3C), \fBshadow\fR(4). +\fBgetpw\fR(3C), \fBputpwent\fR(3C), \fBshadow\fR(5). diff --git a/usr/src/man/man5/pam.conf.5 b/usr/src/man/man5/pam.conf.5 index f4b099dce1..25eed9cdef 100644 --- a/usr/src/man/man5/pam.conf.5 +++ b/usr/src/man/man5/pam.conf.5 @@ -313,7 +313,7 @@ whether or not it is \fBbinding\fR, \fBrequisite\fR, \fBrequired\fR, .SS "Utilities and Files" .LP The specific service names and module types for each service should be -documented in the man page for that service. For instance, the \fBsshd\fR(1M) +documented in the man page for that service. For instance, the \fBsshd\fR(8) man page lists all of the \fBPAM\fR service names and module types for the \fBsshd\fR command. .sp @@ -421,7 +421,7 @@ OTHER password include unix_common .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -439,24 +439,24 @@ Interface Stability See Below. The format is Stable. The contents has no stability attributes. .SH SEE ALSO .LP -\fBlogin\fR(1), \fBpasswd\fR(1), \fBin.rlogind\fR(1M), -\fBin.rshd\fR(1M), \fBin.telnetd\fR(1M), \fBin.uucpd\fR(1M), \fBinit\fR(1M), -\fBsac\fR(1M), \fBttymon\fR(1M), \fBsu\fR(1M), -\fBpam\fR(3PAM), \fBsyslog\fR(3C), \fBlibpam\fR(3LIB), \fBattributes\fR(5), -\fBenviron\fR(5), \fBpam_authtok_check\fR(5), \fBpam_authtok_get\fR(5), -\fBpam_authtok_store\fR(5), \fBpam_dhkeys\fR(5), \fBpam_krb5\fR(5), -\fBpam_passwd_auth\fR(5), \fBpam_unix_account\fR(5), \fBpam_unix_auth\fR(5), -\fBpam_unix_session\fR(5) +\fBlogin\fR(1), \fBpasswd\fR(1), \fBin.rlogind\fR(8), +\fBin.rshd\fR(8), \fBin.telnetd\fR(8), \fBin.uucpd\fR(8), \fBinit\fR(8), +\fBsac\fR(8), \fBttymon\fR(8), \fBsu\fR(8), +\fBpam\fR(3PAM), \fBsyslog\fR(3C), \fBlibpam\fR(3LIB), \fBattributes\fR(7), +\fBenviron\fR(7), \fBpam_authtok_check\fR(7), \fBpam_authtok_get\fR(7), +\fBpam_authtok_store\fR(7), \fBpam_dhkeys\fR(7), \fBpam_krb5\fR(7), +\fBpam_passwd_auth\fR(7), \fBpam_unix_account\fR(7), \fBpam_unix_auth\fR(7), +\fBpam_unix_session\fR(7) .SH NOTES .LP The \fBpam_unix\fR module is no longer supported. Similar functionality is -provided by \fBpam_authtok_check\fR(5), \fBpam_authtok_get\fR(5), -\fBpam_authtok_store\fR(5), \fBpam_dhkeys\fR(5), \fBpam_passwd_auth\fR(5), -\fBpam_unix_account\fR(5), \fBpam_unix_auth\fR(5), and -\fBpam_unix_session\fR(5). +provided by \fBpam_authtok_check\fR(7), \fBpam_authtok_get\fR(7), +\fBpam_authtok_store\fR(7), \fBpam_dhkeys\fR(7), \fBpam_passwd_auth\fR(7), +\fBpam_unix_account\fR(7), \fBpam_unix_auth\fR(7), and +\fBpam_unix_session\fR(7). .sp .LP With the removal of the \fBpam_unix\fR module, the SunOS delivered PAM service modules no longer need or support the "\fBuse_first_pass\fR" or "\fBtry_first_pass\fR" options. This functionality is provided by stacking -\fBpam_authtok_get\fR(5) above a module that requires a password. +\fBpam_authtok_get\fR(7) above a module that requires a password. diff --git a/usr/src/man/man5/passwd.5 b/usr/src/man/man5/passwd.5 index 6ec72d6176..10ad090885 100644 --- a/usr/src/man/man5/passwd.5 +++ b/usr/src/man/man5/passwd.5 @@ -64,7 +64,7 @@ must not contain a colon (\fB:\fR) or a newline (\fB\en\fR). .ad .RS 15n is an empty field. The encrypted password for the user is in the corresponding -entry in the \fB/etc/shadow\fR file. \fBpwconv\fR(1M) relies on a special value +entry in the \fB/etc/shadow\fR file. \fBpwconv\fR(8) relies on a special value of '\fBx\fR' in the password field of \fB/etc/passwd\fR. If this value of '\fBx\fR' exists in the password field of \fB/etc/passwd\fR, this indicates that the password for the user is already in \fB/etc/shadow\fR and should not @@ -168,7 +168,7 @@ entries for all members of the network group \fInetgroup\fR. .sp .LP This is also supported by specifying ``passwd : compat'' in -\fBnsswitch.conf\fR(4). The "compat" source might not be supported in future +\fBnsswitch.conf\fR(5). The "compat" source might not be supported in future releases. The preferred sources are \fBfiles\fR followed by the identifier of a name service, such as \fBnis\fR or \fBldap\fR. This has the effect of incorporating the entire contents of the naming service's \fBpasswd\fR database @@ -335,12 +335,12 @@ but with a \fIgcos\fR field of \fBGuest\fR .LP \fBchgrp\fR(1), \fBchown\fR(1), \fBfinger\fR(1), \fBgroups\fR(1), \fBlogin\fR(1), \fBnewgrp\fR(1), \fBpasswd\fR(1), -\fBsh\fR(1), \fBsort\fR(1), \fBdomainname\fR(1M), \fBgetent\fR(1M), -\fBpassmgmt\fR(1M), \fBpwck\fR(1M), \fBpwconv\fR(1M), -\fBsu\fR(1M), \fBuseradd\fR(1M), \fBuserdel\fR(1M), \fBusermod\fR(1M), +\fBsh\fR(1), \fBsort\fR(1), \fBdomainname\fR(8), \fBgetent\fR(8), +\fBpassmgmt\fR(8), \fBpwck\fR(8), \fBpwconv\fR(8), +\fBsu\fR(8), \fBuseradd\fR(8), \fBuserdel\fR(8), \fBusermod\fR(8), \fBa64l\fR(3C), \fBcrypt\fR(3C), \fBgetpw\fR(3C), \fBgetpwnam\fR(3C), -\fBgetspnam\fR(3C), \fBputpwent\fR(3C), \fBgroup\fR(4), \fBhosts.equiv\fR(4), -\fBnsswitch.conf\fR(4), \fBshadow\fR(4), \fBenviron\fR(5), +\fBgetspnam\fR(3C), \fBputpwent\fR(3C), \fBgroup\fR(5), \fBhosts.equiv\fR(5), +\fBnsswitch.conf\fR(5), \fBshadow\fR(5), \fBenviron\fR(7), \fBunistd.h\fR(3HEAD) .sp .LP diff --git a/usr/src/man/man5/path_to_inst.5 b/usr/src/man/man5/path_to_inst.5 index 3034f4788d..3e736ab979 100644 --- a/usr/src/man/man5/path_to_inst.5 +++ b/usr/src/man/man5/path_to_inst.5 @@ -28,8 +28,8 @@ In order to keep instance numbers persistent across reboots, the system records them in \fB/etc/path_to_inst\fR. .sp .LP -This file is read only at boot time, and is updated by \fBadd_drv\fR(1M) and -\fBdevfsadm\fR(1M). +This file is read only at boot time, and is updated by \fBadd_drv\fR(8) and +\fBdevfsadm\fR(8). .sp .LP Note that it is generally not necessary for the system administrator to change @@ -38,7 +38,7 @@ this file, as the system will maintain it. .LP The system administrator can change the assignment of instance numbers by editing this file and doing a reconfiguration reboot. However, any changes made -in this file will be lost if \fBadd_drv\fR(1M) or \fBdevfsadm\fR(1M) is run +in this file will be lost if \fBadd_drv\fR(8) or \fBdevfsadm\fR(8) is run before the system is rebooted. .sp .LP @@ -117,7 +117,7 @@ Mapping of physical device names to instance numbers. .SH SEE ALSO .sp .LP -\fBadd_drv\fR(1M), \fBboot\fR(1M), \fBdevfsadm\fR(1M), \fBmknod\fR(1M) +\fBadd_drv\fR(8), \fBboot\fR(8), \fBdevfsadm\fR(8), \fBmknod\fR(8) .SH WARNINGS .sp .LP @@ -125,7 +125,7 @@ If the file is removed the system may not be bootable (as it may rely on information found in this file to find the root, usr or swap device). If it does successfully boot, it will regenerate the file, but after rebooting devices may end up having different minor numbers than they did before, and -special files created via \fBmknod\fR(1M) may refer to different devices than +special files created via \fBmknod\fR(8) may refer to different devices than expected. .sp .LP diff --git a/usr/src/man/man5/pci.5 b/usr/src/man/man5/pci.5 index 7b2ae2cb67..1aec21d38d 100644 --- a/usr/src/man/man5/pci.5 +++ b/usr/src/man/man5/pci.5 @@ -27,7 +27,7 @@ devices. .LP On some occasions, drivers for \fBPCI\fR and PCIe devices can use driver configuration files to provide driver private properties through the global -property mechanism. See \fBdriver.conf\fR(4) for further details. Driver +property mechanism. See \fBdriver.conf\fR(5) for further details. Driver configuration files can also be used to augment or override properties for a specific instance of a driver. .sp @@ -239,7 +239,7 @@ of the device. The device has a device number of 2, and a function number of 1. .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -254,7 +254,7 @@ Architecture SPARC, x86 .SH SEE ALSO .LP -\fBdriver.conf\fR(4), \fBattributes\fR(5), \fBddi_intr_add_handler\fR(9F), +\fBdriver.conf\fR(5), \fBattributes\fR(7), \fBddi_intr_add_handler\fR(9F), \fBddi_prop_lookup\fR(9F), \fBddi_regs_map_setup\fR(9F) .sp .LP diff --git a/usr/src/man/man5/phones.5 b/usr/src/man/man5/phones.5 index 120ba7d320..ddbdcd5a33 100644 --- a/usr/src/man/man5/phones.5 +++ b/usr/src/man/man5/phones.5 @@ -28,7 +28,7 @@ lines of the form: .sp .LP -The system name is one of those defined in the \fBremote\fR(4) file and the +The system name is one of those defined in the \fBremote\fR(5) file and the phone number is constructed from \fB[0123456789\(mi=*%]\fR. The `\fB=\fR' and `\fB*\fR' characters are indicators to the auto call units to pause and wait for a second dial tone (when going through an exchange). The `\fB=\fR' is @@ -56,4 +56,4 @@ one in turn, until it establishes a connection. .SH SEE ALSO .sp .LP -\fBtip\fR(1), \fBremote\fR(4) +\fBtip\fR(1), \fBremote\fR(5) diff --git a/usr/src/man/man5/pkginfo.5 b/usr/src/man/man5/pkginfo.5 index adf1c4af0a..9cb3fb0459 100644 --- a/usr/src/man/man5/pkginfo.5 +++ b/usr/src/man/man5/pkginfo.5 @@ -33,7 +33,7 @@ parameters are mandatory. Other parameters are optional. .LP \fBpkginfo\fR provides optional parameters and an environment variable in support of the zones (multiple Solaris environments) feature. See -\fBzones\fR(5). +\fBzones\fR(7). .sp .LP The following parameters are mandatory: @@ -228,7 +228,7 @@ A list of allowable run states for package installation (for example, "\fBS s environment supports the run levels \fBs\fR, \fBS\fR, \fB0\fR, \fB1\fR, \fB2\fR, \fB3\fR, \fB5\fR, and \fB6\fR. Applicable run levels for this parameter are \fBs\fR, \fBS\fR, \fB1\fR, \fB2\fR, and \fB3\fR. See -\fBinit\fR(1M) for details. +\fBinit\fR(8) for details. .RE .sp @@ -266,7 +266,7 @@ field are placed on the medium using the standard ordering procedures. .ad .sp .6 .RS 4n -Production stamp used to mark the \fBpkgmap\fR(4) file on the output volumes. +Production stamp used to mark the \fBpkgmap\fR(5) file on the output volumes. Provides a means for distinguishing between production copies of a version if more than one is in use at a time. If \fBPSTAMP\fR is not defined, the default is used. The default consists of the UNIX system machine name followed by the @@ -285,7 +285,7 @@ allows run states of \fBS\fR, \fBs\fR or \fB1\fR). The Solaris operating environment supports the run levels \fBs\fR, \fBS\fR, \fB0\fR, \fB1\fR, \fB2\fR, \fB3\fR, \fB5\fR, and \fB6\fR. Applicable run levels for this parameter are \fBs\fR, \fBS\fR, \fB1\fR, \fB2\fR, and \fB3\fR See -\fBinit\fR(1M) for details. +\fBinit\fR(8) for details. .RE .sp @@ -679,7 +679,7 @@ RSTATES="S 2" .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -729,7 +729,7 @@ SUNW_PKG_DIR Evolving .SH SEE ALSO .LP \fBisalist\fR(1), \fBlimit\fR(1), \fBpkgmk\fR(1), \fBuname\fR(1), -\fBinit\fR(1M), \fBpkgmap\fR(4), \fBattributes\fR(5), \fBzones\fR(5) +\fBinit\fR(8), \fBpkgmap\fR(5), \fBattributes\fR(7), \fBzones\fR(7) .sp .LP \fIApplication Packaging Developer\&'s Guide\fR diff --git a/usr/src/man/man5/pkgmap.5 b/usr/src/man/man5/pkgmap.5 index f3188f2c40..a30aaff4ea 100644 --- a/usr/src/man/man5/pkgmap.5 +++ b/usr/src/man/man5/pkgmap.5 @@ -12,7 +12,7 @@ pkgmap \- package contents description file .LP \fBpkgmap\fR is an \fBASCII\fR file that provides a complete listing of the package contents. It is automatically generated by \fBpkgmk\fR(1) using the -information in the \fBprototype\fR(4) file. +information in the \fBprototype\fR(5) file. .sp .LP Each entry in \fBpkgmap\fR describes a single ``deliverable object file.'' A @@ -178,11 +178,11 @@ specified if the \fIftype\fR is \fBi\fR (information file). .RS 12n \fIpathname\fR may contain variables of the form \fB$\fR\fIvariable\fR that support install-time configuration of the file. \fIvariable\fR may be embedded -in the pathname structure. (See \fBprototype\fR(4) for definitions of variable +in the pathname structure. (See \fBprototype\fR(5) for definitions of variable specifications.) .sp Do not use the following reserved words in \fIpathname\fR, since they are -applied by \fBpkgadd\fR(1M) using a different mechanism: +applied by \fBpkgadd\fR(8) using a different mechanism: .sp .in +2 .nf @@ -226,7 +226,7 @@ indicates that the mode will be left unchanged, implying that the file already exists on the target machine. This field is not used for linked files, packaging information files, or non-installable files. .sp -The mode can contain a variable specification. (See \fBprototype\fR(4) for +The mode can contain a variable specification. (See \fBprototype\fR(5) for definitions of variable specifications.) .RE @@ -245,7 +245,7 @@ This field is not used for linked files or non-installable files. It is used optionally with a package information file. If used, it indicates with what owner an installation script will be executed. .sp -The owner can contain a variable specification. (See \fBprototype\fR(4) for +The owner can contain a variable specification. (See \fBprototype\fR(5) for definitions of variable specifications.) .RE @@ -264,7 +264,7 @@ the file system. This field is not used for linked files or non-installable files. It is used optionally with a package information file. If used, it indicates with what group an installation script will be executed. .sp -The group can contain a variable specification. (See \fBprototype\fR(4) for +The group can contain a variable specification. (See \fBprototype\fR(5) for definitions of variable specifications.) .RE @@ -353,8 +353,8 @@ processes which are executing during installation to be overwritten. .SH SEE ALSO .sp .LP -\fBpkgmk\fR(1), \fBpkgadd\fR(1M), \fBstat\fR(2), \fBpkginfo\fR(4), -\fBprototype\fR(4) +\fBpkgmk\fR(1), \fBpkgadd\fR(8), \fBstat\fR(2), \fBpkginfo\fR(5), +\fBprototype\fR(5) .sp .LP \fIApplication Packaging Developer\&'s Guide\fR diff --git a/usr/src/man/man5/policy.conf.5 b/usr/src/man/man5/policy.conf.5 index f5ee570b22..4b6a20f5eb 100644 --- a/usr/src/man/man5/policy.conf.5 +++ b/usr/src/man/man5/policy.conf.5 @@ -32,7 +32,7 @@ The following keys are defined: .RS 4n Specify the default set of authorizations granted to all users. This entry is interpreted by \fBchkauthattr\fR(3SECDB). The value is zero or more -comma-separated authorizations defined in \fBauth_attr\fR(4). +comma-separated authorizations defined in \fBauth_attr\fR(5). .RE .sp @@ -44,7 +44,7 @@ comma-separated authorizations defined in \fBauth_attr\fR(4). .RS 4n Specify the default set of profiles granted to all users. This entry is interpreted by \fBchkauthattr\fR(3SECDB) and \fBgetexecuser\fR(3SECDB). The -value is zero or more comma-separated profiles defined in \fBprof_attr\fR(4). +value is zero or more comma-separated profiles defined in \fBprof_attr\fR(5). .RE .sp @@ -57,7 +57,7 @@ value is zero or more comma-separated profiles defined in \fBprof_attr\fR(4). Specify an additional default set of profiles granted to the \fIconsole user\fR user. This entry is interpreted by \fBchkauthattr\fR(3SECDB) and \fBgetexecuser\fR(3SECDB). The value is zero or more comma-separated profiles -defined in \fBprof_attr\fR(4). +defined in \fBprof_attr\fR(5). .RE .sp @@ -68,10 +68,10 @@ defined in \fBprof_attr\fR(4). .sp .6 .RS 4n Settings for these keys determine the default privileges that users have. (See -\fBprivileges\fR(5).) If these keys are not set, the default privileges are +\fBprivileges\fR(7).) If these keys are not set, the default privileges are taken from the inherited set. \fBPRIV_DEFAULT\fR determines the default set on login. \fBPRIV_LIMIT\fR defines the limit set on login. Users can have -privileges assigned or taken away through use of \fBuser_attr\fR(4). Privileges +privileges assigned or taken away through use of \fBuser_attr\fR(5). Privileges can also be assigned to profiles, in which case users who have those profiles can exercise the assigned privileges through \fBpfexec\fR(1). .sp @@ -98,7 +98,7 @@ privilege set can cause unexpected failure modes in applications. Specifies whether a local account is locked after the count of failed logins for a user equals or exceeds the allowed number of retries as defined by \fBRETRIES\fR in \fB/etc/default/login\fR. The default value for users is -\fBNO\fR. Individual account overrides are provided by \fBuser_attr\fR(4). +\fBNO\fR. Individual account overrides are provided by \fBuser_attr\fR(5). .RE .sp @@ -133,7 +133,7 @@ another algorithm, such as \fBCRYPT_DEFAULT=1\fR for BSD and Linux MD5. .sp .6 .RS 4n Specify the default algorithm for new passwords. The Solaris default was once -the traditional UNIX algorithm. This is not listed in \fBcrypt.conf\fR(4) since +the traditional UNIX algorithm. This is not listed in \fBcrypt.conf\fR(5) since it is internal to \fBlibc\fR. The reserved name \fB__unix__\fR is used to refer to it. .RE @@ -225,7 +225,7 @@ Defines policy for the system. .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -242,9 +242,9 @@ Interface Stability Committed .LP \fBlogin\fR(1), \fBpfexec\fR(1), \fBchkauthattr\fR(3SECDB), -\fBgetexecuser\fR(3SECDB), \fBauth_attr\fR(4), \fBcrypt.conf\fR(4), -\fBprof_attr\fR(4), \fBuser_attr\fR(4), \fBattributes\fR(5), -\fBprivileges\fR(5) +\fBgetexecuser\fR(3SECDB), \fBauth_attr\fR(5), \fBcrypt.conf\fR(5), +\fBprof_attr\fR(5), \fBuser_attr\fR(5), \fBattributes\fR(7), +\fBprivileges\fR(7) .SH NOTES .LP diff --git a/usr/src/man/man5/power.conf.5 b/usr/src/man/man5/power.conf.5 index 67d7e2afe3..d11581bf21 100644 --- a/usr/src/man/man5/power.conf.5 +++ b/usr/src/man/man5/power.conf.5 @@ -13,8 +13,8 @@ power.conf \- Power Management configuration information file .SH DESCRIPTION The \fBpower.conf\fR file is used by the Power Management configuration program -\fBpmconfig\fR(1M), to initialize the settings for Power Management. If you -make changes to this file, you must run \fBpmconfig\fR(1M) manually for the +\fBpmconfig\fR(8), to initialize the settings for Power Management. If you +make changes to this file, you must run \fBpmconfig\fR(8) manually for the changes to take effect. .sp .LP @@ -745,10 +745,10 @@ autopm disable .sp .LP -Then run \fBpmconfig\fR or reboot. See \fBpmconfig\fR(1M) for more information. +Then run \fBpmconfig\fR or reboot. See \fBpmconfig\fR(8) for more information. .SH ATTRIBUTES -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -762,9 +762,9 @@ Interface stability Committed .TE .SH SEE ALSO -\fBpmconfig\fR(1M), \fBpowerd\fR(1M), \fBuadmin\fR(2), -\fBlibdevinfo\fR(3LIB), \fBattributes\fR(5), \fBcpr\fR(7), \fBldterm\fR(7M), -\fBpm\fR(7D), \fBpm-components\fR(9P), \fBremovable-media\fR(9P) +\fBpmconfig\fR(8), \fBpowerd\fR(8), \fBuadmin\fR(2), +\fBlibdevinfo\fR(3LIB), \fBattributes\fR(7), \fBcpr\fR(4), \fBldterm\fR(4M), +\fBpm\fR(4D), \fBpm-components\fR(9P), \fBremovable-media\fR(9P) .sp .LP \fIWriting Device Drivers\fR diff --git a/usr/src/man/man5/printers.5 b/usr/src/man/man5/printers.5 index 2968f368fc..edc0801032 100644 --- a/usr/src/man/man5/printers.5 +++ b/usr/src/man/man5/printers.5 @@ -15,7 +15,7 @@ $HOME/.printers .SH DESCRIPTION .LP The \fB$HOME/.printers\fR file is a simplified version of the system -\fB/etc/printers.conf\fR file. See \fBprinters.conf\fR(4). Users create the +\fB/etc/printers.conf\fR file. See \fBprinters.conf\fR(5). Users create the \fB$HOME/.printers\fR file in their home directory. This optional file is customizable by the user. .sp @@ -30,7 +30,7 @@ Sets personal aliases for all print commands. .TP 2. Sets the interest list for the \fBlpget\fR, \fBlpstat\fR, and \fBcancel\fR -commands. See \fBlpget\fR(1M), \fBlpstat\fR(1) and \fBcancel\fR(1). +commands. See \fBlpget\fR(8), \fBlpstat\fR(1) and \fBcancel\fR(1). .RE .RS +4 .TP @@ -60,10 +60,10 @@ by a NEWLINE. .LP Specify the alias or aliases in the first field. Separate multiple aliases by a pipe sign (`\fB|\fR'). Specify the destination in the second field. A -destination names a printer or class of printers, See \fBlpadmin\fR(1M). +destination names a printer or class of printers, See \fBlpadmin\fR(8). Specify the destination using atomic, URI-style (\fIscheme\fR\fB://\fR\fBendpoint\fR), or POSIX-style -(\fIserver\fR\fB:\fR\fIdestination\fR) names. See \fBprinters.conf\fR(4) for +(\fIserver\fR\fB:\fR\fIdestination\fR) names. See \fBprinters.conf\fR(5) for information regarding the naming conventions for destination names. .SS "Setting the Interest List for lpget, lpstat and cancel" .LP @@ -71,7 +71,7 @@ Specify \fB_all\fR in the first field. Specify the list of destinations for the interest list in the second field. Separate each destinations by a comma (`\fB,\fR'). Specify destinations using atomic, URI-style (\fIscheme\fR\fB://\fR\fBendpoint\fR), or POSIX-style -(\fIserver\fR\fB:\fR\fIdestination\fR) names. See \fBprinters.conf\fR(4) for +(\fIserver\fR\fB:\fR\fIdestination\fR) names. See \fBprinters.conf\fR(5) for information regarding the naming conventions for destination names. This list of destinations can refer to an alias defined in \fB$HOME/.printers\fR. .SS "Setting the Default Destination" @@ -79,14 +79,14 @@ of destinations can refer to an alias defined in \fB$HOME/.printers\fR. Specify \fB_default\fR in the first field. Specify the default destination in the second field. Specify the default destination using atomic, URI-style (\fIscheme\fR\fB://\fR\fBendpoint\fR), or POSIX-style -(\fIserver\fR\fB:\fR\fIdestination\fR) names. See \fBprinters.conf\fR(4) for +(\fIserver\fR\fB:\fR\fIdestination\fR) names. See \fBprinters.conf\fR(5) for information regarding the naming conventions for destination names. The default destination can refer to an alias defined in \fB$HOME/.printers\fR. .SS "Locating Destination Information" .LP The print client commands locate destination information based on the "printers" database entry in the \fB/etc/nsswitch.conf\fR file. See -\fBnsswitch.conf\fR(4). +\fBnsswitch.conf\fR(5). .SS "Locating the Personal Default Destination" .LP The default destination is located differently depending on the command. @@ -275,7 +275,7 @@ LDAP version of \fB/etc/printers.conf\fR .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -291,8 +291,8 @@ Interface Stability Stable .SH SEE ALSO .LP \fBcancel\fR(1), \fBlp\fR(1), \fBlpq\fR(1B), \fBlpr\fR(1B), \fBlprm\fR(1B), -\fBlpstat\fR(1), \fBlpadmin\fR(1M), \fBlpget\fR(1M), \fBnsswitch.conf\fR(4), -\fBprinters.conf\fR(4), \fBattributes\fR(5), \fBstandards\fR(5) +\fBlpstat\fR(1), \fBlpadmin\fR(8), \fBlpget\fR(8), \fBnsswitch.conf\fR(5), +\fBprinters.conf\fR(5), \fBattributes\fR(7), \fBstandards\fR(7) .sp .LP \fISystem Administration Guide: Basic Administration\fR diff --git a/usr/src/man/man5/printers.conf.5 b/usr/src/man/man5/printers.conf.5 index cc1d6dcdb9..ffdd4e37cb 100644 --- a/usr/src/man/man5/printers.conf.5 +++ b/usr/src/man/man5/printers.conf.5 @@ -29,7 +29,7 @@ printers.conf \- system printing configuration database The \fBprinters.conf\fR file is the system printing configuration database. System administrators use \fBprinters.conf\fR to describe destinations for the print client commands and the print protocol adaptor. A destination names a -printer or class of printers. See \fBlpadmin\fR(1M). The \fBLP\fR print spooler +printer or class of printers. See \fBlpadmin\fR(8). The \fBLP\fR print spooler uses private \fBLP\fR configuration data for represented in the \fBprinters.conf\fR database. .SS "Entries" @@ -40,7 +40,7 @@ terminated by a NEWLINE. The first field of each entry specifies the name of the destination and aliases to which the entry describes. Specify one or more names or aliases of the destination in this first field. Specify the destination using atomic names. URI-style and POSIX-style names are not -acceptable. See \fBstandards\fR(5). Separate destination names by pipe signs +acceptable. See \fBstandards\fR(7). Separate destination names by pipe signs (`\fB|\fR'). .sp .LP @@ -59,7 +59,7 @@ multiple lines by adding a backslash (`\fB\e\fR\&') as the last character in the line. \fBprinters.conf\fR can include comments. Comments have a pound sign (`\fB#\fR') as the first character in the line, and are terminated by a NEWLINE. Use the \fBlpset\fR command to create or modify \fBprinters.conf\fR. -See \fBlpset\fR(1M). Do \fBnot\fR make changes in \fBprinters.conf\fR by using +See \fBlpset\fR(8). Do \fBnot\fR make changes in \fBprinters.conf\fR by using an editor. .SS "Specifying Configuration Options" .LP @@ -178,7 +178,7 @@ Sets the interest list for the \fBlpget\fR, \fBlpstat\fR, and \fBcancel\fR commands. \fIdestination_list\fR is a comma-separated list of destinations. Specify \fIdestination\fR using atomic, URI-style (\fIscheme\fR://\fIendpoint\fR), or Posix-style names (\fBserver:printer\fR). -See \fBlpget\fR(1M), \fBlpstat\fR(1), and \fBcancel\fR(1). +See \fBlpget\fR(8), \fBlpstat\fR(1), and \fBcancel\fR(1). .RE .SS "LP Server Options" @@ -210,7 +210,7 @@ associated print service and communications endpoint make use of a specific name resolution ordering. Destination names in URI and POSIX form are complete unto themselves and require no further resolution. Names in atomic form are resolved based on the \fBprinters\fR database entry in the /etc/nsswitch.conf -file. See nsswitch.conf(4) +file. See nsswitch.conf(5) .SS "Locating the Personal Default Destination" .LP The default destination is located differently depending on the command. @@ -417,7 +417,7 @@ LDAP version of \fB/etc/printers.conf\fR .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -433,10 +433,10 @@ Stability Level Stable .SH SEE ALSO .LP \fBcancel\fR(1), \fBenable\fR(1), \fBenable\fR(1), \fBlp\fR(1), \fBlpq\fR(1B), -\fBlpr\fR(1B), \fBlprm\fR(1B), \fBlpstat\fR(1), \fBaccept\fR(1M), -\fBin.lpd\fR(1M), \fBlpadmin\fR(1M), \fBlpget\fR(1M), \fBlpmove\fR(1M), -\fBlpset\fR(1M), \fBaccept\fR(1M), \fBnsswitch.conf\fR(4), \fBprinters\fR(4), -\fBattributes\fR(5), \fBstandards\fR(5) +\fBlpr\fR(1B), \fBlprm\fR(1B), \fBlpstat\fR(1), \fBaccept\fR(8), +\fBin.lpd\fR(8), \fBlpadmin\fR(8), \fBlpget\fR(8), \fBlpmove\fR(8), +\fBlpset\fR(8), \fBaccept\fR(8), \fBnsswitch.conf\fR(5), \fBprinters\fR(5), +\fBattributes\fR(7), \fBstandards\fR(7) .sp .LP \fISystem Administration Guide: Basic Administration\fR diff --git a/usr/src/man/man5/priv_names.5 b/usr/src/man/man5/priv_names.5 index c2a22f109d..bbc03e9480 100644 --- a/usr/src/man/man5/priv_names.5 +++ b/usr/src/man/man5/priv_names.5 @@ -16,7 +16,7 @@ priv_names \- privilege definition file .sp .LP The \fBpriv_names\fR file, located in \fB/etc/security\fR, defines the -privileges with which a process can be associated. See \fBprivileges\fR(5) for +privileges with which a process can be associated. See \fBprivileges\fR(7) for the privilege definitions. In that man page, privileges correspond to privilege names in \fBpriv_names\fR as shown in the following examples: .sp @@ -25,7 +25,7 @@ names in \fBpriv_names\fR as shown in the following examples: .TS c c l l . -name in privileges(5) Name in \fBpriv_names\fR +name in privileges(7) Name in \fBpriv_names\fR _ \fBPRIV_FILE_CHOWN\fR \fBfile_chown\fR \fBPRIV_FILE_CHOWN_SELF\fR \fBfile_chown_self\fR @@ -35,7 +35,7 @@ _ .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -51,4 +51,4 @@ Interface Stability Evolving .SH SEE ALSO .sp .LP -\fBppriv\fR(1), \fBattributes\fR(5), \fBprivileges\fR(5) +\fBppriv\fR(1), \fBattributes\fR(7), \fBprivileges\fR(7) diff --git a/usr/src/man/man5/process.5 b/usr/src/man/man5/process.5 index 25cd60240f..7bad270968 100644 --- a/usr/src/man/man5/process.5 +++ b/usr/src/man/man5/process.5 @@ -16,7 +16,7 @@ Process contracts allow processes to create a fault boundary around a set of subprocesses and observe events which occur within that boundary. .sp .LP -Process contracts are managed using the \fBcontract\fR(4) file system and the +Process contracts are managed using the \fBcontract\fR(5) file system and the \fBlibcontract\fR(3LIB) library. The process contract type directory is \fB/system/contract/process\fR. .SS "CREATION" @@ -66,7 +66,7 @@ A member of the process contract exited. .sp .6 .RS 4n A process failed and dumped core. This could also occur if the process would -have dumped core had appropriate \fBcoreadm\fR(1M) options been enabled and +have dumped core had appropriate \fBcoreadm\fR(8) options been enabled and core file size was unlimited. .RE @@ -92,7 +92,7 @@ A process was killed because of an uncorrectable hardware error. .RE .SS "TERMS" -The following common contract terms, defined in \fBcontract\fR(4), have +The following common contract terms, defined in \fBcontract\fR(5), have process-contract specific attributes: .sp .ne 2 @@ -126,7 +126,7 @@ CT_PR_EV_SIGNAL)\fR. .LP The following contract terms can be read from or written to a process contract template using the named \fBlibcontract\fR(3LIB) interfaces. These contract -terms are in addition to those described in \fBcontract\fR(4). +terms are in addition to those described in \fBcontract\fR(5). .sp .ne 2 .na @@ -490,7 +490,7 @@ The name of the system-wide core file in the global zone. Use .sp .LP -See \fBcoreadm\fR(1M) for more information about per-process, global, and +See \fBcoreadm\fR(8) for more information about per-process, global, and system-wide core files. .sp .LP @@ -531,7 +531,7 @@ Contains definitions of event-type macros. .RE .SH SEE ALSO -\fBctrun\fR(1), \fBctstat\fR(1), \fBctwatch\fR(1), \fBcoreadm\fR(1M), +\fBctrun\fR(1), \fBctstat\fR(1), \fBctwatch\fR(1), \fBcoreadm\fR(8), \fBclose\fR(2), \fBfork\fR(2), \fBioctl\fR(2), \fBopen\fR(2), \fBpoll\fR(2), \fBct_pr_event_get_exitstatus\fR(3CONTRACT), \fBct_pr_event_get_gcorefile\fR(3CONTRACT), @@ -546,4 +546,4 @@ Contains definitions of event-type macros. \fBct_pr_tmpl_set_transfer\fR(3CONTRACT), \fBct_tmpl_set_cookie\fR(3CONTRACT), \fBct_tmpl_set_critical\fR(3CONTRACT), \fBct_tmpl_set_informative\fR(3CONTRACT), \fBlibcontract\fR(3LIB), -\fBcontract\fR(4), \fBprivileges\fR(5) +\fBcontract\fR(5), \fBprivileges\fR(7) diff --git a/usr/src/man/man5/prof_attr.5 b/usr/src/man/man5/prof_attr.5 index 0a7c50e978..4036a62763 100644 --- a/usr/src/man/man5/prof_attr.5 +++ b/usr/src/man/man5/prof_attr.5 @@ -22,7 +22,7 @@ routines to gain access to this information. .sp .LP The search order for multiple \fBprof_attr\fR sources is specified in the -\fB/etc/nsswitch.conf\fR file, as described in the \fBnsswitch.conf\fR(4) man +\fB/etc/nsswitch.conf\fR file, as described in the \fBnsswitch.conf\fR(5) man page. .sp .LP @@ -89,7 +89,7 @@ keys can be specified. There are four valid keys: \fBhelp\fR, \fBprofiles\fR, \fB\&.html\fR. .sp \fBauths\fR specifies a comma-separated list of authorization names chosen from -those names defined in the \fBauth_attr\fR(4) database. Authorization names can +those names defined in the \fBauth_attr\fR(5) database. Authorization names can be specified using the asterisk (\fB*\fR) character as a wildcard. For example, \fBsolaris.printer.*\fR would mean all of Sun's authorizations for printing. .sp @@ -97,7 +97,7 @@ be specified using the asterisk (\fB*\fR) character as a wildcard. For example, those names defined in the \fBprof_attr\fR database. .sp \fBprivs\fR specifies a comma-separated list of privileges names chosen from -those names defined in the \fBpriv_names\fR(4) database. These privileges can +those names defined in the \fBpriv_names\fR(5) database. These privileges can then be used for executing commands with \fBpfexec\fR(1). .RE @@ -144,7 +144,7 @@ able to log in and do system maintenance in single-user mode and at other times when the network name service databases are not available. So that the profile definitions for root can be located at such times, root's profiles should be defined in the local \fBprof_attr\fR file, and the order shown in the example -\fBnsswitch.conf\fR(4) file entry under EXAMPLES is highly recommended. +\fBnsswitch.conf\fR(5) file entry under EXAMPLES is highly recommended. .sp .LP Because the list of legal keys is likely to expand, any code that parses this @@ -165,5 +165,5 @@ equals (\fB=\fR), and backslash (\fB\e\fR). .SH SEE ALSO .LP \fBauths\fR(1), \fBpfexec\fR(1), \fBprofiles\fR(1), \fBgetauthattr\fR(3SECDB), -\fBgetprofattr\fR(3SECDB), \fBgetuserattr\fR(3SECDB), \fBauth_attr\fR(4), -\fBexec_attr\fR(4), \fBpriv_names\fR(4), \fBuser_attr\fR(4) +\fBgetprofattr\fR(3SECDB), \fBgetuserattr\fR(3SECDB), \fBauth_attr\fR(5), +\fBexec_attr\fR(5), \fBpriv_names\fR(5), \fBuser_attr\fR(5) diff --git a/usr/src/man/man5/profile.5 b/usr/src/man/man5/profile.5 index 16cb93c970..0388794bcb 100644 --- a/usr/src/man/man5/profile.5 +++ b/usr/src/man/man5/profile.5 @@ -89,7 +89,7 @@ system-wide environment .sp .LP \fBenv\fR(1), \fBlogin\fR(1), \fBmail\fR(1), \fBsh\fR(1), \fBstty\fR(1), -\fBtput\fR(1), \fBsu\fR(1M), \fBterminfo\fR(4), \fBenviron\fR(5), \fBterm\fR(5) +\fBtput\fR(1), \fBsu\fR(8), \fBterminfo\fR(5), \fBenviron\fR(7), \fBterm\fR(7) .sp .LP \fISolaris Advanced User\&'s Guide\fR diff --git a/usr/src/man/man5/project.5 b/usr/src/man/man5/project.5 index e1c54f7076..a25731b840 100644 --- a/usr/src/man/man5/project.5 +++ b/usr/src/man/man5/project.5 @@ -98,9 +98,9 @@ where \fIname\fR is the arbitrary string specifying the key's name and \fIvalue\fR is the optional key value. An explanation of the valid name-value pair syntax is provided in the \fBUSAGE\fR section of this page. The expected most frequent use of the attribute field is for the specification of resource -controls. See \fBresource_controls\fR(5) for a description of the resource +controls. See \fBresource_controls\fR(7) for a description of the resource controls supported in the current release of the Solaris operating system. You -can also use the attribute field for resource caps (see \fBrcapd\fR(1M)) and +can also use the attribute field for resource caps (see \fBrcapd\fR(8)) and for the \fBproject.pool\fR attribute (see \fBsetproject\fR(3PROJECT)). .RE @@ -155,7 +155,7 @@ and only one line. .sp .LP -An example project entry for \fBnsswitch.conf\fR(4) is: +An example project entry for \fBnsswitch.conf\fR(5) is: .sp .in +2 @@ -220,11 +220,11 @@ support (into further values lists) by parentheses. Each of these values can be composed of the upper and lower case alphabetic characters, the digits '0' through '9', and the punctuation characters hyphen (-), plus (+), period (.), slash (/), and underscore (_). Example resource control value specifications -are provided in EXAMPLES, above, and in \fBresource_controls\fR(5) and +are provided in EXAMPLES, above, and in \fBresource_controls\fR(7) and \fBgetprojent\fR(3PROJECT). .SH SEE ALSO .sp .LP \fBnewtask\fR(1), \fBprojects\fR(1), \fBprctl\fR(1), \fBgetprojent\fR(3PROJECT), \fBsetrctl\fR(2), \fBunistd.h\fR(3HEAD), -\fBnsswitch.conf\fR(4), \fBresource_controls\fR(5) +\fBnsswitch.conf\fR(5), \fBresource_controls\fR(7) diff --git a/usr/src/man/man5/protocols.5 b/usr/src/man/man5/protocols.5 index 3e31f27f9e..56cc63e865 100644 --- a/usr/src/man/man5/protocols.5 +++ b/usr/src/man/man5/protocols.5 @@ -91,7 +91,7 @@ configuration file for name-service switch .SH SEE ALSO .LP -\fBgetprotobyname\fR(3SOCKET), \fBnsswitch.conf\fR(4) +\fBgetprotobyname\fR(3SOCKET), \fBnsswitch.conf\fR(5) .SH NOTES .LP \fB/etc/inet/protocols\fR is the official SVR4 name of the \fBprotocols\fR diff --git a/usr/src/man/man5/prototype.5 b/usr/src/man/man5/prototype.5 index 9e53cd2ee7..4fe870a80d 100644 --- a/usr/src/man/man5/prototype.5 +++ b/usr/src/man/man5/prototype.5 @@ -180,7 +180,7 @@ A pathname can contain a variable specification of the form a build variable. If \fIvariable\fR begins with an upper case letter, it is an install variable. Build variables are bound at build time. If an install variable is known at build time, its definition is inserted into the -\fBpkginfo\fR(4) file so that it is available at install time. If an install +\fBpkginfo\fR(5) file so that it is available at install time. If an install variable is not known at build time, it is bound at install time. .RE @@ -219,7 +219,7 @@ The mode can be a variable specification of the form \fB$\fR\fIvariable.\fR If \fIvariable\fR begins with a lower case letter, it is a build variable. If \fIvariable\fR begins with an upper case letter, it is an install variable. Build variables are bound at build time. If an install variable is known at -build time, its definition is inserted into the \fBpkginfo\fR(4) file so that +build time, its definition is inserted into the \fBpkginfo\fR(5) file so that it is available at install time. If an install variable is not known at build time, it is bound at install time. .RE @@ -240,7 +240,7 @@ The owner can be a variable specification of the form \fB$\fR\fIvariable.\fR If \fIvariable\fR begins with a lower case letter, it is a build variable. If \fIvariable\fR begins with an upper case letter, it is an install variable. Build variables are bound at build time. If an install variable is known at -build time, its definition is inserted into the \fBpkginfo\fR(4) file so that +build time, its definition is inserted into the \fBpkginfo\fR(5) file so that it is available at install time. If an install variable is not known at build time, it is bound at install time. .RE @@ -261,7 +261,7 @@ The group can be a variable specification of the form \fB$\fR\fIvariable.\fR If \fIvariable\fR begins with a lower case letter, it is a build variable. If \fIvariable\fR begins with an upper case letter, it is an install variable. Build variables are bound at build time. If an install variable is known at -build time, its definition is inserted into the \fBpkginfo\fR(4) file so that +build time, its definition is inserted into the \fBpkginfo\fR(5) file so that it is available at install time. If an install variable is not known at build time, it is bound at install time. .RE @@ -392,7 +392,7 @@ d src /usr/wrap/src 0755 root bin .SH SEE ALSO .sp .LP -\fBpkgmk\fR(1), \fBpkginfo\fR(4) +\fBpkgmk\fR(1), \fBpkginfo\fR(5) .sp .LP \fIApplication Packaging Developer\&'s Guide\fR diff --git a/usr/src/man/man5/pseudo.5 b/usr/src/man/man5/pseudo.5 index 191e7f1c5f..cf2c20033f 100644 --- a/usr/src/man/man5/pseudo.5 +++ b/usr/src/man/man5/pseudo.5 @@ -23,7 +23,7 @@ Each entry in the configuration file creates a prototype devinfo node. Each node is assigned an instance number which is determined by the value of the \fIinstance\fR property. This property is only applicable to children of the \fIpseudo\fR parent, and is required since pseudo devices have no hardware -address from which to determine the instance number. See \fBdriver.conf\fR(4) +address from which to determine the instance number. See \fBdriver.conf\fR(5) for further details of configuration file syntax. .SH EXAMPLES .LP @@ -52,7 +52,7 @@ name="ramdisk" parent="pseudo" instance=1 disk-size=512;\fR .SH SEE ALSO .sp .LP -\fBdriver.conf\fR(4), \fBddi_prop_op\fR(9F) +\fBdriver.conf\fR(5), \fBddi_prop_op\fR(9F) .sp .LP \fIWriting Device Drivers\fR diff --git a/usr/src/man/man5/publickey.5 b/usr/src/man/man5/publickey.5 index c651427423..5203e42f25 100644 --- a/usr/src/man/man5/publickey.5 +++ b/usr/src/man/man5/publickey.5 @@ -26,5 +26,5 @@ password (also in hex notation). The \fB/etc/publickey\fR file contains a default entry for \fBnobody\fR. .SH SEE ALSO .LP -\fBchkey\fR(1), \fBnewkey\fR(1M), \fBgetpublickey\fR(3NSL), -\fBnsswitch.conf\fR(4) +\fBchkey\fR(1), \fBnewkey\fR(8), \fBgetpublickey\fR(3NSL), +\fBnsswitch.conf\fR(5) diff --git a/usr/src/man/man5/queuedefs.5 b/usr/src/man/man5/queuedefs.5 index d310c67603..1f97750dfa 100644 --- a/usr/src/man/man5/queuedefs.5 +++ b/usr/src/man/man5/queuedefs.5 @@ -16,7 +16,7 @@ queuedefs \- queue description file for at, batch, and cron .sp .LP The \fBqueuedefs\fR file describes the characteristics of the queues managed by -\fBcron\fR(1M). Each non-comment line in this file describes one queue. The +\fBcron\fR(8). Each non-comment line in this file describes one queue. The format of the lines are as follows: .sp .LP @@ -99,7 +99,7 @@ run it. .LP The \fBb\fR queue, for \fBbatch\fR(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a \fBnice\fR(1) value of 2. If a -job cannot be run because too many other jobs are running, \fBcron\fR(1M) will +job cannot be run because too many other jobs are running, \fBcron\fR(8) will wait 90 seconds before trying again to run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a \fBnice\fR value of 2, and if a job cannot be run because too many other jobs are running \fBcron\fR @@ -118,4 +118,4 @@ queue description file for \fBat\fR, \fBbatch\fR, and \fBcron\fR. .SH SEE ALSO .sp .LP -\fBat\fR(1), \fBcrontab\fR(1), \fBnice\fR(1), \fBcron\fR(1M) +\fBat\fR(1), \fBcrontab\fR(1), \fBnice\fR(1), \fBcron\fR(8) diff --git a/usr/src/man/man5/rcmscript.5 b/usr/src/man/man5/rcmscript.5 index c8e5207e1f..a817bcf8aa 100644 --- a/usr/src/man/man5/rcmscript.5 +++ b/usr/src/man/man5/rcmscript.5 @@ -349,7 +349,7 @@ Logging is discussed below. .el o \fBTZ\fR .RE -See \fBenviron\fR(5) for a description of these variables. See \fBgettext\fR(1) +See \fBenviron\fR(7) for a description of these variables. See \fBgettext\fR(1) for details on retrieving localized messages. .RE .sp @@ -622,8 +622,8 @@ pair \fBrcm_failure_reason\fR and exit with status 1. .SS "Logging" .LP A script must log all error and debug messages by writing to stdout the -name-value pairs listed below. The logged messages go to \fBsyslogd\fR(1M) with -the \fBsyslog\fR facility of \fBLOG_DAEMON\fR. See \fBsyslog.conf\fR(4). +name-value pairs listed below. The logged messages go to \fBsyslogd\fR(8) with +the \fBsyslog\fR facility of \fBLOG_DAEMON\fR. See \fBsyslog.conf\fR(5). .sp .ne 2 .na @@ -954,7 +954,7 @@ where \fIfailure_reason\fR is a localized human readable message describing the reason for failure of the RCM command. .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -969,9 +969,9 @@ Interface Stability Evolving .SH SEE ALSO .LP -\fBgettext\fR(1), \fBcfgadm\fR(1M), \fBcfgadm_scsi\fR(1M), -\fBcfgadm_pci\fR(1M), \fBsyslog\fR(3C), \fBsignal.h\fR(3HEAD), -\fBsyslog.conf\fR(4), \fBattributes\fR(5), \fBenviron\fR(5) +\fBgettext\fR(1), \fBcfgadm\fR(8), \fBcfgadm_scsi\fR(8), +\fBcfgadm_pci\fR(8), \fBsyslog\fR(3C), \fBsignal.h\fR(3HEAD), +\fBsyslog.conf\fR(5), \fBattributes\fR(7), \fBenviron\fR(7) .SH NOTES .LP RCM scripts are expected to properly handle all RCM commands that the script diff --git a/usr/src/man/man5/remote.5 b/usr/src/man/man5/remote.5 index 3ecf816e7d..ad8eb2cdd2 100644 --- a/usr/src/man/man5/remote.5 +++ b/usr/src/man/man5/remote.5 @@ -388,7 +388,7 @@ default is \fBnone\fR. .RS 6n \fB(str)\fR Telephone number(s) for this host. If the telephone number field contains an `\fB@\fR' sign, \fBtip\fR searches the \fB/etc/phones\fR file for a -list of telephone numbers \(em see \fBphones\fR(4). A `\fB%\fR' sign in the +list of telephone numbers \(em see \fBphones\fR(5). A `\fB%\fR' sign in the telephone number indicates a 5-second delay for the Ventel Modem. .sp For Hayes-compatible modems, if the telephone number starts with an 'S', the @@ -520,7 +520,7 @@ remote host phone number database. .SH SEE ALSO .sp .LP -\fBtip\fR(1), \fBphones\fR(4) +\fBtip\fR(1), \fBphones\fR(5) .sp .LP \fISystem Administration Guide: IP Services\fR diff --git a/usr/src/man/man5/resolv.conf.5 b/usr/src/man/man5/resolv.conf.5 index 01b6bc7229..c74fb0e9f3 100644 --- a/usr/src/man/man5/resolv.conf.5 +++ b/usr/src/man/man5/resolv.conf.5 @@ -232,7 +232,7 @@ white space. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -248,9 +248,9 @@ Interface Stability Standard BIND 8.3.3 .SH SEE ALSO .sp .LP -\fBdomainname\fR(1M), \fBsysinfo\fR(2), \fBgethostbyname\fR(3NSL), +\fBdomainname\fR(8), \fBsysinfo\fR(2), \fBgethostbyname\fR(3NSL), \fBgetnameinfo\fR(3SOCKET), \fBgetipnodebyname\fR(3SOCKET), -\fBgethostname\fR(3C), \fBresolver\fR(3RESOLV), \fBattributes\fR(5) +\fBgethostname\fR(3C), \fBresolver\fR(3RESOLV), \fBattributes\fR(7) .sp .LP Vixie, Paul, Dunlap, Keven J., Karels, Michael J. \fIName Server Operations diff --git a/usr/src/man/man5/rmtab.5 b/usr/src/man/man5/rmtab.5 index c8862c78cf..afde9c6484 100644 --- a/usr/src/man/man5/rmtab.5 +++ b/usr/src/man/man5/rmtab.5 @@ -17,8 +17,8 @@ rmtab \- remote mounted file system table .sp .LP \fBrmtab\fR contains a table of filesystems that are remotely mounted by -\fBNFS\fR clients. This file is maintained by \fBmountd\fR(1M), the mount -daemon. The data in this file should be obtained only from \fBmountd\fR(1M) +\fBNFS\fR clients. This file is maintained by \fBmountd\fR(8), the mount +daemon. The data in this file should be obtained only from \fBmountd\fR(8) using the \fBMOUNTPROC_DUMP\fR remote procedure call. .sp .LP @@ -38,7 +38,7 @@ mount request and deletes the appropriate entries for an unmount request. .sp .LP Lines beginning with a hash (' \fB#\fR') are commented out. These lines are -removed from the file by \fBmountd\fR(1M) when it first starts up. Stale +removed from the file by \fBmountd\fR(8) when it first starts up. Stale entries may accumulate for clients that crash without sending an unmount request. .SH FILES @@ -54,4 +54,4 @@ request. .SH SEE ALSO .sp .LP -\fBmountd\fR(1M), \fBshowmount\fR(1M) +\fBmountd\fR(8), \fBshowmount\fR(8) diff --git a/usr/src/man/man5/rpc.5 b/usr/src/man/man5/rpc.5 index 3d9d5dc289..dec87ed5ec 100644 --- a/usr/src/man/man5/rpc.5 +++ b/usr/src/man/man5/rpc.5 @@ -74,4 +74,4 @@ keyserv 100029 keyserver .SH SEE ALSO .LP -\fBnsswitch.conf\fR(4) +\fBnsswitch.conf\fR(5) diff --git a/usr/src/man/man5/rt_dptbl.5 b/usr/src/man/man5/rt_dptbl.5 index aaedce125a..f1818732f3 100644 --- a/usr/src/man/man5/rt_dptbl.5 +++ b/usr/src/man/man5/rt_dptbl.5 @@ -42,7 +42,7 @@ described in the \fB/usr/include/sys/rt.h\fR header file. .ad .RS 14n The global scheduling priority associated with this priority level. The -\fBrt_globpri\fR values cannot be changed with \fBdispadmin\fR(1M). +\fBrt_globpri\fR values cannot be changed with \fBdispadmin\fR(8). .RE .sp @@ -69,7 +69,7 @@ absolute time. An administrator can affect the behavior of the real-time portion of the scheduler by reconfiguring the \fBrt_dptbl\fR. There are two methods available for doing this: reconfigure with a loadable module at boot-time or by using -\fBdispadmin\fR(1M) at run-time. +\fBdispadmin\fR(8) at run-time. .SS "rt_dptbl Loadable Module" The \fBrt_dptbl\fR can be reconfigured with a loadable module which contains a new real time dispatch table. The module containing the dispatch table is @@ -80,7 +80,7 @@ real time class. The relevant procedure and source code is described in the Examples section. .SS "dispadmin Configuration File" The \fBrt_quantum\fR values in the \fBrt_dptbl\fR can be examined and modified -on a running system using the \fBdispadmin\fR(1M) command. Invoking +on a running system using the \fBdispadmin\fR(8) command. Invoking \fBdispadmin\fR for the real-time class allows the administrator to retrieve the current \fBrt_dptbl\fR configuration from the kernel's in-core table, or overwrite the in-core table with values from a configuration file. The @@ -201,7 +201,7 @@ Replace the current \fBRT_DPTBL\fR in \fB/usr/kernel/sched\fR. .TP 5. You will have to make changes in the \fB/etc/system\fR file to reflect the -changes to the sizes of the tables. See \fBsystem\fR(4). The \fBrt_maxpri\fR +changes to the sizes of the tables. See \fBsystem\fR(5). The \fBrt_maxpri\fR variable may need changing. The syntax for setting this is: .sp .in +2 @@ -336,7 +336,7 @@ rtdpent_t config_rt_dptbl[] = { .in -2 .SH SEE ALSO -\fBpriocntl\fR(1), \fBdispadmin\fR(1M), \fBpriocntl\fR(2), \fBsystem\fR(4) +\fBpriocntl\fR(1), \fBdispadmin\fR(8), \fBpriocntl\fR(2), \fBsystem\fR(5) .sp .LP \fISystem Administration Guide: Basic Administration\fR diff --git a/usr/src/man/man5/sasl_appname.conf.5 b/usr/src/man/man5/sasl_appname.conf.5 index 906d394b73..1b1b08ffbe 100644 --- a/usr/src/man/man5/sasl_appname.conf.5 +++ b/usr/src/man/man5/sasl_appname.conf.5 @@ -151,7 +151,7 @@ the GSS client security context. The default value of \fBuser_authid\fR is .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -167,4 +167,4 @@ Interface Stability Evolving .SH SEE ALSO .sp .LP -\fBattributes\fR(5) +\fBattributes\fR(7) diff --git a/usr/src/man/man5/sbus.5 b/usr/src/man/man5/sbus.5 index 6fa44f185b..62388be469 100644 --- a/usr/src/man/man5/sbus.5 +++ b/usr/src/man/man5/sbus.5 @@ -22,7 +22,7 @@ The information is usually derived from a small Forth program stored in the \fBFCode\fR \fBPROM\fR on the card, so driver configuration files should be completely unnecessary for these devices. However, on some occasions, drivers for \fBSBus\fR devices may need to use driver configuration files to augment -the information provided by the \fBSBus\fR card. See \fBdriver.conf\fR(4) for +the information provided by the \fBSBus\fR card. See \fBdriver.conf\fR(5) for further details. .sp .LP @@ -158,7 +158,7 @@ name="SUNW,netboard" class="sbus" .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -173,7 +173,7 @@ Architecture SPARC .SH SEE ALSO .LP -\fBdriver.conf\fR(4), \fBattributes\fR(5), \fBddi_add_intr\fR(9F), +\fBdriver.conf\fR(5), \fBattributes\fR(7), \fBddi_add_intr\fR(9F), \fBddi_map_regs\fR(9F), \fBddi_prop_op\fR(9F) .sp .LP diff --git a/usr/src/man/man5/scsi.5 b/usr/src/man/man5/scsi.5 index a76e55c24c..4a5dca3147 100644 --- a/usr/src/man/man5/scsi.5 +++ b/usr/src/man/man5/scsi.5 @@ -9,7 +9,7 @@ scsi \- configuration files for SCSI target drivers .SH DESCRIPTION The architecture of the illumos \fBSCSI\fR subsystem distinguishes two types of device drivers: \fBSCSI\fR target drivers, and \fBSCSI\fR host adapter drivers. -Target drivers like \fBsd\fR(7D) and \fBst\fR(7D) manage the device on the +Target drivers like \fBsd\fR(4D) and \fBst\fR(4D) manage the device on the other end of the \fBSCSI\fR bus. Host adapter drivers manage the \fBSCSI\fR bus on behalf of all the devices that share it. .sp @@ -22,13 +22,13 @@ for further details of these, and associated routines. .sp .LP Depending on the interconnect (transport), SCSI target devices are either -self-identifying or rely on \fBdriver.conf\fR(4) entries to be recognized by +self-identifying or rely on \fBdriver.conf\fR(5) entries to be recognized by the system. For self-identifying target devices the driver binding is chosen based on the IEEE-1275 like 'compatible' forms of the target devices. Currently -the Fibre Channel interconnects, \fBfcp\fR(7D), \fBifp\fR(7D), -\fBscsi_vhci\fR(7D), \fBsf\fR(7D), and the SATA framework drivers (see -\fBsata\fR(7D)) are self-identifying. You must specify other possible -interconnects target devices by using the target driver \fBdriver.conf\fR(4) +the Fibre Channel interconnects, \fBfcp\fR(4D), \fBifp\fR(4D), +\fBscsi_vhci\fR(4D), \fBsf\fR(4D), and the SATA framework drivers (see +\fBsata\fR(4D)) are self-identifying. You must specify other possible +interconnects target devices by using the target driver \fBdriver.conf\fR(5) configuration files. .SS "Self-Identifying" Host adapter drivers of class scsi-self-identifying that dynamically create @@ -37,8 +37,8 @@ on each child. The compatible property is an ordered array of strings, each string is a compatible \fBform\fR. High precedence forms are defined first. For a particular device, the highest precedence form that has an established driver alias selects the driver for the device. Driver associations to compatible -forms, called aliases, are administered by way of \fBadd_drv\fR(1M), -\fBupdate_drv\fR(1M), and \fBrem_drv\fR(1M) utilities. +forms, called aliases, are administered by way of \fBadd_drv\fR(8), +\fBupdate_drv\fR(8), and \fBrem_drv\fR(8) utilities. .sp .LP The forms for self-identifying SCSI target devices are derived from the SCSI @@ -292,7 +292,7 @@ in the file shipped with illumos. .LP The following line is a stub device definition which implies the host adapter drivers of class scsi-self-identifying might have children that bind to the -\fBsd\fR(7D) driver: +\fBsd\fR(4D) driver: .sp .in +2 @@ -303,7 +303,7 @@ name="sd" class="scsi-self-identifying"; .sp .SH ATTRIBUTES -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -317,9 +317,9 @@ Interface Stability Committed .TE .SH SEE ALSO -\fBadd_drv\fR(1M), \fBrem_drv\fR(1M), \fBupdate_drv\fR(1M), -\fBdriver.conf\fR(4), \fBattributes\fR(5), \fBfcp\fR(7D), \fBifp\fR(7D), -\fBsata\fR(7D), \fBscsi_vhci\fR(7D), \fBsd\fR(7D), \fBsf\fR(7D), \fBst\fR(7D), +\fBadd_drv\fR(8), \fBrem_drv\fR(8), \fBupdate_drv\fR(8), +\fBdriver.conf\fR(5), \fBattributes\fR(7), \fBfcp\fR(4D), \fBifp\fR(4D), +\fBsata\fR(4D), \fBscsi_vhci\fR(4D), \fBsd\fR(4D), \fBsf\fR(4D), \fBst\fR(4D), \fBscsi_ifgetcap\fR(9F), \fBscsi_init_pkt\fR(9F), \fBscsi_transport\fR(9F) .sp .LP @@ -337,7 +337,7 @@ Interface Stability Committed .LP \fIIEEE 1275 SCSI Target Device Binding\fR .SH NOTES -With \fBdriver.conf\fR(4) configuration, you need to ensure that the +With \fBdriver.conf\fR(5) configuration, you need to ensure that the \fBtarget\fR and \fBlun\fR values claimed by your target driver do not conflict with existing target drivers on the system. For example, if the target is a direct access device, the standard \fBsd.conf\fR file usually makes \fBsd\fR diff --git a/usr/src/man/man5/securenets.5 b/usr/src/man/man5/securenets.5 index 0533e7e7a3..cb000fd3f3 100644 --- a/usr/src/man/man5/securenets.5 +++ b/usr/src/man/man5/securenets.5 @@ -41,13 +41,13 @@ indicating that the second field is a specific host to be allowed access. .RE .sp .LP -Both \fBypserv\fR(1M) and \fBypxfrd\fR(1M) use the \fB/var/yp/securenets\fR -file. The file is read when the \fBypserv\fR(1M) and \fBypxfrd\fR(1M) daemons -begin. If \fB/var/yp/securenets\fR is present, \fBypserv\fR(1M) and -\fBypxfrd\fR(1M) respond only to \fBIP\fR addresses in the range given. In +Both \fBypserv\fR(8) and \fBypxfrd\fR(8) use the \fB/var/yp/securenets\fR +file. The file is read when the \fBypserv\fR(8) and \fBypxfrd\fR(8) daemons +begin. If \fB/var/yp/securenets\fR is present, \fBypserv\fR(8) and +\fBypxfrd\fR(8) respond only to \fBIP\fR addresses in the range given. In order for a change in the \fB/var/yp/securenets\fR file to take effect, you -must kill and restart any active daemons using \fBypstop\fR(1M) and -\fBypstart\fR(1M). +must kill and restart any active daemons using \fBypstop\fR(8) and +\fBypstart\fR(8). .sp .LP An important thing to note for all the examples below is that the server must @@ -166,7 +166,7 @@ Configuration file for \fBNIS\fR security. .RE .SH SEE ALSO -\fBypserv\fR(1M), \fBypstart\fR(1M), \fBypstop\fR(1M), \fBypxfrd\fR(1M) +\fBypserv\fR(8), \fBypstart\fR(8), \fBypstop\fR(8), \fBypxfrd\fR(8) .SH NOTES The Network Information Service (NIS) was formerly known as Sun Yellow Pages (YP). The functionality of the two remains the same; only the name has diff --git a/usr/src/man/man5/sendmail.5 b/usr/src/man/man5/sendmail.5 index 0de1fbe117..c5e8aa03d5 100644 --- a/usr/src/man/man5/sendmail.5 +++ b/usr/src/man/man5/sendmail.5 @@ -20,7 +20,7 @@ sendmail, sendmail.cf, submit.cf \- sendmail configuration files .SH DESCRIPTION .LP The \fBsendmail.cf\fR and \fBsubmit.cf\fR files are the configuration files for -\fBsendmail\fR(1M). Starting with version 8.12 of \fBsendmail\fR, which was +\fBsendmail\fR(8). Starting with version 8.12 of \fBsendmail\fR, which was shipped with version 9 of the Solaris operating system, two configuration files are used for submission and transmission of mail, instead of only \fBsendmail.cf\fR, as before. These are: @@ -222,7 +222,7 @@ take effect. Steps 4 and 5 can be automated. See \fBAutomated Rebuilding of Configuration Files\fR below. .SS "Enabling Access to Remote Clients" .LP -The \fBsendmail\fR(1M) man page describes how the \fBconfig/local_only\fR +The \fBsendmail\fR(8) man page describes how the \fBconfig/local_only\fR property can be set to \fBtrue\fR or \fBfalse\fR to disallow or allow, respectively, access to remote clients for unmodified systems. .sp @@ -273,7 +273,7 @@ Describes \fBsendmail\fR configuration files. .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -288,8 +288,8 @@ Interface Stability Committed .SH SEE ALSO .LP -\fBmake\fR(1S), \fBps\fR(1), \fBsendmail\fR(1M), \fBsvcadm\fR(1M), -\fBattributes\fR(5) +\fBmake\fR(1S), \fBps\fR(1), \fBsendmail\fR(8), \fBsvcadm\fR(8), +\fBattributes\fR(7) .sp .LP \fISystem Administration Guide: Network Services\fR diff --git a/usr/src/man/man5/service_bundle.5 b/usr/src/man/man5/service_bundle.5 index 948b81a207..7f42649dcb 100644 --- a/usr/src/man/man5/service_bundle.5 +++ b/usr/src/man/man5/service_bundle.5 @@ -15,7 +15,7 @@ service_bundle \- service manifest file format .SH DESCRIPTION .sp .LP -The service management facility, described in \fBsmf\fR(5), utilizes an +The service management facility, described in \fBsmf\fR(7), utilizes an XML-based file format to marshal the description of a set of services or service instances between systems. This file is known as a service bundle. The primary form of a service bundle is the inventory of services that are provided @@ -59,7 +59,7 @@ of each instance .TP .ie t \(bu .el o -A set of method property groups as required by \fBsvc.startd\fR(1M), or by a +A set of method property groups as required by \fBsvc.startd\fR(8), or by a delegated restarter .RE .RS +4 @@ -107,22 +107,22 @@ that identify regular features in describing a service, such as the .LP Service manifests within packages should be identified with the class \fBmanifest\fR. Class action scripts that install and remove service manifests -are included in the packaging subsystem. When \fBpkgadd\fR(1M) is invoked, the +are included in the packaging subsystem. When \fBpkgadd\fR(8) is invoked, the service manifest is imported. .sp .LP -When \fBpkgrm\fR(1M) is invoked, instances in the manifest that are disabled +When \fBpkgrm\fR(8) is invoked, instances in the manifest that are disabled are deleted. Any services in the manifest with no remaining instances are also deleted. .sp .LP -If the \fB-R\fR option is supplied to \fBpkgadd\fR(1M) or \fBpkgrm\fR(1M), the +If the \fB-R\fR option is supplied to \fBpkgadd\fR(8) or \fBpkgrm\fR(8), the actions described in this section are done when the system is next rebooted with that alternate root path. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -138,9 +138,9 @@ Stability Committed .SH SEE ALSO .sp .LP -\fBpkgadd\fR(1M), \fBpkgrm\fR(1M), \fBsvcadm\fR(1M), \fBsvccfg\fR(1M), -\fBsvc.startd\fR(1M), \fBlibscf\fR(3LIB), \fBattributes\fR(5), \fBlocale\fR(5), -\fBsmf\fR(5), \fBsmf_method\fR(5), \fBsmf_template\fR(5) +\fBpkgadd\fR(8), \fBpkgrm\fR(8), \fBsvcadm\fR(8), \fBsvccfg\fR(8), +\fBsvc.startd\fR(8), \fBlibscf\fR(3LIB), \fBattributes\fR(7), \fBlocale\fR(7), +\fBsmf\fR(7), \fBsmf_method\fR(7), \fBsmf_template\fR(7) .SH NOTES .sp .LP diff --git a/usr/src/man/man5/service_provider.conf.5 b/usr/src/man/man5/service_provider.conf.5 index d5563a2a3b..a76121d685 100644 --- a/usr/src/man/man5/service_provider.conf.5 +++ b/usr/src/man/man5/service_provider.conf.5 @@ -17,9 +17,9 @@ service_provider.conf \- service provider configuration file \fBservice_provider.conf\fR contains information about the device type that the service provider supports. This information includes the pathname of the service provider library, the library version and other library characteristics -that are required by the system administrative command, \fBdatadm\fR(1M). -\fBdatadm\fR(1M) puts this information in the DAT static register file, -\fBdat.conf\fR(4). +that are required by the system administrative command, \fBdatadm\fR(8). +\fBdatadm\fR(8) puts this information in the DAT static register file, +\fBdat.conf\fR(5). .sp .LP The \fBdatadm\fR program enumerates each device entry into a list of interface @@ -166,7 +166,7 @@ pci15b3,5a44 u1.2 nonthreadsafe default \e .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -180,4 +180,4 @@ Stability Evolving .SH SEE ALSO .LP -\fBdatadm\fR(1M), \fBdat.conf\fR(4), \fBattributes\fR(5) +\fBdatadm\fR(8), \fBdat.conf\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man5/services.5 b/usr/src/man/man5/services.5 index 3926bb853e..51045c97df 100644 --- a/usr/src/man/man5/services.5 +++ b/usr/src/man/man5/services.5 @@ -86,7 +86,7 @@ configuration file for name-service switch .SH SEE ALSO .LP -\fBgetservbyname\fR(3SOCKET), \fBinetd.conf\fR(4), \fBnsswitch.conf\fR(4) +\fBgetservbyname\fR(3SOCKET), \fBinetd.conf\fR(5), \fBnsswitch.conf\fR(5) .SH NOTES .LP \fB/etc/inet/services\fR is the official SVR4 name of the \fBservices\fR file. diff --git a/usr/src/man/man5/shadow.5 b/usr/src/man/man5/shadow.5 index 054448d903..0944af3012 100644 --- a/usr/src/man/man5/shadow.5 +++ b/usr/src/man/man5/shadow.5 @@ -136,14 +136,14 @@ The encrypted password consists of at most \fBCRYPT_MAXCIPHERTEXTLEN\fR characters chosen from a 64-character alphabet (\fB\&.\fR, \fB/\fR, \fB0\(mi9\fR, \fBA\(miZ\fR, \fBa\(miz\fR). Two additional special characters, "$" and ",", can also be used and are defined in \fBcrypt\fR(3C). To update -this file, use the \fBpasswd\fR(1), \fBuseradd\fR(1M), \fBusermod\fR(1M), or -\fBuserdel\fR(1M) commands. +this file, use the \fBpasswd\fR(1), \fBuseradd\fR(8), \fBusermod\fR(8), or +\fBuserdel\fR(8) commands. .sp .LP In order to make system administration manageable, \fB/etc/shadow\fR entries should appear in exactly the same order as \fB/etc/passwd\fR entries; this includes ``+'' and ``-'' entries if the \fBcompat\fR source is being used (see -\fBnsswitch.conf\fR(4)). +\fBnsswitch.conf\fR(5)). .sp .LP Values for the various time-related fields are interpreted as Greenwich Mean @@ -186,7 +186,7 @@ time of last login .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -201,19 +201,19 @@ Interface Stability Stable .SH SEE ALSO .LP -\fBlogin\fR(1), \fBpasswd\fR(1), \fBuseradd\fR(1M), \fBuserdel\fR(1M), -\fBusermod\fR(1M), \fBstrtol\fR(3C), \fBcrypt\fR(3C), \fBcrypt_gensalt\fR(3C), -\fBgetspnam\fR(3C), \fBputspent\fR(3C), \fBnsswitch.conf\fR(4), -\fBpasswd\fR(4), \fBattributes\fR(5), \fBpam_unix_account\fR(5), -\fBpam_unix_auth\fR(5) +\fBlogin\fR(1), \fBpasswd\fR(1), \fBuseradd\fR(8), \fBuserdel\fR(8), +\fBusermod\fR(8), \fBstrtol\fR(3C), \fBcrypt\fR(3C), \fBcrypt_gensalt\fR(3C), +\fBgetspnam\fR(3C), \fBputspent\fR(3C), \fBnsswitch.conf\fR(5), +\fBpasswd\fR(5), \fBattributes\fR(7), \fBpam_unix_account\fR(7), +\fBpam_unix_auth\fR(7) .SH NOTES .LP If password aging is turned on in any name service the \fIpasswd:\fR line in the \fB/etc/nsswitch.conf\fR file must have a format specified in the -\fBnsswitch.conf\fR(4) man page. +\fBnsswitch.conf\fR(5) man page. .sp .LP If the \fB/etc/nsswitch.conf\fR passwd policy is not in one of the supported formats, logins will not be allowed upon password expiration, because the software does not know how to handle password updates under these conditions. -See \fBnsswitch.conf\fR(4) for additional information. +See \fBnsswitch.conf\fR(5) for additional information. diff --git a/usr/src/man/man5/sharetab.5 b/usr/src/man/man5/sharetab.5 index 7e9048dda9..5e7976b030 100644 --- a/usr/src/man/man5/sharetab.5 +++ b/usr/src/man/man5/sharetab.5 @@ -70,4 +70,4 @@ resource was shared. .SH SEE ALSO .sp .LP -\fBshare\fR(1M) +\fBshare\fR(8) diff --git a/usr/src/man/man5/shells.5 b/usr/src/man/man5/shells.5 index ff51fd3a0f..e66bc8d52d 100644 --- a/usr/src/man/man5/shells.5 +++ b/usr/src/man/man5/shells.5 @@ -53,5 +53,5 @@ list of shells on system .SH SEE ALSO .sp .LP -\fBvipw\fR(1B), \fBftpd\fR(1M), \fBsendmail\fR(1M), \fBgetusershell\fR(3C), -\fBaliases\fR(4) +\fBvipw\fR(1B), \fBftpd\fR(8), \fBsendmail\fR(8), \fBgetusershell\fR(3C), +\fBaliases\fR(5) diff --git a/usr/src/man/man5/slp.conf.5 b/usr/src/man/man5/slp.conf.5 index 83c510ae72..e4af8b1d3d 100644 --- a/usr/src/man/man5/slp.conf.5 +++ b/usr/src/man/man5/slp.conf.5 @@ -16,7 +16,7 @@ slp.conf \- configuration file for Service Location Protocol agents .sp .LP \fBslp.conf \fR provides all Service Location Protocol ("\fBSLP\fR") agents -with their operational configuration. \fBslpd\fR(1M) reads \fBslp.conf\fR on +with their operational configuration. \fBslpd\fR(8) reads \fBslp.conf\fR on startup. Service Agents ("\fBSA\fRs") and User Agents ("\fBUA\fRs") read \fBslp.conf\fR on invocation of the \fBSA\fR and \fBUA\fR library routines; configuration parameters are then cached on a per-process basis. All \fBSA\fR's @@ -140,8 +140,8 @@ Boolean \fBTrue\fR or \fBFalse\fR .RE -A boolean that indicates whether \fBslpd\fR(1M) is to act as a \fBDA\fR. If -\fBFalse\fR, \fBslpd\fR(1M) is not run as a \fBDA\fR. +A boolean that indicates whether \fBslpd\fR(8) is to act as a \fBDA\fR. If +\fBFalse\fR, \fBslpd\fR(8) is not run as a \fBDA\fR. .RE .sp @@ -310,7 +310,7 @@ IPv4 addresses or host names A list of \fBIP\fR addresses or \fBDNS\fR-resolvable names that denote the \fBDA\fRs to use for statically configured \fBUA\fRs and \fBSA\fRs. The -property is read by \fBslpd\fR(1M), and registrations are forwarded to the +property is read by \fBslpd\fR(8), and registrations are forwarded to the \fBDA\fRs. The \fBDA\fRs are provided to \fBUA\fRs upon request. Unlike other properties, this property is "read-only", so attempts to change it after the configuration file has been read are ignored. @@ -347,7 +347,7 @@ changed. .LP These properties direct tracing and logging information to be sent to \fBsyslogd\fR at the \fBLOG_INFO\fR priority. These properties affect -\fBslpd\fR(1M) only. +\fBslpd\fR(8) only. .sp .ne 2 .na @@ -1113,7 +1113,7 @@ type. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -1131,7 +1131,7 @@ Interface Stability Standard .SH SEE ALSO .sp .LP -\fBslpd\fR(1M), \fBslpd.reg\fR(4), \fBslp_api\fR(3SLP), \fBslp\fR(7P) +\fBslpd\fR(8), \fBslpd.reg\fR(5), \fBslp_api\fR(3SLP), \fBslp\fR(4P) .sp .LP \fISystem Administration Guide: Network Services\fR diff --git a/usr/src/man/man5/slpd.reg.5 b/usr/src/man/man5/slpd.reg.5 index 077ae44dff..b2601420df 100644 --- a/usr/src/man/man5/slpd.reg.5 +++ b/usr/src/man/man5/slpd.reg.5 @@ -16,11 +16,11 @@ daemon (slpd) .SH DESCRIPTION .LP The serialized registration file contains a group of registrations that -\fBslpd\fR(1M) registers when it starts. These registrations are primarily for +\fBslpd\fR(8) registers when it starts. These registrations are primarily for older service programs that do not internally support \fBSLP\fR and cannot be converted. The character format of the registration file is required to be \fBASCII\fR. To use serialized registrations, set the -\fBnet.slp.serializedRegURL\fR property in \fBslp.conf\fR(4) to point at a +\fBnet.slp.serializedRegURL\fR property in \fBslp.conf\fR(5) to point at a valid \fBslpd.reg\fR file. The syntax of the serialized registration file, in \fBABNF\fR format (see \fIRFC 2234\fR), is as follows: .sp @@ -115,7 +115,7 @@ location=headquarters .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -132,8 +132,8 @@ Interface Stability Standard .SH SEE ALSO .LP -\fBslpd\fR(1M), \fBslp_api\fR(3SLP), \fBsyslog\fR(3C), \fBslp.conf\fR(4), -\fBattributes\fR(5) +\fBslpd\fR(8), \fBslp_api\fR(3SLP), \fBsyslog\fR(3C), \fBslp.conf\fR(5), +\fBattributes\fR(7) .sp .LP Crocker, D. and Overell, P., \fIRFC 2234, Augmented BNF for Syntax diff --git a/usr/src/man/man5/smb.5 b/usr/src/man/man5/smb.5 index d94e07305d..762689c8b1 100644 --- a/usr/src/man/man5/smb.5 +++ b/usr/src/man/man5/smb.5 @@ -22,10 +22,10 @@ smb \- configuration properties for Solaris CIFS server .SH DESCRIPTION Behavior of the Solaris CIFS server is defined by property values that are -stored in the Service Management Facility, \fBsmf\fR(5). +stored in the Service Management Facility, \fBsmf\fR(7). .sp .LP -An authorized user can use the \fBsharectl\fR(1M) command to set global values +An authorized user can use the \fBsharectl\fR(8) command to set global values for these properties in SMF. .sp .LP @@ -440,7 +440,7 @@ on the server, is derived from the \fBmax_workers\fR value. To ensure compatibility with older versions of Windows the lower 8-bits of \fBmax_mpx\fR must not be zero. If the lower byte of \fBmax_workers\fR is zero, \fB64\fR is added to the value. Thus the minimum value is \fB64\fR and the default value, -which appears in \fBsharectl\fR(1M) as \fB1024\fR, is \fB1088\fR. +which appears in \fBsharectl\fR(8) as \fB1024\fR, is \fB1088\fR. .RE .sp @@ -598,7 +598,7 @@ set. .RE .SH ATTRIBUTES -See the \fBattributes\fR(5) man page for descriptions of the following +See the \fBattributes\fR(7) man page for descriptions of the following attributes: .sp @@ -613,5 +613,5 @@ Interface Stability Uncommitted .TE .SH SEE ALSO -\fBsharectl\fR(1M), \fBsmbadm\fR(1M), \fBsmbd\fR(1M), \fBsmbstat\fR(1M), -\fBattributes\fR(5), \fBsmf\fR(5) +\fBsharectl\fR(8), \fBsmbadm\fR(8), \fBsmbd\fR(8), \fBsmbstat\fR(8), +\fBattributes\fR(7), \fBsmf\fR(7) diff --git a/usr/src/man/man5/smbautohome.5 b/usr/src/man/man5/smbautohome.5 index dbc99ca05a..d6c12e0dd5 100644 --- a/usr/src/man/man5/smbautohome.5 +++ b/usr/src/man/man5/smbautohome.5 @@ -51,7 +51,7 @@ A map entry, which is also referred to as a mapping, uses the following format: .LP \fIkey\fR is a user name, \fIlocation\fR is the fully qualified path for the user's home directory, and \fIoptions\fR specifies the share options, for -example, an AD container or description. See \fBsharemgr\fR(1M) for information +example, an AD container or description. See \fBsharemgr\fR(8) for information on share options. .sp .LP @@ -181,7 +181,7 @@ The wildcard and \fBnsswitch\fR rules are mutually exclusive. Do not include an \fB/etc/smbautohome\fR .SH ATTRIBUTES .LP -See the \fBattributes\fR(5) man page for descriptions of the following +See the \fBattributes\fR(7) man page for descriptions of the following attributes: .sp @@ -197,5 +197,5 @@ Interface Stability Uncommitted .SH SEE ALSO .LP -\fBsharectl\fR(1M), \fBsharemgr\fR(1M), \fBsmbadm\fR(1M), \fBsmbd\fR(1M), -\fBsmbstat\fR(1M), \fBsmb\fR(4), \fBattributes\fR(5) +\fBsharectl\fR(8), \fBsharemgr\fR(8), \fBsmbadm\fR(8), \fBsmbd\fR(8), +\fBsmbstat\fR(8), \fBsmb\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man5/smhba.conf.5 b/usr/src/man/man5/smhba.conf.5 index 60ddc2ff46..1f33324bd6 100644 --- a/usr/src/man/man5/smhba.conf.5 +++ b/usr/src/man/man5/smhba.conf.5 @@ -66,7 +66,7 @@ com.sun.sashba64 /usr/lib/64/libsun_sas.so.1 .in -2 .SH ATTRIBUTES -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -84,7 +84,7 @@ T} .TE .SH SEE ALSO -\fBHBA_LoadLibrary\fR(3HBAAPI), \fBlibSMHBAAPI\fR(3LIB), \fBattributes\fR(5) +\fBHBA_LoadLibrary\fR(3HBAAPI), \fBlibSMHBAAPI\fR(3LIB), \fBattributes\fR(7) .SH NOTES The SMHBAAPI library is provided in both 32-and 64-bit versions, but only one configuration file is specified. As a result, both 32- and 64-bit VSL libraries diff --git a/usr/src/man/man5/sock2path.d.5 b/usr/src/man/man5/sock2path.d.5 index 977cefbe54..b1f9376ce4 100644 --- a/usr/src/man/man5/sock2path.d.5 +++ b/usr/src/man/man5/sock2path.d.5 @@ -18,10 +18,10 @@ sock2path.d \- socket mapping files that map sockets to transport providers \fB/etc/sock2path.d\fR is a directory containing files with mappings between the \fBsocket\fR(3SOCKET) call parameters and the transport provider driver. The mapping file format is described in the -\fBsoconfig\fR(1M) manual page. +\fBsoconfig\fR(8) manual page. .sp .LP -The \fBinit\fR(1M) utility uses the \fBsoconfig\fR utility with the +The \fBinit\fR(8) utility uses the \fBsoconfig\fR utility with the \fBsock2path.d\fR directory during the boot sequence. .SH EXAMPLES .LP @@ -55,4 +55,4 @@ The following is an example of a mapping file: .SH SEE ALSO .sp .LP -\fBinit\fR(1M), \fBsoconfig\fR(1M), \fBsocket\fR(3SOCKET) +\fBinit\fR(8), \fBsoconfig\fR(8), \fBsocket\fR(3SOCKET) diff --git a/usr/src/man/man5/space.5 b/usr/src/man/man5/space.5 index eceaf9f390..b266c3cfee 100644 --- a/usr/src/man/man5/space.5 +++ b/usr/src/man/man5/space.5 @@ -11,8 +11,8 @@ space \- disk space requirement file .LP \fBspace\fR is an \fBASCII\fR file that gives information about disk space requirements for the target environment. The \fBspace\fR file defines space -needed beyond what is used by objects defined in the \fBprototype\fR(4) file; -for example, files which will be installed with the \fBinstallf\fR(1M) command. +needed beyond what is used by objects defined in the \fBprototype\fR(5) file; +for example, files which will be installed with the \fBinstallf\fR(8) command. The \fBspace\fR file should define the maximum amount of additional space that a package will require. .sp @@ -71,7 +71,7 @@ data 500 1 .SH SEE ALSO .sp .LP -\fBinstallf\fR(1M), \fBprototype\fR(4) +\fBinstallf\fR(8), \fBprototype\fR(5) .sp .LP \fIApplication Packaging Developer\&'s Guide\fR diff --git a/usr/src/man/man5/sulog.5 b/usr/src/man/man5/sulog.5 index 1a73695357..a4073afae9 100644 --- a/usr/src/man/man5/sulog.5 +++ b/usr/src/man/man5/sulog.5 @@ -17,7 +17,7 @@ sulog \- su command log file .sp .LP The \fBsulog\fR file is a record of all attempts by users on the system to -execute the \fBsu\fR(1M) command. Each time \fBsu\fR(1M) is executed, an +execute the \fBsu\fR(8) command. Each time \fBsu\fR(8) is executed, an entry is added to the \fBsulog\fR file. .sp .LP @@ -40,7 +40,7 @@ where \fB\fBdate\fR\fR .ad .RS 11n -The month and date \fBsu\fR(1M) was executed. \fBdate\fR is displayed in the +The month and date \fBsu\fR(8) was executed. \fBdate\fR is displayed in the form \fImm\fR\fB/\fR\fBdd\fR where \fImm\fR is the month number and \fBdd\fR is the day number in the month. .RE @@ -51,7 +51,7 @@ is the day number in the month. \fB\fBtime\fR\fR .ad .RS 11n -The time \fBsu\fR(1M) was executed. \fBtime\fR is displayed in the form +The time \fBsu\fR(8) was executed. \fBtime\fR is displayed in the form \fIHH\fR\fB/\fR\fIMM\fR where \fIHH\fR is the hour number (24 hour system) and \fIMM\fR is the minute number. .RE @@ -62,7 +62,7 @@ The time \fBsu\fR(1M) was executed. \fBtime\fR is displayed in the form \fB\fIresult\fR\fR .ad .RS 11n -The result of the \fBsu\fR(1M) command. A ` + ' sign is displayed in this +The result of the \fBsu\fR(8) command. A ` + ' sign is displayed in this field if the su attempt was successful; otherwise a ` - ' sign is displayed. .RE @@ -72,7 +72,7 @@ field if the su attempt was successful; otherwise a ` - ' sign is displayed. \fB\fIport\fR\fR .ad .RS 11n -The name of the terminal device from which \fBsu\fR(1M) was executed. +The name of the terminal device from which \fBsu\fR(8) was executed. .RE .sp @@ -81,7 +81,7 @@ The name of the terminal device from which \fBsu\fR(1M) was executed. \fB\fIuser\fR\fR .ad .RS 11n -The user id of the user executing the \fBsu\fR(1M) command. +The user id of the user executing the \fBsu\fR(8) command. .RE .sp @@ -90,7 +90,7 @@ The user id of the user executing the \fBsu\fR(1M) command. \fB\fInewuser\fR\fR .ad .RS 11n -The user id being switched to with \fBsu\fR(1M). +The user id being switched to with \fBsu\fR(8). .RE .SH EXAMPLES @@ -136,4 +136,4 @@ contains the default location of \fBsulog\fR .SH SEE ALSO .sp .LP -\fBsu\fR(1M) +\fBsu\fR(8) diff --git a/usr/src/man/man5/sysbus.5 b/usr/src/man/man5/sysbus.5 index 4dff46d54d..0214f2eb1e 100644 --- a/usr/src/man/man5/sysbus.5 +++ b/usr/src/man/man5/sysbus.5 @@ -17,7 +17,7 @@ can occupy. .LP Configuration files for \fBISA\fR device drivers are only necessary to describe properties used by a particular driver that are not part of the standard -properties found in the device tree. See \fBdriver.conf\fR(4) for further +properties found in the device tree. See \fBdriver.conf\fR(5) for further details of configuration file syntax. .sp .LP @@ -85,7 +85,7 @@ The order of the tuples in the reg property is determined by the boot system probe code and depends on the characteristics of each particular device. However, the reg property maintains the same order of entries from system boot to system boot. The recommended way to determine the reg property for a -particular device is to use the \fBprtconf\fR(1M) command after installing the +particular device is to use the \fBprtconf\fR(8) command after installing the particular device. The output of the \fBprtconf\fR command can be examined to determine the reg property for any installed device. .sp @@ -104,7 +104,7 @@ devices that use DMA channels have a \fBdma-channels\fR property. .RE .SH ATTRIBUTES -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -118,7 +118,7 @@ Architecture x86 .TE .SH SEE ALSO -\fBprtconf\fR(1M), \fBdriver.conf\fR(4), \fBscsi\fR(4), \fBattributes\fR(5), +\fBprtconf\fR(8), \fBdriver.conf\fR(5), \fBscsi\fR(5), \fBattributes\fR(7), \fBddi_add_intr\fR(9F), \fBddi_intr_hilevel\fR(9F), \fBddi_map_regs\fR(9F), \fBddi_prop_op\fR(9F) .sp diff --git a/usr/src/man/man5/syslog.conf.5 b/usr/src/man/man5/syslog.conf.5 index b7174b2f58..dc01ec1a98 100644 --- a/usr/src/man/man5/syslog.conf.5 +++ b/usr/src/man/man5/syslog.conf.5 @@ -14,7 +14,7 @@ syslog.conf \- configuration file for syslogd system log daemon .SH DESCRIPTION .LP The file \fB/etc/syslog.conf\fR contains information used by the system log -daemon, \fBsyslogd\fR(1M), to forward a system message to appropriate log files +daemon, \fBsyslogd\fR(8), to forward a system message to appropriate log files and/or users. \fBsyslogd\fR preprocesses this file through \fBm4\fR(1) to obtain the correct information for certain log files, defining \fBLOGHOST\fR if the address of "loghost" is the same as one of the addresses of the host that @@ -93,7 +93,7 @@ Various system daemons. \fB\fBauth\fR\fR .ad .RS 12n -The authorization system: \fBlogin\fR(1), \fBsu\fR(1M), \fBgetty\fR(1M), among +The authorization system: \fBlogin\fR(1), \fBsu\fR(8), \fBgetty\fR(8), among others. .RE @@ -388,7 +388,7 @@ l l . .sp .LP -\fBsyslogd\fR(1M) logs all mail system messages except \fBdebug\fR messages and +\fBsyslogd\fR(8) logs all mail system messages except \fBdebug\fR messages and all \fBnotice\fR (or higher) messages into a file named \fB/var/log/notice\fR. It logs all critical messages into \fB/var/log/critical\fR, and all kernel messages and 20-minute marks onto the system console. @@ -403,7 +403,7 @@ logged in the file \fB/var/log/auth\fR. .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -419,6 +419,6 @@ Interface Stability Stable .SH SEE ALSO .LP \fBat\fR(1), \fBcrontab\fR(1), \fBlogger\fR(1), \fBlogin\fR(1), \fBlp\fR(1), -\fBlpc\fR(1B), \fBlpr\fR(1B), \fBm4\fR(1), \fBcron\fR(1M), \fBgetty\fR(1M), -\fBin.ftpd\fR(1M), \fBsu\fR(1M), \fBsyslogd\fR(1M), \fBsyslog\fR(3C), -\fBhosts\fR(4), \fBattributes\fR(5) +\fBlpc\fR(1B), \fBlpr\fR(1B), \fBm4\fR(1), \fBcron\fR(8), \fBgetty\fR(8), +\fBin.ftpd\fR(8), \fBsu\fR(8), \fBsyslogd\fR(8), \fBsyslog\fR(3C), +\fBhosts\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man5/system.5 b/usr/src/man/man5/system.5 index a0c7473cfa..ab77b9bf2b 100644 --- a/usr/src/man/man5/system.5 +++ b/usr/src/man/man5/system.5 @@ -351,7 +351,7 @@ set moddebug | 0x40 .SH SEE ALSO .LP -\fBboot\fR(1M), \fBinit\fR(1M), \fBkernel\fR(1M) +\fBboot\fR(8), \fBinit\fR(8), \fBkernel\fR(8) .SH WARNINGS .LP Use care when modifying the \fBsystem\fR file; it modifies the operation of the diff --git a/usr/src/man/man5/term.5 b/usr/src/man/man5/term.5 index d1edc8a688..28417aadc7 100644 --- a/usr/src/man/man5/term.5 +++ b/usr/src/man/man5/term.5 @@ -15,8 +15,8 @@ term \- format of compiled term file .SH DESCRIPTION .sp .LP -The \fBterm\fR file is compiled from \fBterminfo\fR(4) source files using -\fBtic\fR(1M). Compiled files are organized in a directory hierarchy under the +The \fBterm\fR file is compiled from \fBterminfo\fR(5) source files using +\fBtic\fR(8). Compiled files are organized in a directory hierarchy under the first letter of each terminal name. For example, the \fBvt100\fR file would have the pathname \fB/usr/lib/terminfo/v/vt100\fR. The default directory is \fB/usr/share/lib/terminfo\fR. Synonyms for the same terminal are implemented @@ -84,7 +84,7 @@ the size, in bytes, of the string table. .LP The terminal name section comes next. It contains the first line of the \fBterminfo\fR description, listing the various names for the terminal, -separated by the bar ( | ) character (see \fBterm\fR(5)). The section is +separated by the bar ( | ) character (see \fBterm\fR(7)). The section is terminated with an \fBASCII NUL\fR character. .sp .LP @@ -214,5 +214,5 @@ X/Open Curses \fBterminfo\fR header .SH SEE ALSO .sp .LP -\fBinfocmp\fR(1M), \fBcurses\fR(3CURSES), \fBcurses\fR(3XCURSES), -\fBterminfo\fR(4), \fBterm\fR(5) +\fBinfocmp\fR(8), \fBcurses\fR(3CURSES), \fBcurses\fR(3XCURSES), +\fBterminfo\fR(5), \fBterm\fR(7) diff --git a/usr/src/man/man5/terminfo.5 b/usr/src/man/man5/terminfo.5 index 36c2b7accf..6a970d508f 100644 --- a/usr/src/man/man5/terminfo.5 +++ b/usr/src/man/man5/terminfo.5 @@ -25,7 +25,7 @@ devices without changes to the programs. .LP \fBterminfo\fR descriptions are located in the directory pointed to by the environment variable \fBTERMINFO\fR or in \fB/usr/share/lib/terminfo\fR. -\fBterminfo\fR descriptions are generated by \fBtic\fR(1M). +\fBterminfo\fR descriptions are generated by \fBtic\fR(8). .sp .LP \fBterminfo\fR source files consist of one or more device descriptions. Each @@ -58,7 +58,7 @@ The first line, commonly referred to as the header line, must begin in column one and must contain at least two aliases separated by vertical bars. The last field in the header line must be the long name of the device and it may contain any string. Alias names must be unique in the \fBterminfo\fR database -and they must conform to system file naming conventions. See \fBtic\fR(1M). +and they must conform to system file naming conventions. See \fBtic\fR(8). They cannot, for example, contain white space or slashes. .sp .LP @@ -2905,7 +2905,7 @@ terminal (escape sequences that set margins and tabs) .SH SEE ALSO \fBls\fR(1), \fBpg\fR(1), \fBstty\fR(1), \fBtput\fR(1), \fBtty\fR(1), -\fBvi\fR(1), \fBinfocmp\fR(1M), \fBtic\fR(1M), \fBprintf\fR(3C), +\fBvi\fR(1), \fBinfocmp\fR(8), \fBtic\fR(8), \fBprintf\fR(3C), \fBcurses\fR(3CURSES), \fBcurses\fR(3XCURSES) .SH NOTES The most effective way to prepare a terminal description is by imitating the diff --git a/usr/src/man/man5/timezone.5 b/usr/src/man/man5/timezone.5 index 131341a35a..f05c9f69c0 100644 --- a/usr/src/man/man5/timezone.5 +++ b/usr/src/man/man5/timezone.5 @@ -36,7 +36,7 @@ was used by the installer in older releases of Solaris. .sp .LP The \fBtimezone\fR file does not set the timezone environment variable -\fBTZ\fR. See \fBTIMEZONE\fR(4) for information to set the \fBTZ\fR environment +\fBTZ\fR. See \fBTIMEZONE\fR(5) for information to set the \fBTZ\fR environment variable. .SH EXAMPLES \fBExample 1 \fRTypical timezone line @@ -62,4 +62,4 @@ US/Eastern East.Example.COM #Host on East Coast .RE .SH SEE ALSO -\fBTIMEZONE\fR(4) +\fBTIMEZONE\fR(5) diff --git a/usr/src/man/man5/ts_dptbl.5 b/usr/src/man/man5/ts_dptbl.5 index 9010d519b1..451a7b6551 100644 --- a/usr/src/man/man5/ts_dptbl.5 +++ b/usr/src/man/man5/ts_dptbl.5 @@ -51,7 +51,7 @@ The global scheduling priority associated with this priority level. The mapping between time-sharing priority levels and global scheduling priorities is determined at boot time by the system configuration. \fBts_globpri\fR is the only member of the \fBts_dptbl\fR which cannot be changed with -\fBdispadmin\fR(1M). +\fBdispadmin\fR(8). .RE .sp @@ -126,7 +126,7 @@ scheduler by reconfiguring the \fBts_dptbl\fR. Since processes in the time-sharing and inter-active scheduling classes share the same dispatch parameter table (\fBts_dptbl\fR), changes to this table will affect both scheduling classes. There are two methods available for doing this: reconfigure -with a loadable module at boot-time or by using \fBdispadmin\fR(1M) at +with a loadable module at boot-time or by using \fBdispadmin\fR(8) at run-time. .SS "ts_dptbl Loadable Module" The \fBts_dptbl\fR can be reconfigured with a loadable module which contains a @@ -139,7 +139,7 @@ relevant procedure and source code is described in the \fBREPLACING THE TS_DPTBL LOADABLE MODULE\fR section. .SS "dispadmin Configuration File" With the exception of \fBts_globpri\fR all of the members of the \fBts_dptbl\fR -can be examined and modified on a running system using the \fBdispadmin\fR(1M) +can be examined and modified on a running system using the \fBdispadmin\fR(8) command. Invoking \fBdispadmin\fR for the time-sharing or inter-active class allows the administrator to retrieve the current \fBts_dptbl\fR configuration from the kernel's in-core table, or overwrite the in-core table with values @@ -259,7 +259,7 @@ Replace the current \fBTS_DPTBL\fR in \fB/kernel/sched\fR. .TP 5. You will have to make changes in the \fB/etc/system\fR file to reflect the -changes to the sizes of the tables. See \fBsystem\fR(4). The two variables +changes to the sizes of the tables. See \fBsystem\fR(5). The two variables affected are \fBts_maxupri\fR and \fBts_maxkmdpri\fR. The syntax for setting these is as follows: .sp @@ -430,7 +430,7 @@ ts_getmaxumdpri() .in -2 .SH SEE ALSO -\fBpriocntl\fR(1), \fBdispadmin\fR(1M), \fBpriocntl\fR(2), \fBsystem\fR(4) +\fBpriocntl\fR(1), \fBdispadmin\fR(8), \fBpriocntl\fR(2), \fBsystem\fR(5) .sp .LP \fISystem Administration Guide: Basic Administration\fR diff --git a/usr/src/man/man5/ttydefs.5 b/usr/src/man/man5/ttydefs.5 index 3c1bee65c7..fcbeb65d43 100644 --- a/usr/src/man/man5/ttydefs.5 +++ b/usr/src/man/man5/ttydefs.5 @@ -32,7 +32,7 @@ which the terminal is supposed to run, for example, \fB1200\fR. \fB\fIinitial-flags\fR\fR .ad .RS 17n -Contains the initial \fBtermio\fR(7I) settings to which the terminal is to be +Contains the initial \fBtermio\fR(4I) settings to which the terminal is to be set. For example, the system administrator will be able to specify what the default erase and kill characters will be. \fIinitial-flags\fR must be specified in the syntax recognized by the \fBstty\fR command. @@ -79,7 +79,7 @@ example, \fB4800\fR may be linked to \fB1200\fR, which in turn is linked to .SH SEE ALSO .sp .LP -\fBsttydefs\fR(1M), \fBttymon\fR(1M), \fBtermio\fR(7I) +\fBsttydefs\fR(8), \fBttymon\fR(8), \fBtermio\fR(4I) .sp .LP \fISystem Administration Guide: Basic Administration\fR diff --git a/usr/src/man/man5/ufsdump.5 b/usr/src/man/man5/ufsdump.5 index a073636379..6fe47d5859 100644 --- a/usr/src/man/man5/ufsdump.5 +++ b/usr/src/man/man5/ufsdump.5 @@ -14,7 +14,7 @@ ufsdump, dumpdates \- incremental dump format .fi .SH DESCRIPTION -Tapes used by \fBufsdump\fR(1M) and \fBufsrestore\fR(1M) contain: +Tapes used by \fBufsdump\fR(8) and \fBufsrestore\fR(8) contain: .RS +4 .TP .ie t \(bu @@ -708,7 +708,7 @@ The name of the device on which the dumped file system resides. .TP .ie t \(bu .el o -The level number of the dump tape; see \fBufsdump\fR(1M). +The level number of the dump tape; see \fBufsdump\fR(8). .RE .RS +4 .TP @@ -722,7 +722,7 @@ The date of the incremental dump in the format generated by \fBctime\fR(3C). entry to \fB/etc/dumpdates\fR; \fBDUMPINFMT\fR is the format to use when using \fBscanf\fR(3C) to read an entry from \fB/etc/dumpdates\fR. .SH ATTRIBUTES -See \fBattributes\fR(5) for a description of the following attributes: +See \fBattributes\fR(7) for a description of the following attributes: .sp .sp @@ -736,5 +736,5 @@ Stability Level Unstable .TE .SH SEE ALSO -\fBufsdump\fR(1M), \fBufsrestore\fR(1M), \fBctime\fR(3C), \fBprintf\fR(3C), -\fBscanf\fR(3C), \fBtypes.h\fR(3HEAD), \fBattributes\fR(5), +\fBufsdump\fR(8), \fBufsrestore\fR(8), \fBctime\fR(3C), \fBprintf\fR(3C), +\fBscanf\fR(3C), \fBtypes.h\fR(3HEAD), \fBattributes\fR(7), diff --git a/usr/src/man/man5/updaters.5 b/usr/src/man/man5/updaters.5 index a7f8021648..a82b9c0426 100644 --- a/usr/src/man/man5/updaters.5 +++ b/usr/src/man/man5/updaters.5 @@ -18,7 +18,7 @@ updaters \- configuration file for NIS updating The file \fB/var/yp/updaters\fR is a makefile (see \fBmake\fR(1S)) which is used for updating the Network Information Service (NIS) databases. Databases can only be updated in a secure network, that is, one that has a -\fBpublickey\fR(4) database. Each entry in the file is a make target for a +\fBpublickey\fR(5) database. Each entry in the file is a make target for a particular \fBNIS\fR database. For example, if there is an \fBNIS\fR database named \fBpasswd.byname\fR that can be updated, there should be a \fBmake\fR target named \fBpasswd.byname\fR in the \fBupdaters\fR file with the command to @@ -104,7 +104,7 @@ The makefile used for updating the \fBNIS\fR databases. .SH SEE ALSO .sp .LP -\fBmake\fR(1S), \fBrpc.ypupdated\fR(1M), \fBpublickey\fR(4) +\fBmake\fR(1S), \fBrpc.ypupdated\fR(8), \fBpublickey\fR(5) .SH NOTES .sp .LP diff --git a/usr/src/man/man5/user_attr.5 b/usr/src/man/man5/user_attr.5 index 2c3c5f4f00..c90fe24fd1 100644 --- a/usr/src/man/man5/user_attr.5 +++ b/usr/src/man/man5/user_attr.5 @@ -21,8 +21,8 @@ routines to gain access to this information. .sp .LP The search order for multiple \fBuser_attr\fR sources is specified in the -\fB/etc/nsswitch.conf\fR file, as described in the \fBnsswitch.conf\fR(4) man -page. The search order follows that for \fBpasswd\fR(4). +\fB/etc/nsswitch.conf\fR file, as described in the \fBnsswitch.conf\fR(5) man +page. The search order follows that for \fBpasswd\fR(5). .sp .LP Each entry in the \fBuser_attr\fR databases consists of a single line with five @@ -42,7 +42,7 @@ fields separated by colons (\fB:\fR). Line continuations using the backslash .ad .sp .6 .RS 4n -The name of the user as specified in the \fBpasswd\fR(4) database. +The name of the user as specified in the \fBpasswd\fR(5) database. .RE .sp @@ -94,7 +94,7 @@ system: .sp .6 .RS 4n Specifies a comma-separated list of authorization names chosen from those names -defined in the \fBauth_attr\fR(4) database. Authorization names may be +defined in the \fBauth_attr\fR(5) database. Authorization names may be specified using the asterisk (\fB*\fR) character as a wildcard. For example, \fBsolaris.printer.*\fR means all of Sun's printer authorizations. .RE @@ -107,9 +107,9 @@ specified using the asterisk (\fB*\fR) character as a wildcard. For example, .sp .6 .RS 4n Contains an ordered, comma-separated list of profile names chosen from -\fBprof_attr\fR(4). Profiles are enforced by the profile shells, \fBpfcsh\fR, +\fBprof_attr\fR(5). Profiles are enforced by the profile shells, \fBpfcsh\fR, \fBpfksh\fR, and \fBpfsh\fR. See \fBpfsh\fR(1). A default profile is assigned -in \fB/etc/security/policy.conf\fR (see \fBpolicy.conf\fR(4)). If no profiles +in \fB/etc/security/policy.conf\fR (see \fBpolicy.conf\fR(5)). If no profiles are assigned, the profile shells do not allow the user to execute any commands. .RE @@ -159,7 +159,7 @@ the user has logged in. .ad .sp .6 .RS 4n -Can be assigned a name of one project from the \fBproject\fR(4) database to be +Can be assigned a name of one project from the \fBproject\fR(5) database to be used as a default project to place the user in at login time. For more information, see \fBgetdefaultproj\fR(3PROJECT). .RE @@ -183,7 +183,7 @@ See "Privileges Keywords," below. .sp .6 .RS 4n The maximum set of privileges a user or any process started by the user, -whether through \fBsu\fR(1M) or any other means, can obtain. The system +whether through \fBsu\fR(8) or any other means, can obtain. The system administrator must take extreme care when removing privileges from the limit set. Removing any basic privilege has the ability of crippling all applications; removing any other privilege can cause many or all applications @@ -215,8 +215,8 @@ Trusted Extensions feature: .RS 4n Contains the maximum label at which the user can operate. If unspecified, in the Defense Intelligence Agency (\fBDIA\fR) encodings scheme, the default is -specified in \fBlabel_encodings\fR(4) (see \fBlabel_encodings\fR(4) and -\fBlabels\fR(5) in the \fISolaris Trusted Extensions Reference Manual\fR). +specified in \fBlabel_encodings\fR(5) (see \fBlabel_encodings\fR(5) and +\fBlabels\fR(7) in the \fISolaris Trusted Extensions Reference Manual\fR). .RE .sp @@ -228,7 +228,7 @@ specified in \fBlabel_encodings\fR(4) (see \fBlabel_encodings\fR(4) and .RS 4n Contains the minimum label at which the user can log in. If unspecified, in the \fBDIA\fR encodings scheme, the default is specified in -\fBlabel_encodings\fR(4) (see \fBlabel_encodings\fR(4) and \fBlabels\fR(5) in +\fBlabel_encodings\fR(5) (see \fBlabel_encodings\fR(5) and \fBlabels\fR(7) in the \fISolaris Trusted Extensions Reference Manual\fR). .RE @@ -237,8 +237,8 @@ the \fISolaris Trusted Extensions Reference Manual\fR). .sp .LP Except for the \fBtype\fR key, the \fB\fIkey\fR=\fIvalue\fR\fR fields in -\fB/etc/user_attr\fR can be added using \fBroleadd\fR(1M) and -\fBuseradd\fR(1M). You can use \fBrolemod\fR(1M) and \fBusermod\fR(1M) to +\fB/etc/user_attr\fR can be added using \fBroleadd\fR(8) and +\fBuseradd\fR(8). You can use \fBrolemod\fR(8) and \fBusermod\fR(8) to modify \fB\fIkey\fR=\fIvalue\fR\fR fields in \fB/etc/user_attr\fR. Modification of the \fBtype\fR key is restricted as described in \fBrolemod\fR and \fBusermod\fR. @@ -247,16 +247,16 @@ The \fBdefaultpriv\fR and \fBlimitpriv\fR are the privileges-related keywords and are described above. .sp .LP -See \fBprivileges\fR(5) for a description of privileges. The command +See \fBprivileges\fR(7) for a description of privileges. The command \fBppriv\fR \fB-l\fR (see \fBppriv\fR(1)) produces a list of all supported privileges. Note that you specify privileges as they are displayed by -\fBppriv\fR. In \fBprivileges\fR(5), privileges are listed in the form +\fBppriv\fR. In \fBprivileges\fR(7), privileges are listed in the form \fBPRIV_\fR\fI<privilege_name>\fR\&. For example, the privilege \fBfile_chown\fR, as you would specify it in \fBuser_attr\fR, is listed in -\fBprivileges\fR(5) as \fBPRIV_FILE_CHOWN\fR. +\fBprivileges\fR(7) as \fBPRIV_FILE_CHOWN\fR. .sp .LP -See \fBusermod\fR(1M) for examples of commands that +See \fBusermod\fR(8) for examples of commands that modify privileges and their subsequent effect on \fBuser_attr\fR. .SH EXAMPLES \fBExample 1 \fRAssigning a Profile to Root @@ -278,7 +278,7 @@ The \fBsolaris.*\fR wildcard authorization shown above gives root all the \fBsolaris\fR authorizations; and the \fBsolaris.grant\fR authorization gives root the right to grant to others any \fBsolaris\fR authorizations that root has. The combination of authorizations enables root to grant to others all the -\fBsolaris\fR authorizations. See \fBauth_attr\fR(4) for more about +\fBsolaris\fR authorizations. See \fBauth_attr\fR(5) for more about authorizations. .SH FILES @@ -288,7 +288,7 @@ authorizations. .ad .sp .6 .RS 4n -See \fBnsswitch.conf\fR(4). +See \fBnsswitch.conf\fR(5). .RE .sp @@ -302,7 +302,7 @@ Described here. .RE .SH ATTRIBUTES -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -322,11 +322,11 @@ Interface Stability See below The command-line syntax is Committed. The output is Uncommitted. .SH SEE ALSO \fBauths\fR(1), \fBpfcsh\fR(1), \fBpfksh\fR(1), \fBpfsh\fR(1), \fBppriv\fR(1), -\fBprofiles\fR(1), \fBroles\fR(1), \fBroleadd\fR(1M), \fBrolemod\fR(1M), -\fBuseradd\fR(1M), \fBusermod\fR(1M), \fBgetdefaultproj\fR(3PROJECT), -\fBgetuserattr\fR(3SECDB), \fBauth_attr\fR(4), \fBexec_attr\fR(4), -\fBnsswitch.conf\fR(4), \fBpasswd\fR(4), \fBpolicy.conf\fR(4), -\fBprof_attr\fR(4), \fBproject\fR(4), \fBattributes\fR(5), \fBprivileges\fR(5) +\fBprofiles\fR(1), \fBroles\fR(1), \fBroleadd\fR(8), \fBrolemod\fR(8), +\fBuseradd\fR(8), \fBusermod\fR(8), \fBgetdefaultproj\fR(3PROJECT), +\fBgetuserattr\fR(3SECDB), \fBauth_attr\fR(5), \fBexec_attr\fR(5), +\fBnsswitch.conf\fR(5), \fBpasswd\fR(5), \fBpolicy.conf\fR(5), +\fBprof_attr\fR(5), \fBproject\fR(5), \fBattributes\fR(7), \fBprivileges\fR(7) .sp .LP \fISystem Administration Guide: Security Services\fR @@ -336,7 +336,7 @@ including the fact that root needs to be able to log in and do system maintenance in single-user mode, before the network name service databases are available. For this reason, an entry should exist for root in the local \fBuser_attr\fR file, and the precedence shown in the example -\fBnsswitch.conf\fR(4) file entry under EXAMPLES is highly recommended. +\fBnsswitch.conf\fR(5) file entry under EXAMPLES is highly recommended. .sp .LP Because the list of legal keys is likely to expand, any code that parses this diff --git a/usr/src/man/man5/utmp.5 b/usr/src/man/man5/utmp.5 index d1947e3a69..2c34bce7d5 100644 --- a/usr/src/man/man5/utmp.5 +++ b/usr/src/man/man5/utmp.5 @@ -20,7 +20,7 @@ utmp, wtmp \- utmp and wtmp database entry formats The \fButmp\fR and \fBwtmp\fR database files are obsolete and are no longer present on the system. They have been superseded by the extended database contained in the \fButmpx\fR and \fBwtmpx\fR database files. See -\fButmpx\fR(4). +\fButmpx\fR(5). .sp .LP It is possible for \fB/var/adm/utmp\fR to reappear on the system. This would @@ -31,4 +31,4 @@ application is recreating this file. .SH SEE ALSO .sp .LP -\fButmpx\fR(4) +\fButmpx\fR(5) diff --git a/usr/src/man/man5/warn.conf.5 b/usr/src/man/man5/warn.conf.5 index 5b4ad6f0a3..27d65616ee 100644 --- a/usr/src/man/man5/warn.conf.5 +++ b/usr/src/man/man5/warn.conf.5 @@ -212,7 +212,7 @@ Kerberos warning daemon .RE .SH ATTRIBUTES -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -226,8 +226,8 @@ Interface Stability Evolving .TE .SH SEE ALSO -\fBkinit\fR(1), \fBkdestroy\fR(1), \fBktkt_warnd\fR(1M), \fBsyslog.conf\fR(4), -\fButmpx\fR(4), \fBattributes\fR(5), \fBkerberos\fR(5), \fBpam_krb5\fR(5) +\fBkinit\fR(1), \fBkdestroy\fR(1), \fBktkt_warnd\fR(8), \fBsyslog.conf\fR(5), +\fButmpx\fR(5), \fBattributes\fR(7), \fBkerberos\fR(7), \fBpam_krb5\fR(7) .SH NOTES The auto-renew of the TGT is attempted only if the user is logged-in, as -determined by examining \fButmpx\fR(4). +determined by examining \fButmpx\fR(5). diff --git a/usr/src/man/man5/ypfiles.5 b/usr/src/man/man5/ypfiles.5 index 9743bb8544..980652680a 100644 --- a/usr/src/man/man5/ypfiles.5 +++ b/usr/src/man/man5/ypfiles.5 @@ -40,7 +40,7 @@ N2L mode enables NIS clients to be supported in an LDAP environment. .sp .LP In N2L mode, the old style DBM files, NIS source files, and the -\fBypmake\fR(1M) utility have to role. They are retained to enable easy +\fBypmake\fR(8) utility have to role. They are retained to enable easy conversion back to the traditional mode, if required. .SS "Converting from N2L to Traditional NIS" .LP @@ -54,7 +54,7 @@ files, \fB/var/yp/*/LDAP_*\fR can also be deleted. .LP If you want to run the system in traditional mode with information based on the DIT, then the NIS source files must be regenerated based on the N2L maps. To -regenerate the NIS source files based on the N2L maps, run \fBypmap2src\fR(1M). +regenerate the NIS source files based on the N2L maps, run \fBypmap2src\fR(8). .SH FILES .ne 2 .na @@ -149,6 +149,6 @@ NIS to LDAP mode map files .SH SEE ALSO .LP -\fBldap\fR(1), \fBmakedbm\fR(1M), \fBypbind\fR(1M), \fBypinit\fR(1M), -\fBypmake\fR(1M), \fBypmap2src\fR(1M), \fBypserv\fR(1M), \fBypxfrd\fR(1M), +\fBldap\fR(1), \fBmakedbm\fR(8), \fBypbind\fR(8), \fBypinit\fR(8), +\fBypmake\fR(8), \fBypmap2src\fR(8), \fBypserv\fR(8), \fBypxfrd\fR(8), \fBndbm\fR(3C), \fBypclnt\fR(3NSL) diff --git a/usr/src/man/man5/yppasswdd.5 b/usr/src/man/man5/yppasswdd.5 index 5bf267d42b..d8fe57b730 100644 --- a/usr/src/man/man5/yppasswdd.5 +++ b/usr/src/man/man5/yppasswdd.5 @@ -16,7 +16,7 @@ yppasswdd \- configuration file for rpc.yppasswdd (NIS password daemon) .sp .LP The \fByppasswdd\fR file contains a parameter that modifies the behavior of the -\fBrpc.yppasswdd\fR(1M) daemon. +\fBrpc.yppasswdd\fR(8) daemon. .sp .LP The \fByppasswdd\fR file contains a single parameter: @@ -58,4 +58,4 @@ configuration file for \fBrpc.yppasswdd\fR daemon .SH SEE ALSO .sp .LP -\fBrpc.yppasswdd\fR(1M) +\fBrpc.yppasswdd\fR(8) diff --git a/usr/src/man/man5/ypserv.5 b/usr/src/man/man5/ypserv.5 index b4ca1d084e..aeee9b3e44 100644 --- a/usr/src/man/man5/ypserv.5 +++ b/usr/src/man/man5/ypserv.5 @@ -16,20 +16,20 @@ ypserv \- configuration file for NIS to LDAP transition daemons .SH DESCRIPTION .LP The \fBypserv\fR file specifies configuration information for the -\fBypserv\fR(1M) daemon. Configuration information can come from LDAP or be +\fBypserv\fR(8) daemon. Configuration information can come from LDAP or be specified in the \fBypserv\fR file. .sp .LP -You can create a simple \fBypserv\fR file by running \fBinityp2l\fR(1M). The +You can create a simple \fBypserv\fR file by running \fBinityp2l\fR(8). The \fBypserv\fR file can then be customized as required. .sp .LP A related \fBNISLDAPmapping\fR file contains mapping information that converts -NIS entries into LDAP entries. See the \fBNISLDAPmapping\fR(4) man page for an +NIS entries into LDAP entries. See the \fBNISLDAPmapping\fR(5) man page for an overview of the setup that is needed to map NIS data to or from LDAP. .SH EXTENDED DESCRIPTION .LP -The \fBypserv\fR(1M) server recognizes the attributes that follow. Values +The \fBypserv\fR(8) server recognizes the attributes that follow. Values specified for these attributes in the \fBypserv\fR file, including any empty values, override values that are obtained from LDAP. However, the \fBnisLDAPconfig*\fR values are read from the \fBypserv\fR file only @@ -273,11 +273,11 @@ recognized and default values for \fBnisLDAPTLSCertificateDBPath\fR, see the .ad .sp .6 .RS 4n -Proxy user used by \fBypserv\fR(1M), \fBypxfrd\fR(1M) and \fByppasswdd\fR(1M) +Proxy user used by \fBypserv\fR(8), \fBypxfrd\fR(8) and \fByppasswdd\fR(8) to read or to write from or to LDAP. Assumed to have the appropriate permission to read and modify LDAP data. There is no default value. If the value ends in a comma, the value of the context for the current domain, as defined by a -\fBnisLDAPdomainContext\fR attribute, is appended. See \fBNISLDAPmapping\fR(4). +\fBnisLDAPdomainContext\fR attribute, is appended. See \fBNISLDAPmapping\fR(5). For example: .sp .in +2 @@ -507,7 +507,7 @@ default value for \fBnisLDAPstoreErrortimeout\fR is 15 seconds. The .SS "Storing Configuration Attributes in LDAP" .LP Most attributes described on this man page, as well as those described on -\fBNISLDAPmapping\fR(4), can be stored in LDAP. In order to do so, you will +\fBNISLDAPmapping\fR(5), can be stored in LDAP. In order to do so, you will need to add the following definitions to your LDAP server, which are described here in \fBLDIF\fR format suitable for use by \fBldapadd\fR(1). The attribute and objectclass OIDs are examples only. @@ -690,7 +690,7 @@ preferredServerList: 127.0.0.1:389 .SH ATTRIBUTES .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -705,9 +705,9 @@ Interface Stability Obsolete .SH SEE ALSO .LP -\fBldapadd\fR(1), \fBldapmodify\fR(1), \fBinityp2l\fR(1M), \fByppasswdd\fR(1M), -\fBypserv\fR(1M), \fBypxfrd\fR(1M), \fBNISLDAPmapping\fR(4), -\fBattributes\fR(5) +\fBldapadd\fR(1), \fBldapmodify\fR(1), \fBinityp2l\fR(8), \fByppasswdd\fR(8), +\fBypserv\fR(8), \fBypxfrd\fR(8), \fBNISLDAPmapping\fR(5), +\fBattributes\fR(7) .sp .LP \fISystem Administration Guide: Naming and Directory Services (DNS, NIS, and |