diff options
Diffstat (limited to 'usr/src/man/man7')
86 files changed, 590 insertions, 590 deletions
diff --git a/usr/src/man/man7/ad.7 b/usr/src/man/man7/ad.7 index 8361956f84..25accd4009 100644 --- a/usr/src/man/man7/ad.7 +++ b/usr/src/man/man7/ad.7 @@ -12,13 +12,13 @@ servers. .sp .LP The Solaris system must first join an AD domain and then add the \fBad\fR -keyword to the appropriate entries in the \fBnsswitch.conf\fR(4) file. The -Solaris system joins the AD domain by using the \fBkclient\fR(1M) utility. The +keyword to the appropriate entries in the \fBnsswitch.conf\fR(5) file. The +Solaris system joins the AD domain by using the \fBkclient\fR(8) utility. The AD name service only supports the naming databases for \fBpasswd\fR and \fBgroup\fR. .sp .LP -Windows users are not able to log in. The \fBuser_attr\fR(4) database has no +Windows users are not able to log in. The \fBuser_attr\fR(5) database has no entries for Windows users, and the \fBpasswd\fR(1) command does not support the synchronization of user passwords with AD. .sp @@ -27,7 +27,7 @@ The Solaris AD client uses auto-discovery techniques to find AD directory servers, such as domain controllers and global catalog servers. The client also uses the LDAP v3 protocol to access naming information from AD servers. The AD server schema requires no modification because the AD client works with native -AD schema. The Solaris AD client uses the \fBidmap\fR(1M) service to map +AD schema. The Solaris AD client uses the \fBidmap\fR(8) service to map between Windows security identifiers (SIDs) and Solaris user identifiers (UIDs) and group identifiers (GIDs). User names and group names are taken from the \fBsAMAccountName\fR attribute of the AD user and group objects and then tagged @@ -37,7 +37,7 @@ user name or group name by the \fB@\fR character. .LP The client uses the SASL/GSSAPI/KRB5 security model. The \fBkclient\fR utility is used to join the client to AD. During the join operation, \fBkclient\fR -configures Kerberos v5 on the client. See \fBkclient\fR(1M). +configures Kerberos v5 on the client. See \fBkclient\fR(8). .SH FILES .ne 2 .na @@ -67,6 +67,6 @@ Name service switch module for AD. .RE .SH SEE ALSO -\fBpasswd\fR(1), \fBsvcs\fR(1), \fBidmap\fR(1M), \fBidmapd\fR(1M), -\fBkclient\fR(1M), \fBsvcadm\fR(1M), \fBsvccfg\fR(1M), -\fBnsswitch.conf\fR(4), \fBuser_attr\fR(4), \fBsmf\fR(5) +\fBpasswd\fR(1), \fBsvcs\fR(1), \fBidmap\fR(8), \fBidmapd\fR(8), +\fBkclient\fR(8), \fBsvcadm\fR(8), \fBsvccfg\fR(8), +\fBnsswitch.conf\fR(5), \fBuser_attr\fR(5), \fBsmf\fR(7) diff --git a/usr/src/man/man7/attributes.7 b/usr/src/man/man7/attributes.7 index 176a63831f..f31bbf070e 100644 --- a/usr/src/man/man7/attributes.7 +++ b/usr/src/man/man7/attributes.7 @@ -28,7 +28,7 @@ Interface Stability Committed _ MT-Level Safe _ -Standard See \fBstandards\fR(5). +Standard See \fBstandards\fR(7). .TE .SS "Architecture" @@ -650,7 +650,7 @@ other race-condition reasons, the use of \fBforkall()\fR is discouraged. .sp In all Solaris releases prior to Solaris 10, the behavior of \fBfork()\fR depended on whether or not the application was linked with \fB-lpthread\fR -(POSIX threads, see \fBstandards\fR(5)). If linked with \fB-lpthread\fR, +(POSIX threads, see \fBstandards\fR(7)). If linked with \fB-lpthread\fR, \fBfork()\fR behaved like \fBfork1()\fR; otherwise it behaved like \fBforkall()\fR. To avoid any confusion concerning the behavior of \fBfork()\fR, applications can specifically call \fBfork1()\fR or @@ -717,4 +717,4 @@ accepted organization such as IETF, or as informal as the sole contributor in the case of FOSS (Free or Open Source Software). .SH SEE ALSO .LP -\fBuname\fR(1), \fBIntro\fR(3), \fBstandards\fR(5) +\fBuname\fR(1), \fBIntro\fR(3), \fBstandards\fR(7) diff --git a/usr/src/man/man7/audit_binfile.7 b/usr/src/man/man7/audit_binfile.7 index 3b4b0a5641..8966c10156 100644 --- a/usr/src/man/man7/audit_binfile.7 +++ b/usr/src/man/man7/audit_binfile.7 @@ -17,9 +17,9 @@ audit_binfile \- generation of audit logs .LP The \fBaudit_binfile\fR plugin module for audit, \fB/usr/lib/security/audit_binfile.so\fR, writes binary audit data to files as -specified in the plugin's attributes configured by \fBauditconfig\fR(1M); it -is the default plugin for the audit daemon \fBauditd\fR(1M). Its output is -described by \fBaudit.log\fR(4). +specified in the plugin's attributes configured by \fBauditconfig\fR(8); it +is the default plugin for the audit daemon \fBauditd\fR(8). Its output is +described by \fBaudit.log\fR(5). .SH OBJECT ATTRIBUTES .LP The \fBp_dir\fR attribute specifies a comma-separated list of @@ -27,8 +27,8 @@ directories to be used for storing audit files. .sp .LP The \fBp_minfree\fR attribute specifies the percentage of free space required. -If free space falls below this threshold, the audit daemon \fBauditd\fR(1M) -invokes the shell script \fBaudit_warn\fR(1M). The default threshold is 0%. +If free space falls below this threshold, the audit daemon \fBauditd\fR(8) +invokes the shell script \fBaudit_warn\fR(8). The default threshold is 0%. .sp .LP The \fBp_fsize\fR attribute defines the maximum size in bytes that an audit @@ -41,7 +41,7 @@ be within the range of [512,000, 2,147,483,647]. .LP The following commands cause \fBaudit_binfile.so\fR to be activated, specify the directories for writing audit logs, and specify the percentage of required free -space per directory. Note that using \fBauditconfig\fR(1M) only allows one +space per directory. Note that using \fBauditconfig\fR(8) only allows one attribute to be set at a time. .sp .in +2 @@ -57,7 +57,7 @@ p_dir=/var/audit/jedgar/eggplant,\e .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 @@ -74,4 +74,4 @@ Interface Stability Committed .SH SEE ALSO .LP -\fBauditd\fR(1M), \fBauditconfig\fR(1M), \fBaudit.log\fR(4), \fBattributes\fR(5) +\fBauditd\fR(8), \fBauditconfig\fR(8), \fBaudit.log\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man7/audit_remote.7 b/usr/src/man/man7/audit_remote.7 index 9054f34f71..5a67bd5b7c 100644 --- a/usr/src/man/man7/audit_remote.7 +++ b/usr/src/man/man7/audit_remote.7 @@ -15,8 +15,8 @@ audit_remote \- send audit logs to a remote server .SH DESCRIPTION The \fBaudit_remote\fR plugin module for audit, \fB/usr/lib/security/audit_remote.so\fR, sends binary audit records -(\fBaudit.log\fR(4)) to audit servers specified in the plugin's attributes -configured by \fBauditconfig\fR(1M). +(\fBaudit.log\fR(5)) to audit servers specified in the plugin's attributes +configured by \fBauditconfig\fR(8). .SS "Object Attributes" The following attributes specify the configuration of the \fBaudit_remote\fR plugin: @@ -50,7 +50,7 @@ number is that assigned to the \fBsolaris-audit\fR service. See \fBgetservbyname\fR(3XNET). .sp The \fBmech\fR part of a \fBp_host\fR entry is the GSS-API mechanism name -(\fBmech\fR(4)). If not specified, the local host's default mechanism is used. +(\fBmech\fR(5)). If not specified, the local host's default mechanism is used. The recommended mechanism is \fBkerberos_v5\fR. .RE @@ -88,7 +88,7 @@ The default value is \fB5\fR seconds. The maximum number of outstanding audit records to keep. .sp The default is the value of the kernel queue control high water mark. See -\fBauditconfig\fR(1M). +\fBauditconfig\fR(8). .RE .SS "GSS SESSION" @@ -100,7 +100,7 @@ tokens generated by \fBgss_wrap\fR(3GSS). .LP The plugin initiates a TCP connection to an audit server (\fIhost:port:mech\fR) and establishes a GSS security context (with \fBgss_init_sec_context\fR(3GSS)), -with appropriate security mechanism (\fBmech\fR(4)). +with appropriate security mechanism (\fBmech\fR(5)). .sp .LP If no port is specified, the service name \fBsolaris-audit\fR is looked up to @@ -129,7 +129,7 @@ client side has to be eligible to non-interactively gain session keys for the \fBaudit/<host_fqdn>@<REALM>\fR principal from the Kerberos KDC/TGS. At the same time the identity running the audit server application has to have the long term keys associated with the \fBaudit/<host_fqdn>@<REALM>\fR principal -stored in the \fBkeytab\fR file (\fBkrb5.conf\fR(4)) to be able to decrypt the +stored in the \fBkeytab\fR file (\fBkrb5.conf\fR(5)) to be able to decrypt the session keys. .sp .LP @@ -138,7 +138,7 @@ The \fBaudit_remote\fR plugin initiates a connection to first server in the responded to in \fBp_timeout\fR seconds, after \fBp_retries\fR attempts the plugin tries to connect to the next server. If the connection to the last server fails, the plugin retries to connect to the first host in the list. -\fBaudit_warn\fR(1M) is executed at every unsuccessful attempt to connect to +\fBaudit_warn\fR(8) is executed at every unsuccessful attempt to connect to the server or send timeout with the plugin option plugin \fBaudit_remote.so retry <count> <error>.<error>\fR is connection \fB<host:port> <the network error>\fR\&. An \fBEPROTO\fR network error indicates that the client plugin did @@ -175,7 +175,7 @@ of the channel bindings of the GSS security context establishment. .sp .LP Subsequent tokens contain a 64 bit sequence number in network byte order and a -single audit record (\fBaudit.log\fR(4)); the client uses confidentiality +single audit record (\fBaudit.log\fR(5)); the client uses confidentiality protection. wrap (64 bit sequence number || audit record) .sp .LP @@ -258,7 +258,7 @@ Secure remote audit client/server communication flow: .LP The following commands cause \fBaudit_remote.so\fR to be activated and set the \fBp_retries\fR and \fBp_timeout\fR attributes. Note that using -\fBauditconfig\fR(1M) only allows one attribute to be set at a time. +\fBauditconfig\fR(8) only allows one attribute to be set at a time. .sp .in +2 @@ -305,7 +305,7 @@ jbadams.ebay.example.com:4592 .sp .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 @@ -323,16 +323,16 @@ Interface Stability See below. .sp .LP The plugin configuration parameters are Committed. The client/server protocol -(version \fB"01"\fR) is Contracted Project Private. See \fBaudit.log\fR(4) for +(version \fB"01"\fR) is Contracted Project Private. See \fBaudit.log\fR(5) for the audit record format and content stability. .SH SEE ALSO -\fBauditd\fR(1M), \fBauditconfig\fR(1M), \fBaudit_warn\fR(1M), +\fBauditd\fR(8), \fBauditconfig\fR(8), \fBaudit_warn\fR(8), \fBgetipnodebyname\fR(3SOCKET), \fBgetservbyname\fR(3XNET), \fBgss_accept_sec_context\fR(3GSS), \fBgss_get_mic\fR(3GSS), \fBgss_init_sec_context\fR(3GSS), \fBgss_wrap\fR(3GSS), \fBgss_unwrap\fR(3GSS), \fBlibgss\fR(3LIB), \fBlibsocket\fR(3LIB), -\fBaudit.log\fR(4), \fBkrb5.conf\fR(4), \fBmech\fR(4), \fBattributes\fR(5), -\fBkerberos\fR(5), \fBtcp\fR(7P) +\fBaudit.log\fR(5), \fBkrb5.conf\fR(5), \fBmech\fR(5), \fBattributes\fR(7), +\fBkerberos\fR(7), \fBtcp\fR(4P) .SH NOTES \fBaudit_remote\fR authenticates itself to the remote audit service by way of GSS-API (\fBlibgss\fR(3LIB)). Default gss credentials are used as provided by diff --git a/usr/src/man/man7/audit_syslog.7 b/usr/src/man/man7/audit_syslog.7 index a916c461e1..6d3dd21c66 100644 --- a/usr/src/man/man7/audit_syslog.7 +++ b/usr/src/man/man7/audit_syslog.7 @@ -18,17 +18,17 @@ audit_syslog \- realtime conversion of audit data to syslog messages The \fBaudit_syslog\fR plugin module for audit, \fB/usr/lib/security/audit_syslog.so\fR, provides realtime conversion of audit data to syslog-formatted (text) data and sends it to a syslog -daemon as configured in \fBsyslog.conf\fR(4). +daemon as configured in \fBsyslog.conf\fR(5). .sp .LP Messages to \fBsyslog\fR are written if the \fBaudit_syslog\fR plugin is -activated and configured using \fBauditconfig\fR(1M). +activated and configured using \fBauditconfig\fR(8). .sp .LP Syslog messages are generated with the facility code of -\fBLOG_AUDIT\fR (\fBaudit\fR in \fBsyslog.conf\fR(4)) and severity of +\fBLOG_AUDIT\fR (\fBaudit\fR in \fBsyslog.conf\fR(5)) and severity of \fBLOG_NOTICE\fR. Audit \fBsyslog\fR messages contain data selected from the -tokens described for the binary audit log. (See \fBaudit.log\fR(4)). As with +tokens described for the binary audit log. (See \fBaudit.log\fR(5)). As with all \fBsyslog\fR messages, each line in a \fBsyslog\fR file consists of two parts, a \fBsyslog\fR header and a message. .sp @@ -169,7 +169,7 @@ access(2) ok session 255 by janeuser as janeuser:staff from \e The \fBp_flags\fR attribute is used to further filter audit data being sent to the \fBsyslog\fR daemon beyond the default and non-attributable audit flags. The parameter is a comma-separated list; each -item represents an audit class (see \fBaudit_class\fR(4)) and is specified +item represents an audit class (see \fBaudit_class\fR(5)) and is specified using the same syntax used by \fBauditconfig\fR for the \fB-setflags\fR and \fB-setnaflags\fR options. The default (no \fBp_flags\fR set) is that no audit records are generated. @@ -210,7 +210,7 @@ Plugin: audit_syslog (active) .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 @@ -231,8 +231,8 @@ The message format and message content are Uncommitted. The configuration parameters are Committed. .SH SEE ALSO .LP -\fBauditd\fR(1M), \fBauditconfig\fR(1M), \fBaudit_class\fR(4), -\fBsyslog.conf\fR(4), \fBattributes\fR(5) +\fBauditd\fR(8), \fBauditconfig\fR(8), \fBaudit_class\fR(5), +\fBsyslog.conf\fR(5), \fBattributes\fR(7) .SH NOTES .LP Use of the \fBplugin\fR configuration line to include \fBaudit_syslog.so\fR diff --git a/usr/src/man/man7/brands.7 b/usr/src/man/man7/brands.7 index 4591d34d51..4b8c8ddaa5 100644 --- a/usr/src/man/man7/brands.7 +++ b/usr/src/man/man7/brands.7 @@ -8,7 +8,7 @@ brands \- alternate operating environments for non-global zones .SH DESCRIPTION The branded zone (BrandZ) framework extends the Solaris Zones infrastructure -described in \fBzones\fR(5) to include the creation of brands, which provide +described in \fBzones\fR(7) to include the creation of brands, which provide non-global zones that contain non-native operating environments. .sp .LP @@ -39,14 +39,14 @@ A brand is an attribute of a zone, set at zone create time. .TP .ie t \(bu .el o -The zonecfg tool (see \fBzonecfg\fR(1M)) is used to set a zone's brand type and +The zonecfg tool (see \fBzonecfg\fR(8)) is used to set a zone's brand type and configure the zone. .RE .RS +4 .TP .ie t \(bu .el o -The zoneadm tool (see \fBzoneadm\fR(1M)) is used to report a zone's brand type +The zoneadm tool (see \fBzoneadm\fR(8)) is used to report a zone's brand type and administer the zone. .RE .SS "Device Support" @@ -57,7 +57,7 @@ administrator chooses to add an unsupported device despite that warning, that device might or might not work as expected. The configuration will be untested and unsupported. .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 @@ -71,4 +71,4 @@ Interface Stability Evolving .TE .SH SEE ALSO -\fBzoneadm\fR(1M), \fBzonecfg\fR(1M), \fBattributes\fR(5), \fBzones\fR(5) +\fBzoneadm\fR(8), \fBzonecfg\fR(8), \fBattributes\fR(7), \fBzones\fR(7) diff --git a/usr/src/man/man7/cancellation.7 b/usr/src/man/man7/cancellation.7 index 334df1b3dd..519755224a 100644 --- a/usr/src/man/man7/cancellation.7 +++ b/usr/src/man/man7/cancellation.7 @@ -275,7 +275,7 @@ T} .SS "Cancel-Safe" .LP With the arrival of POSIX cancellation, the Cancel-Safe level has been added to -the list of MT-Safety levels. See \fBattributes\fR(5). An application or +the list of MT-Safety levels. See \fBattributes\fR(7). An application or library is Cancel-Safe whenever it has arranged for cleanup handlers to restore system or program state wherever cancellation can occur. The application or library is specifically Deferred-Cancel-Safe when it is Cancel-Safe for threads @@ -406,7 +406,7 @@ main() .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 @@ -422,8 +422,8 @@ MT-Level MT-Safe .SH SEE ALSO .LP \fBread\fR(2), \fBsigwait\fR(2), \fBwrite\fR(2), \fBIntro\fR(3), -\fBcondition\fR(5), \fBpthread_cleanup_pop\fR(3C), +\fBcondition\fR(7), \fBpthread_cleanup_pop\fR(3C), \fBpthread_cleanup_push\fR(3C), \fBpthread_exit\fR(3C), \fBpthread_join\fR(3C), \fBpthread_setcancelstate\fR(3C), \fBpthread_setcanceltype\fR(3C), -\fBpthread_testcancel\fR(3C), \fBsetjmp\fR(3C), \fBattributes\fR(5), -\fBstandards\fR(5) +\fBpthread_testcancel\fR(3C), \fBsetjmp\fR(3C), \fBattributes\fR(7), +\fBstandards\fR(7) diff --git a/usr/src/man/man7/charmap.7 b/usr/src/man/man7/charmap.7 index d5f41f68e0..b98d682596 100644 --- a/usr/src/man/man7/charmap.7 +++ b/usr/src/man/man7/charmap.7 @@ -356,4 +356,4 @@ appropriate. .sp .LP \fBlocale\fR(1), \fBlocaledef\fR(1), \fBnl_langinfo\fR(3C), -\fBextensions\fR(5), \fBlocale\fR(5) +\fBextensions\fR(7), \fBlocale\fR(7) diff --git a/usr/src/man/man7/condition.7 b/usr/src/man/man7/condition.7 index 0ac60cfd49..2ee043f9ef 100644 --- a/usr/src/man/man7/condition.7 +++ b/usr/src/man/man7/condition.7 @@ -107,7 +107,7 @@ all threads waiting on the condition variable. The condition destroy functions destroy any state, but not the space, associated with the condition variable. .SH ATTRIBUTES -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -127,8 +127,8 @@ MT-Level MT-Safe \fBpthread_cond_broadcast\fR(3C), \fBpthread_cond_destroy\fR(3C), \fBpthread_cond_init\fR(3C), \fBpthread_cond_signal\fR(3C), \fBpthread_cond_timedwait\fR(3C), \fBpthread_cond_wait\fR(3C), -\fBpthread_condattr_init\fR(3C), \fBsignal\fR(3C), \fBattributes\fR(5), -\fBmutex\fR(5), \fBstandards\fR(5) +\fBpthread_condattr_init\fR(3C), \fBsignal\fR(3C), \fBattributes\fR(7), +\fBmutex\fR(7), \fBstandards\fR(7) .SH NOTES If more than one thread is blocked on a condition variable, the order in which threads are unblocked is determined by the scheduling policy. diff --git a/usr/src/man/man7/crypt_bsdbf.7 b/usr/src/man/man7/crypt_bsdbf.7 index a525d0ad48..6f4cde9d08 100644 --- a/usr/src/man/man7/crypt_bsdbf.7 +++ b/usr/src/man/man7/crypt_bsdbf.7 @@ -17,14 +17,14 @@ crypt_bsdbf \- password hashing module using Blowfish cryptographic algorithm .LP The \fBcrypt_bsdbf\fR module is a one-way password hashing module for use with \fBcrypt\fR(3C) that uses the Blowfish cryptographic algorithm. The algorithm -identifier for \fBcrypt.conf\fR(4) and \fBpolicy.conf\fR(4) is \fB2a\fR. +identifier for \fBcrypt.conf\fR(5) and \fBpolicy.conf\fR(5) is \fB2a\fR. .sp .LP The maximum password length for \fBcrypt_bsdbf\fR is 72 characters. .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 @@ -42,4 +42,4 @@ MT-Level Safe .LP \fBpasswd\fR(1), \fBcrypt\fR(3C), \fBcrypt_genhash_impl\fR(3C), \fBcrypt_gensalt\fR(3C), \fBcrypt_gensalt_impl\fR(3C), \fBgetpassphrase\fR(3C), -\fBcrypt.conf\fR(4), \fBpasswd\fR(4), \fBpolicy.conf\fR(4), \fBattributes\fR(5) +\fBcrypt.conf\fR(5), \fBpasswd\fR(5), \fBpolicy.conf\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man7/crypt_bsdmd5.7 b/usr/src/man/man7/crypt_bsdmd5.7 index 3c2a0c0c27..0d6cf729de 100644 --- a/usr/src/man/man7/crypt_bsdmd5.7 +++ b/usr/src/man/man7/crypt_bsdmd5.7 @@ -17,7 +17,7 @@ crypt_bsdmd5 \- password hashing module using MD5 message hash algorithm .LP The \fBcrypt_bsdmd5\fR module is a one-way password hashing module for use with \fBcrypt\fR(3C) that uses the MD5 message hash algorithm. The algorithm -identifier for \fBcrypt.conf\fR(4) and \fBpolicy.conf\fR(4) is \fB1\fR. The +identifier for \fBcrypt.conf\fR(5) and \fBpolicy.conf\fR(5) is \fB1\fR. The output is compatible with \fBmd5crypt\fR on BSD and Linux systems. .sp .LP @@ -25,7 +25,7 @@ The maximum password length for \fBcrypt_bsdmd5\fR is 255 characters. .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 @@ -43,4 +43,4 @@ MT-Level Safe .LP \fBpasswd\fR(1), \fBcrypt\fR(3C), \fBcrypt_genhash_impl\fR(3C), \fBcrypt_gensalt\fR(3C), \fBcrypt_gensalt_impl\fR(3C), \fBgetpassphrase\fR(3C), -\fBcrypt.conf\fR(4), \fBpasswd\fR(4), \fBpolicy.conf\fR(4), \fBattributes\fR(5) +\fBcrypt.conf\fR(5), \fBpasswd\fR(5), \fBpolicy.conf\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man7/crypt_sha256.7 b/usr/src/man/man7/crypt_sha256.7 index 2984792569..584a846e9b 100644 --- a/usr/src/man/man7/crypt_sha256.7 +++ b/usr/src/man/man7/crypt_sha256.7 @@ -17,7 +17,7 @@ crypt_sha256 \- password hashing module using SHA-256 message hash algorithm .LP The \fBcrypt_sha256\fR module is a one-way password hashing module for use with \fBcrypt\fR(3C) that uses the SHA-256 message hash algorithm. The algorithm -identifier for \fBcrypt.conf\fR(4) and \fBpolicy.conf\fR(4) is \fB5\fR. +identifier for \fBcrypt.conf\fR(5) and \fBpolicy.conf\fR(5) is \fB5\fR. .sp .LP This module is designed to make it difficult to crack passwords that use brute @@ -29,7 +29,7 @@ The maximum password length for \fBcrypt_sha256\fR is 255 characters. .sp .LP The following options can be passed to the module by means of -\fBcrypt.conf\fR(4): +\fBcrypt.conf\fR(5): .sp .ne 2 .na @@ -51,8 +51,8 @@ $5,rounds=6000$nlxmTTpz$ .in -2 When \fBcrypt_gensalt\fR(3C) is being used to generate a new salt, if the -number of additional rounds configured in \fBcrypt.conf\fR(4) is greater than -that in the old salt, the value from \fBcrypt.conf\fR(4) is used instead. This +number of additional rounds configured in \fBcrypt.conf\fR(5) is greater than +that in the old salt, the value from \fBcrypt.conf\fR(5) is used instead. This allows for migration to stronger (but more time-consuming) salts on password change. .RE @@ -60,7 +60,7 @@ change. .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 @@ -80,4 +80,4 @@ MT-Level Safe .LP \fBpasswd\fR(1), \fBcrypt\fR(3C), \fBcrypt_genhash_impl\fR(3C), \fBcrypt_gensalt\fR(3C), \fBcrypt_gensalt_impl\fR(3C), \fBgetpassphrase\fR(3C), -\fBcrypt.conf\fR(4), \fBpasswd\fR(4), \fBpolicy.conf\fR(4), \fBattributes\fR(5) +\fBcrypt.conf\fR(5), \fBpasswd\fR(5), \fBpolicy.conf\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man7/crypt_sha512.7 b/usr/src/man/man7/crypt_sha512.7 index cea20fc797..2057a1c176 100644 --- a/usr/src/man/man7/crypt_sha512.7 +++ b/usr/src/man/man7/crypt_sha512.7 @@ -17,7 +17,7 @@ crypt_sha512 \- password hashing module using SHA-512 message hash algorithm .LP The \fBcrypt_sha512\fR module is a one-way password hashing module for use with \fBcrypt\fR(3C) that uses the SHA-512 message hash algorithm. The algorithm -identifier for \fBcrypt.conf\fR(4) and \fBpolicy.conf\fR(4) is \fB6\fR. +identifier for \fBcrypt.conf\fR(5) and \fBpolicy.conf\fR(5) is \fB6\fR. .sp .LP This module is designed to make it difficult to crack passwords that use brute @@ -29,7 +29,7 @@ The maximum password length for \fBcrypt_sha512\fR is 255 characters. .sp .LP The following options can be passed to the module by means of -\fBcrypt.conf\fR(4): +\fBcrypt.conf\fR(5): .sp .ne 2 .na @@ -51,8 +51,8 @@ $6,rounds=6000$nlxmTTpz$ .in -2 When \fBcrypt_gensalt\fR(3C) is being used to generate a new salt, if the -number of additional rounds configured in \fBcrypt.conf\fR(4) is greater than -that in the old salt, the value from \fBcrypt.conf\fR(4) is used instead. This +number of additional rounds configured in \fBcrypt.conf\fR(5) is greater than +that in the old salt, the value from \fBcrypt.conf\fR(5) is used instead. This allows for migration to stronger (but more time-consuming) salts on password change. .RE @@ -60,7 +60,7 @@ change. .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 @@ -80,4 +80,4 @@ MT-Level Safe .LP \fBpasswd\fR(1), \fBcrypt\fR(3C), \fBcrypt_genhash_impl\fR(3C), \fBcrypt_gensalt\fR(3C), \fBcrypt_gensalt_impl\fR(3C), \fBgetpassphrase\fR(3C), -\fBcrypt.conf\fR(4), \fBpasswd\fR(4), \fBpolicy.conf\fR(4), \fBattributes\fR(5) +\fBcrypt.conf\fR(5), \fBpasswd\fR(5), \fBpolicy.conf\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man7/crypt_sunmd5.7 b/usr/src/man/man7/crypt_sunmd5.7 index aa4ccd17ea..d139010218 100644 --- a/usr/src/man/man7/crypt_sunmd5.7 +++ b/usr/src/man/man7/crypt_sunmd5.7 @@ -17,7 +17,7 @@ crypt_sunmd5 \- password hashing module using MD5 message hash algorithm .LP The \fBcrypt_sunmd5\fR module is a one-way password hashing module for use with \fBcrypt\fR(3C) that uses the MD5 message hash algorithm. The algorithm -identifier for \fBcrypt.conf\fR(4) and \fBpolicy.conf\fR(4) is \fBmd5\fR. +identifier for \fBcrypt.conf\fR(5) and \fBpolicy.conf\fR(5) is \fBmd5\fR. .sp .LP This module is designed to make it difficult to crack passwords that use brute @@ -29,7 +29,7 @@ The maximum password length for \fBcrypt_sunmd5\fR is 255 characters. .sp .LP The following options can be passed to the module by means of -\fBcrypt.conf\fR(4): +\fBcrypt.conf\fR(5): .sp .ne 2 .na @@ -50,8 +50,8 @@ $md5,rounds=1000$nlxmTTpz$ .in -2 When \fBcrypt_gensalt\fR(3C) is being used to generate a new salt, if the -number of additional rounds configured in \fBcrypt.conf\fR(4) is greater than -that in the old salt, the value from \fBcrypt.conf\fR(4) is used instead. This +number of additional rounds configured in \fBcrypt.conf\fR(5) is greater than +that in the old salt, the value from \fBcrypt.conf\fR(5) is used instead. This allows for migration to stronger (but more time-consuming) salts on password change. .RE @@ -59,7 +59,7 @@ change. .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 @@ -77,4 +77,4 @@ MT-Level Safe .LP \fBpasswd\fR(1), \fBcrypt\fR(3C), \fBcrypt_genhash_impl\fR(3C), \fBcrypt_gensalt\fR(3C), \fBcrypt_gensalt_impl\fR(3C), \fBgetpassphrase\fR(3C), -\fBcrypt.conf\fR(4), \fBpasswd\fR(4), \fBpolicy.conf\fR(4), \fBattributes\fR(5) +\fBcrypt.conf\fR(5), \fBpasswd\fR(5), \fBpolicy.conf\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man7/crypt_unix.7 b/usr/src/man/man7/crypt_unix.7 index 04ba20c0ce..fd1df9fa85 100644 --- a/usr/src/man/man7/crypt_unix.7 +++ b/usr/src/man/man7/crypt_unix.7 @@ -11,12 +11,12 @@ crypt_unix \- traditional UNIX crypt algorithm .LP The \fBcrypt_unix\fR algorithm is the traditional UNIX crypt algorithm. It is not considered sufficiently secure for current systems and is provided for -backwards compatibility. The \fBcrypt_sunmd5\fR(5), \fBcrypt_bsdmd5\fR(5), or -\fBcrypt_bsdbf\fR(5) algorithm should be used instead. +backwards compatibility. The \fBcrypt_sunmd5\fR(7), \fBcrypt_bsdmd5\fR(7), or +\fBcrypt_bsdbf\fR(7) algorithm should be used instead. .sp .LP -The algorithm identifier for \fBpolicy.conf\fR(4) is \fB__unix__\fR. There is -no entry in \fBcrypt.conf\fR(4) for this algorithm. +The algorithm identifier for \fBpolicy.conf\fR(5) is \fB__unix__\fR. There is +no entry in \fBcrypt.conf\fR(5) for this algorithm. .sp .LP The \fBcrypt_unix\fR algorithm is internal to \fBlibc\fR and provides the @@ -37,11 +37,11 @@ The maximum password length for \fBcrypt_unix\fR is 8 characters. .sp .LP The return value of the \fBcrypt_unix\fR algorithm might not be portable among -standard-conforming systems. See \fBstandards\fR(5). +standard-conforming systems. See \fBstandards\fR(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 @@ -59,6 +59,6 @@ MT-Level Safe .LP \fBpasswd\fR(1), \fBcrypt\fR(3C), \fBcrypt_genhash_impl\fR(3C), \fBcrypt_gensalt\fR(3C), \fBcrypt_gensalt_impl\fR(3C), \fBgetpassphrase\fR(3C), -\fBcrypt.conf\fR(4), \fBpasswd\fR(4), \fBpolicy.conf\fR(4), -\fBattributes\fR(5), \fBcrypt_bsdbf\fR(5), \fBcrypt_bsdmd5\fR(5), -\fBcrypt_sunmd5\fR(5), \fBstandards\fR(5) +\fBcrypt.conf\fR(5), \fBpasswd\fR(5), \fBpolicy.conf\fR(5), +\fBattributes\fR(7), \fBcrypt_bsdbf\fR(7), \fBcrypt_bsdmd5\fR(7), +\fBcrypt_sunmd5\fR(7), \fBstandards\fR(7) diff --git a/usr/src/man/man7/device_clean.7 b/usr/src/man/man7/device_clean.7 index 8d90231e3c..8116d6731e 100644 --- a/usr/src/man/man7/device_clean.7 +++ b/usr/src/man/man7/device_clean.7 @@ -280,7 +280,7 @@ device clean programs .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 @@ -300,7 +300,7 @@ The Invocation is Uncommitted. The Output is Not-an-interface. .sp .LP \fBallocate\fR(1), \fBdeallocate\fR(1), \fBlist_devices\fR(1), -\fBattributes\fR(5) +\fBattributes\fR(7) .sp .LP \fISystem Administration Guide: Security Services\fR diff --git a/usr/src/man/man7/dhcp.7 b/usr/src/man/man7/dhcp.7 index ce73c873a7..a4fdbb9d76 100644 --- a/usr/src/man/man7/dhcp.7 +++ b/usr/src/man/man7/dhcp.7 @@ -19,7 +19,7 @@ This manual page provides a brief summary of the \fBDHCP\fR implementation. .SS "DHCP Client" The DHCP client is implemented as background daemon, -\fBdhcpagent\fR(1M). +\fBdhcpagent\fR(8). .LP For IPv4, this daemon is started automatically during bootup if there exists at least one \fBdhcp.\fR\fIinterface\fR file in \fB/etc\fR. Only interfaces with a @@ -35,14 +35,14 @@ Network parameters needed for system configuration during bootup are extracted from the information received by the daemon through the use of the \fBdhcpinfo\fR(1) command. The daemon's default behavior can be altered by changing the tunables in the \fB/etc/default/dhcpagent\fR file. The daemon is -controlled by the \fBifconfig\fR(1M) utility. Check the status of the daemon -using the \fBnetstat\fR(1M) and \fBifconfig\fR(1M) commands. +controlled by the \fBifconfig\fR(8) utility. Check the status of the daemon +using the \fBnetstat\fR(8) and \fBifconfig\fR(8) commands. .SH SEE ALSO -\fBdhcpinfo\fR(1), \fBdhcpagent\fR(1M), -\fBifconfig\fR(1M), -\fBin.ndpd\fR(1M), \fBnetstat\fR(1M), +\fBdhcpinfo\fR(1), \fBdhcpagent\fR(8), +\fBifconfig\fR(8), +\fBin.ndpd\fR(8), \fBnetstat\fR(8), \fBsyslog\fR(3C), -\fBdhcp_inittab\fR(4), \fBndpd.conf\fR(4) +\fBdhcp_inittab\fR(5), \fBndpd.conf\fR(5) .LP Alexander, S., and R. Droms. \fIRFC 2132, DHCP Options and BOOTP Vendor Extensions\fR. Silicon Graphics, Inc. Bucknell University. March 1997. diff --git a/usr/src/man/man7/environ.7 b/usr/src/man/man7/environ.7 index 20ce5a1098..6b0d94181d 100644 --- a/usr/src/man/man7/environ.7 +++ b/usr/src/man/man7/environ.7 @@ -21,7 +21,7 @@ A name may be placed in the environment by the \fBexport\fR command and \fIname\fR=\fIvalue\fR arguments in \fBsh\fR(1), or by one of the \fBexec\fR functions. It is unwise to conflict with certain shell variables such as \fBMAIL\fR, \fBPS1\fR, \fBPS2\fR, and \fBIFS\fR that are frequently exported by -\fB\&.profile\fR files; see \fBprofile\fR(4). +\fB\&.profile\fR files; see \fBprofile\fR(5). .LP The following environmental variables can be used by applications and are expected to be set in the target run-time environment. @@ -33,7 +33,7 @@ expected to be set in the target run-time environment. .sp .6 .RS 4n The name of the user's login directory, set by \fBlogin\fR(1) from the password -file; see \fBpasswd\fR(4). +file; see \fBpasswd\fR(5). .RE .sp @@ -529,5 +529,5 @@ The \fItime\fR has the same format as \fIoffset\fR except that no leading sign \fBgettxt\fR(3C), \fBlocaleconv\fR(3C), \fBmblen\fR(3C), \fBmktime\fR(3C), \fBnewlocale\fR(3C), \fBprintf\fR(3C), \fBsetlocale\fR(3C), \fBstrcoll\fR(3C), \fBstrftime\fR(3C), -\fBstrtod\fR(3C), \fBstrxfrm\fR(3C), \fBuselocale\fR(3C), \fBTIMEZONE\fR(4), -\fBnetconfig\fR(4), \fBpasswd\fR(4), \fBprofile\fR(4) +\fBstrtod\fR(3C), \fBstrxfrm\fR(3C), \fBuselocale\fR(3C), \fBTIMEZONE\fR(5), +\fBnetconfig\fR(5), \fBpasswd\fR(5), \fBprofile\fR(5) diff --git a/usr/src/man/man7/eqnchar.7 b/usr/src/man/man7/eqnchar.7 index 85c5db63e7..79dedbf040 100644 --- a/usr/src/man/man7/eqnchar.7 +++ b/usr/src/man/man7/eqnchar.7 @@ -36,4 +36,4 @@ print copy. .SH SEE ALSO .sp .LP -\fBeqn\fR(1), \fBnroff\fR(1), \fBtroff\fR(1), \fBattributes\fR(5) +\fBeqn\fR(1), \fBnroff\fR(1), \fBtroff\fR(1), \fBattributes\fR(7) diff --git a/usr/src/man/man7/extendedFILE.7 b/usr/src/man/man7/extendedFILE.7 index a0be3bc7fe..faee410fc0 100644 --- a/usr/src/man/man7/extendedFILE.7 +++ b/usr/src/man/man7/extendedFILE.7 @@ -145,7 +145,7 @@ enabling library .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 @@ -165,7 +165,7 @@ MT-Level Safe .LP \fBlimit\fR(1), \fBopen\fR(2), \fBenable_extended_FILE_stdio\fR(3C), \fBfdopen\fR(3C), \fBfopen\fR(3C), \fBpopen\fR(3C), \fBsignal.h\fR(3HEAD), -\fBstdio\fR(3C), \fBattributes\fR(5) +\fBstdio\fR(3C), \fBattributes\fR(7) .SH WARNINGS .sp .LP diff --git a/usr/src/man/man7/filesystem.7 b/usr/src/man/man7/filesystem.7 index cc78e3dd87..a367b40759 100644 --- a/usr/src/man/man7/filesystem.7 +++ b/usr/src/man/man7/filesystem.7 @@ -102,7 +102,7 @@ Root of the overall file system name space. .ad .sp .6 .RS 4n -The device name file system. See \fBdev\fR(7FS). +The device name file system. See \fBdev\fR(4FS). .RE .sp @@ -283,7 +283,7 @@ Terminal devices. .ad .sp .6 .RS 4n -The devices file system. See \fBdevfs\fR(7FS). +The devices file system. See \fBdevfs\fR(4FS). .RE .sp @@ -327,7 +327,7 @@ Process accounting system configuration information. .ad .sp .6 .RS 4n -Configuration information for \fBcron\fR(1M). +Configuration information for \fBcron\fR(8). .RE .sp @@ -387,7 +387,7 @@ Dynamic Host Configuration Protocol (\fBDHCP\fR) configuration files. .ad .sp .6 .RS 4n -Fault manager configuration files. For more information, see \fBfmd\fR(1M). +Fault manager configuration files. For more information, see \fBfmd\fR(8). .RE .sp @@ -450,7 +450,7 @@ Configuration files for Internet services. .sp .6 .RS 4n Shell scripts for transitioning between init states. The service management -facility, \fBsmf\fR(5) is the preferred mechanism for managing services. +facility, \fBsmf\fR(7) is the preferred mechanism for managing services. .RE .sp @@ -560,7 +560,7 @@ Solaris \fBPPP\fR configuration files. .ad .sp .6 .RS 4n -Scripts for entering or leaving run level 0. See \fBinit\fR(1M). +Scripts for entering or leaving run level 0. See \fBinit\fR(8). .RE .sp @@ -570,7 +570,7 @@ Scripts for entering or leaving run level 0. See \fBinit\fR(1M). .ad .sp .6 .RS 4n -Scripts for entering or leaving run level 1. See \fBinit\fR(1M). +Scripts for entering or leaving run level 1. See \fBinit\fR(8). .RE .sp @@ -580,7 +580,7 @@ Scripts for entering or leaving run level 1. See \fBinit\fR(1M). .ad .sp .6 .RS 4n -Scripts for entering or leaving run level 2. See \fBinit\fR(1M). +Scripts for entering or leaving run level 2. See \fBinit\fR(8). .RE .sp @@ -590,7 +590,7 @@ Scripts for entering or leaving run level 2. See \fBinit\fR(1M). .ad .sp .6 .RS 4n -Scripts for entering or leaving run level 3. See \fBinit\fR(1M). +Scripts for entering or leaving run level 3. See \fBinit\fR(8). .RE .sp @@ -651,7 +651,7 @@ Extensions). .ad .sp .6 .RS 4n -Default profile scripts for new user accounts. See \fBuseradd\fR(1M). +Default profile scripts for new user accounts. See \fBuseradd\fR(8). .RE .sp @@ -785,7 +785,7 @@ Default root of the shared file system tree. .sp .6 .RS 4n Default root of a subtree for user directories. Often managed by the -automounter, see \fBautomount\fR(1M) for more details. +automounter, see \fBautomount\fR(8) for more details. .RE .sp @@ -797,7 +797,7 @@ automounter, see \fBautomount\fR(1M) for more details. .RS 4n Subtree of platform-dependent loadable kernel modules required as part of the boot process. It includes the generic part of the core kernel that is -platform-independent, \fB/kernel/genunix\fR. See \fBkernel\fR(1M) An approved +platform-independent, \fB/kernel/genunix\fR. See \fBkernel\fR(8) An approved installation location for bundled Solaris software and for add-on system software. .RE @@ -950,7 +950,7 @@ The semantics of the series of directories is equivalent to \fB/\fR (root). .RS 4n Platform-specific modules required for boot. These modules have semantics equivalent to \fB/kernel\fR. It includes the file \fBunix\fR, the core kernel. -See \fBkernel\fR(1M). An approved installation location for bundled Solaris +See \fBkernel\fR(8). An approved installation location for bundled Solaris software and for add-on system software. .RE @@ -1043,7 +1043,7 @@ Solaris software and for add-on system software. .ad .sp .6 .RS 4n -Root of a subtree for the process file system. See \fBproc\fR(4). +Root of a subtree for the process file system. See \fBproc\fR(5). .RE .sp @@ -1067,7 +1067,7 @@ Solaris software. .sp .6 .RS 4n Mount point for the contract (CTFS) and object (OBJFS) file systems. See -\fBctfs\fR(7FS) and \fBobjfs\fR(7FS). +\fBctfs\fR(4FS) and \fBobjfs\fR(4FS). .RE .sp @@ -1078,7 +1078,7 @@ Mount point for the contract (CTFS) and object (OBJFS) file systems. See .sp .6 .RS 4n Temporary files. Usually mounted as a memory based file system. See -\fBtmpfs\fR(7FS). +\fBtmpfs\fR(4FS). .RE .sp @@ -1133,7 +1133,7 @@ Default location for Audit log files. .ad .sp .6 .RS 4n -Directory provided for global core files storage. See \fBcoreadm\fR(1M). +Directory provided for global core files storage. See \fBcoreadm\fR(8). .RE .sp @@ -1143,7 +1143,7 @@ Directory provided for global core files storage. See \fBcoreadm\fR(1M). .ad .sp .6 .RS 4n -Default depository for kernel crash dumps. See \fBdumpadm\fR(1M). +Default depository for kernel crash dumps. See \fBdumpadm\fR(8). .RE .sp @@ -1153,7 +1153,7 @@ Default depository for kernel crash dumps. See \fBdumpadm\fR(1M). .ad .sp .6 .RS 4n -Log files for \fBcron\fR(1M). +Log files for \fBcron\fR(8). .RE .sp @@ -1163,7 +1163,7 @@ Log files for \fBcron\fR(1M). .ad .sp .6 .RS 4n -Fault manager state files. For more information, see \fBfmd\fR(1M). +Fault manager state files. For more information, see \fBfmd\fR(8). .RE .sp @@ -1356,7 +1356,7 @@ Service access facility logging and accounting files. .sp .6 .RS 4n Contains directories for files used in printer spooling, mail delivery, -\fBcron\fR(1M), \fBat\fR(1), and so forth. +\fBcron\fR(8), \fBat\fR(1), and so forth. .RE .sp @@ -1366,7 +1366,7 @@ Contains directories for files used in printer spooling, mail delivery, .ad .sp .6 .RS 4n -\fBsendmail\fR(1M) client files. +\fBsendmail\fR(8) client files. .RE .sp @@ -1376,7 +1376,7 @@ Contains directories for files used in printer spooling, mail delivery, .ad .sp .6 .RS 4n -\fBcron\fR(1M) and \fBat\fR(1) spooling files. +\fBcron\fR(8) and \fBat\fR(1) spooling files. .RE .sp @@ -1537,7 +1537,7 @@ property. .ad .sp .6 .RS 4n -Databases used by \fBNIS\fR and \fBypbind\fR(1M). +Databases used by \fBNIS\fR and \fBypbind\fR(8). .RE .SS "\fB/usr\fR File System" @@ -1818,7 +1818,7 @@ x86 platforms. .ad .sp .6 .RS 4n -Accounting scripts and binaries. See \fBacct\fR(1M). +Accounting scripts and binaries. See \fBacct\fR(8). .RE .sp @@ -1872,7 +1872,7 @@ Contains \fBcfgadm\fR hardware-specific driver plugins. .sp .6 .RS 4n Scheduling-class-specific directories containing executables for -\fBpriocntl\fR(1) and \fBdispadmin\fR(1M). +\fBpriocntl\fR(1) and \fBdispadmin\fR(8). .RE .sp @@ -2409,7 +2409,7 @@ Symbolic link to the \fB/usr/share/man\fR directory. .sp .6 .RS 4n Entry points for foreign name service requests relayed using the network -listener. See \fBlisten\fR(1M). +listener. See \fBlisten\fR(8). .RE .sp @@ -2770,7 +2770,7 @@ Tab setting escape sequences. .ad .sp .6 .RS 4n -Terminal description files for \fBterminfo\fR(4). +Terminal description files for \fBterminfo\fR(5). .RE .sp @@ -2941,10 +2941,10 @@ Directory for newer versions of POSIX-compliant utilities. \fBisainfo\fR(1), \fBmail\fR(1), \fBmailx\fR(1), \fBnroff\fR(1), \fBpriocntl\fR(1), \fBrefer\fR(1), \fBsar\fR(1), \fBsh\fR(1), \fBspell\fR(1), \fBsvcs\fR(1), \fBtroff\fR(1), \fBuname\fR(1), \fBuucp\fR(1C), \fBvi\fR(1), -\fBacct\fR(1M), \fBcron\fR(1M), \fBdispadmin\fR(1M), \fBdladm\fR(1M), -\fBfmd\fR(1M), \fBfsck\fR(1M), \fBinit\fR(1M), \fBkernel\fR(1M), -\fBmknod\fR(1M), \fBmount\fR(1M), \fBsvcadm\fR(1M), \fBsvccfg\fR(1M), -\fBuseradd\fR(1M), \fBypbind\fR(1M), \fBmount\fR(2), \fBIntro\fR(4), -\fBproc\fR(4), \fBterminfo\fR(4), \fBsmf\fR(5), \fBctfs\fR(7FS), -\fBdev\fR(7FS), \fBdevfs\fR(7FS), \fBctfs\fR(7FS), \fBobjfs\fR(7FS), -\fBtmpfs\fR(7FS) +\fBacct\fR(8), \fBcron\fR(8), \fBdispadmin\fR(8), \fBdladm\fR(8), +\fBfmd\fR(8), \fBfsck\fR(8), \fBinit\fR(8), \fBkernel\fR(8), +\fBmknod\fR(8), \fBmount\fR(8), \fBsvcadm\fR(8), \fBsvccfg\fR(8), +\fBuseradd\fR(8), \fBypbind\fR(8), \fBmount\fR(2), \fBIntro\fR(5), +\fBproc\fR(5), \fBterminfo\fR(5), \fBsmf\fR(7), \fBctfs\fR(4FS), +\fBdev\fR(4FS), \fBdevfs\fR(4FS), \fBctfs\fR(4FS), \fBobjfs\fR(4FS), +\fBtmpfs\fR(4FS) diff --git a/usr/src/man/man7/fnmatch.7 b/usr/src/man/man7/fnmatch.7 index 869abcd279..7fab5ced54 100644 --- a/usr/src/man/man7/fnmatch.7 +++ b/usr/src/man/man7/fnmatch.7 @@ -53,7 +53,7 @@ matching strings in the shell. Historically, pattern matching notation is related to, but slightly different from, the regular expression notation. For this reason, the description of the rules for this pattern matching notation is based on the description of regular expression notation described on the -\fBregex\fR(5) manual page. +\fBregex\fR(7) manual page. .SS "Patterns Matching a Single Character" .LP The following patterns match a single character: \fIordinary characters\fR, @@ -104,7 +104,7 @@ The open bracket will introduce a pattern bracket expression. .sp .LP The description of basic regular expression bracket expressions on the -\fBregex\fR(5) manual page also applies to the pattern bracket expression, +\fBregex\fR(7) manual page also applies to the pattern bracket expression, except that the exclamation-mark character \fB(\fR \fB!\fR \fB)\fR replaces the circumflex character (\fB^\fR) in its role in a \fInon-matching list\fR in the regular expression notation. A bracket expression starting with an unquoted @@ -335,4 +335,4 @@ pattern string is left unchanged. .RE .SH SEE ALSO .LP -\fBfind\fR(1), \fBksh\fR(1), \fBfnmatch\fR(3C), \fBregex\fR(5) +\fBfind\fR(1), \fBksh\fR(1), \fBfnmatch\fR(3C), \fBregex\fR(7) diff --git a/usr/src/man/man7/fsattr.7 b/usr/src/man/man7/fsattr.7 index 50a44bcc61..e6adec0149 100644 --- a/usr/src/man/man7/fsattr.7 +++ b/usr/src/man/man7/fsattr.7 @@ -633,7 +633,7 @@ error = unlinkat(attrdirfd, "attr"); Applications intending to access the interfaces defined here as well as the POSIX and X/Open specification-conforming interfaces should define the macro \fB_ATFILE_SOURCE\fR to be 1 and set whichever feature test macros are -appropriate to obtain the desired environment. See \fBstandards\fR(5). +appropriate to obtain the desired environment. See \fBstandards\fR(7). .SS "Extended Archive Formats" .sp .LP @@ -791,7 +791,7 @@ of this record is identical to the record described above. .sp .LP \fBcp\fR(1), \fBcpio\fR(1), \fBfind\fR(1), \fBls\fR(1), \fBmv\fR(1), -\fBpax\fR(1), \fBrunat\fR(1), \fBtar\fR(1), \fBdu\fR(1), \fBfsck\fR(1M), +\fBpax\fR(1), \fBrunat\fR(1), \fBtar\fR(1), \fBdu\fR(1), \fBfsck\fR(8), \fBchown\fR(2), \fBlink\fR(2), \fBopen\fR(2), \fBpathconf\fR(2), \fBrename\fR(2), \fBstat\fR(2), \fBunlink\fR(2), \fButimes\fR(2), -\fBattropen\fR(3C), \fBstandards\fR(5) +\fBattropen\fR(3C), \fBstandards\fR(7) diff --git a/usr/src/man/man7/grub.7 b/usr/src/man/man7/grub.7 index 75234ef779..289c6812c8 100644 --- a/usr/src/man/man7/grub.7 +++ b/usr/src/man/man7/grub.7 @@ -46,7 +46,7 @@ distribution: .sp .ne 2 .na -\fB\fBbootadm\fR(1M)\fR +\fB\fBbootadm\fR(8)\fR .ad .RS 19n Enables you to manage the boot archive and make changes to the GRUB menu. @@ -55,7 +55,7 @@ Enables you to manage the boot archive and make changes to the GRUB menu. .sp .ne 2 .na -\fB\fBinstallgrub\fR(1M)\fR +\fB\fBinstallgrub\fR(8)\fR .ad .RS 19n Loads the boot program from disk. @@ -73,7 +73,7 @@ man page describes the GRUB shell. .SH SEE ALSO .sp .LP -\fBboot\fR(1M), \fBbootadm\fR(1M), \fBinstallgrub\fR(1M) +\fBboot\fR(8), \fBbootadm\fR(8), \fBinstallgrub\fR(8) .sp .LP \fISolaris Express Installation Guide: Basic Installations\fR diff --git a/usr/src/man/man7/gss_auth_rules.7 b/usr/src/man/man7/gss_auth_rules.7 index cd9de714a0..d690625c35 100644 --- a/usr/src/man/man7/gss_auth_rules.7 +++ b/usr/src/man/man7/gss_auth_rules.7 @@ -30,7 +30,7 @@ The GSS authorization rules are as follows: .el o If the mechanism of the connection has a set of authorization rules, then use those rules. For example, if the mechanism is Kerberos, then use the -\fBkrb5_auth_rules\fR(5), so that authorization is consistent between raw +\fBkrb5_auth_rules\fR(7), so that authorization is consistent between raw Kerberos applications and GSS/Kerberos applications. .RE .RS +4 @@ -50,13 +50,13 @@ local user's \fBgssname\fR exactly, as compared by .ad .RS 15n System account file. This information may also be in a directory service. See -\fBpasswd\fR(4). +\fBpasswd\fR(5). .RE .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 @@ -72,5 +72,5 @@ Interface Stability Evolving .SH SEE ALSO .sp .LP -\fBftp\fR(1), \fBssh\fR(1), \fBgsscred\fR(1M), \fBgss_compare_name\fR(3GSS), -\fBpasswd\fR(4), \fBattributes\fR(5), \fBkrb5_auth_rules\fR(5) +\fBftp\fR(1), \fBssh\fR(1), \fBgsscred\fR(8), \fBgss_compare_name\fR(3GSS), +\fBpasswd\fR(5), \fBattributes\fR(7), \fBkrb5_auth_rules\fR(7) diff --git a/usr/src/man/man7/hal.7 b/usr/src/man/man7/hal.7 index db2fd09717..3006ca05d6 100644 --- a/usr/src/man/man7/hal.7 +++ b/usr/src/man/man7/hal.7 @@ -26,12 +26,12 @@ devices are added and removed, as well as when properties on a device are changing. .sp .LP -In the Solaris operating system, HAL is supported by a daemon, \fBhald\fR(1M), +In the Solaris operating system, HAL is supported by a daemon, \fBhald\fR(8), and a set of utilities that enable the adding and removing of devices and the modification of their properties. .SH SEE ALSO .LP -\fBhald\fR(1M), \fBfdi\fR(4) +\fBhald\fR(8), \fBfdi\fR(5) .sp .LP See the HAL pages, including the HAL specification, under diff --git a/usr/src/man/man7/iconv.7 b/usr/src/man/man7/iconv.7 index 5e3de92019..25061b5f01 100644 --- a/usr/src/man/man7/iconv.7 +++ b/usr/src/man/man7/iconv.7 @@ -305,8 +305,8 @@ List of conversions supported by conversion tables. .SH SEE ALSO .sp .LP -\fBiconv\fR(1), \fBiconv\fR(3C), \fBiconv_1250\fR(5), \fBiconv_1251\fR(5), -\fBiconv_646\fR(5), \fBiconv_852\fR(5), \fBiconv_8859-1\fR(5), -\fBiconv_8859-2\fR(5), \fBiconv_8859-5\fR(5), \fBiconv_dhn\fR(5), -\fBiconv_koi8-r\fR(5), \fBiconv_mac_cyr\fR(5), \fBiconv_maz\fR(5), -\fBiconv_pc_cyr\fR(5), \fBiconv_unicode\fR(5) +\fBiconv\fR(1), \fBiconv\fR(3C), \fBiconv_1250\fR(7), \fBiconv_1251\fR(7), +\fBiconv_646\fR(7), \fBiconv_852\fR(7), \fBiconv_8859-1\fR(7), +\fBiconv_8859-2\fR(7), \fBiconv_8859-5\fR(7), \fBiconv_dhn\fR(7), +\fBiconv_koi8-r\fR(7), \fBiconv_mac_cyr\fR(7), \fBiconv_maz\fR(7), +\fBiconv_pc_cyr\fR(7), \fBiconv_unicode\fR(7) diff --git a/usr/src/man/man7/iconv_unicode.7 b/usr/src/man/man7/iconv_unicode.7 index 7608021094..432471fab7 100644 --- a/usr/src/man/man7/iconv_unicode.7 +++ b/usr/src/man/man7/iconv_unicode.7 @@ -168,7 +168,7 @@ conversion modules .SH SEE ALSO .sp .LP -\fBiconv\fR(1), \fBiconv\fR(3C), \fBiconv\fR(5) +\fBiconv\fR(1), \fBiconv\fR(3C), \fBiconv\fR(7) .sp .LP Chernov, A., \fIRegistration of a Cyrillic Character Set\fR, RFC 1489, RELCOM diff --git a/usr/src/man/man7/ieee802.11.7 b/usr/src/man/man7/ieee802.11.7 index 718bc6798b..1851e123ab 100644 --- a/usr/src/man/man7/ieee802.11.7 +++ b/usr/src/man/man7/ieee802.11.7 @@ -11,7 +11,7 @@ ieee802.11 \- 802.11 kernel statistics .LP This page describes the kernel statistics that can be used to monitor attributes specific to the 802.11 physical layer. These statistics can be -retrieved using \fBkstat\fR(1M). Not all 802.11 devices will support all +retrieved using \fBkstat\fR(8). Not all 802.11 devices will support all statistics. .sp .ne 2 @@ -137,4 +137,4 @@ supported. .SH SEE ALSO .sp .LP -\fBkstat\fR(1M) +\fBkstat\fR(8) diff --git a/usr/src/man/man7/ipfilter.7 b/usr/src/man/man7/ipfilter.7 index 6424553331..8ab6599eb0 100644 --- a/usr/src/man/man7/ipfilter.7 +++ b/usr/src/man/man7/ipfilter.7 @@ -13,7 +13,7 @@ system. On a properly setup system, it can be used to build a firewall. .sp .LP Solaris IP Filter is installed with the Solaris operating system. However, -packet filtering is not enabled by default. See \fBipf\fR(1M) for a procedure +packet filtering is not enabled by default. See \fBipf\fR(8) for a procedure to enable and activate the IP Filter feature. .SH HOST-BASED FIREWALL .LP @@ -30,11 +30,11 @@ Note - .sp .RS 2 Users can still specify their own ipf rule file if they choose not to take -advantage of the framework. See \fBipf\fR(1M) and \fBipf\fR(4). +advantage of the framework. See \fBipf\fR(8) and \fBipf\fR(5). .RE .SS "Model" .LP -This section describes the host-based firewall framework. See svc.ipfd(1M) for +This section describes the host-based firewall framework. See svc.ipfd(8) for details on how to configure firewall policies. .sp .LP @@ -164,7 +164,7 @@ service and system-wide policy(s) whose firewall mode is not \fBNone\fR. .sp .LP A user configures a firewall by setting the system-wide policies and policy for -each network service. See svc.ipfd(1M) on how to configure a firewall policy. +each network service. See svc.ipfd(8) on how to configure a firewall policy. .sp .LP The firewall framework composes of policy configuration and a mechanism to @@ -188,7 +188,7 @@ network services' policies are stored in each SMF service .ie t \(bu .el o a user activates a firewall by enabling \fBnetwork/ipfilter\fR (see -\fBipf\fR(1M)) +\fBipf\fR(8)) .RE .RS +4 .TP @@ -292,7 +292,7 @@ traffic flow looks like the following diagram. .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 @@ -307,16 +307,16 @@ Interface Stability Committed .SH SEE ALSO .LP -\fBsvcs\fR(1), \fBipf\fR(1M), \fBipnat\fR(1M), \fBsvcadm\fR(1M), -\fBsvc.ipfd\fR(1M), \fBipf\fR(4), \fBipnat\fR(4), \fBattributes\fR(5), -\fBsmf\fR(5) +\fBsvcs\fR(1), \fBipf\fR(8), \fBipnat\fR(8), \fBsvcadm\fR(8), +\fBsvc.ipfd\fR(8), \fBipf\fR(5), \fBipnat\fR(5), \fBattributes\fR(7), +\fBsmf\fR(7) .sp .LP \fISystem Administration Guide: IP Services\fR .SH NOTES .LP The \fBipfilter\fR service is managed by the service management facility, -\fBsmf\fR(5), under the service identifier: +\fBsmf\fR(7), under the service identifier: .sp .in +2 .nf @@ -328,7 +328,7 @@ svc:/network/ipfilter:default .sp .LP Administrative actions on this service, such as enabling, disabling, or -requesting restart, can be performed using \fBsvcadm\fR(1M). The service's +requesting restart, can be performed using \fBsvcadm\fR(8). The service's status can be queried using the \fBsvcs\fR(1) command. .sp .LP diff --git a/usr/src/man/man7/kerberos.7 b/usr/src/man/man7/kerberos.7 index 64d452c739..d8f5747b38 100644 --- a/usr/src/man/man7/kerberos.7 +++ b/usr/src/man/man7/kerberos.7 @@ -28,7 +28,7 @@ unique ticket, its identity is guaranteed. .LP To obtain tickets, a client must first initialize the Kerberos session, either by using the \fBkinit\fR(1) command or a \fBPAM\fR module. (See -\fBpam_krb5\fR(5)). \fBkinit\fR prompts for a password, and then communicates +\fBpam_krb5\fR(7)). \fBkinit\fR prompts for a password, and then communicates with a \fIKey Distribution Center\fR (\fBKDC\fR). The \fBKDC\fR returns a \fITicket-Granting Ticket\fR (\fBTGT\fR) and prompts for a confirmation password. If the client confirms the password, it can use the Ticket-Granting @@ -133,7 +133,7 @@ the words \fBadmin\fR and \fBhost\fR are reserved keywords. .SH SEE ALSO \fBkdestroy\fR(1), \fBkinit\fR(1), \fBklist\fR(1), \fBkpasswd\fR(1), -\fBkrb5.conf\fR(4), \fBkrb5envvar\fR(5) +\fBkrb5.conf\fR(5), \fBkrb5envvar\fR(7) .sp .LP \fISystem Administration Guide: Security Services\fR diff --git a/usr/src/man/man7/krb5_auth_rules.7 b/usr/src/man/man7/krb5_auth_rules.7 index 3a383226a7..57341299e6 100644 --- a/usr/src/man/man7/krb5_auth_rules.7 +++ b/usr/src/man/man7/krb5_auth_rules.7 @@ -25,7 +25,7 @@ such as \fBjdb@ENG.EXAMPLE.COM\fR and \fBjdb/happy.eng.example.com@ENG.EXAMPLE.C would each be legal, though not equivalent, Kerberos principals. The client is granted access if the \fB~/.k5login\fR file is located in the login directory of the remote user account and if the originating user can be authenticated to -one of the principals named in the file. See \fBkadm5.acl\fR(4) for more +one of the principals named in the file. See \fBkadm5.acl\fR(5) for more information on Kerberos principal names. .sp .LP @@ -35,13 +35,13 @@ against the \fBgsscred\fR table. If a \fBgsscred\fR table exists and the principal name is matched in the table, access is granted if the Unix user ID listed in the table corresponds to the user account the client is attempting to access. If the Unix user ID does not match, access is denied. See -\fBgsscred\fR(1M). +\fBgsscred\fR(8). .sp .LP For example, an originating user listed in the \fBgsscred\fR table with the principal name \fBjdb@ENG.EXAMPLE.COM\fR and the \fBuid\fR \fB23154\fR is granted access to the \fBjdb-user\fR account if \fB23154\fR is also the \fBuid\fR of -\fBjdb-user\fR listed in the user account database. See \fBpasswd\fR(4). +\fBjdb-user\fR listed in the user account database. See \fBpasswd\fR(5). .sp .LP Finally, if there is no \fB~/.k5login\fR file and the Kerberos V5 identity of @@ -60,7 +60,7 @@ account name specified by the client. .ie t \(bu .el o The realm part of the client and server are the same, unless the -\fBkrb5.conf\fR(4) \fIauth_to_local_realm\fR parameter is used to create +\fBkrb5.conf\fR(5) \fIauth_to_local_realm\fR parameter is used to create equivalence. .RE .RS +4 @@ -78,7 +78,7 @@ server. This is because the realms \fBSALES.EXAMPLE.COM\fR and \fBENG.EXAMPLE.CO differ. .sp .LP -The \fBkrb5.conf\fR(4) \fIauth_to_local_realm\fR parameter also affects +The \fBkrb5.conf\fR(5) \fIauth_to_local_realm\fR parameter also affects authorization. Non-default realms can be equated with the default realm for authenticated \fBname-to-local name\fR mapping. .SH FILES @@ -97,11 +97,11 @@ Per user-account authorization file. .ad .RS 15n System account file. This information may also be in a directory service. See -\fBpasswd\fR(4). +\fBpasswd\fR(5). .RE .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 @@ -116,6 +116,6 @@ Interface Stability Evolving .SH SEE ALSO \fBftp\fR(1), \fBrcp\fR(1), \fBrdist\fR(1), \fBrlogin\fR(1), \fBrsh\fR(1), -\fBtelnet\fR(1), \fBgsscred\fR(1M), \fBkadm5.acl\fR(4), -\fBkrb5.conf\fR(4), \fBpasswd\fR(4), \fBattributes\fR(5), -\fBgss_auth_rules\fR(5) +\fBtelnet\fR(1), \fBgsscred\fR(8), \fBkadm5.acl\fR(5), +\fBkrb5.conf\fR(5), \fBpasswd\fR(5), \fBattributes\fR(7), +\fBgss_auth_rules\fR(7) diff --git a/usr/src/man/man7/krb5envvar.7 b/usr/src/man/man7/krb5envvar.7 index 85563a4491..c2c80a7a6b 100644 --- a/usr/src/man/man7/krb5envvar.7 +++ b/usr/src/man/man7/krb5envvar.7 @@ -50,7 +50,7 @@ associated file are readable by the invoking process. Care must be taken to ensure that the file is readable only by the set of principals that need to retrieve their unencrypted keys. .sp -The \fBWRFILE\fR type is used by the \fBkadmin\fR(1M) command. Specifying this +The \fBWRFILE\fR type is used by the \fBkadmin\fR(8) command. Specifying this type allows the administrator to designate an alternate \fBkeytab\fR file to write to without using extra command line arguments for file location. .RE @@ -156,7 +156,7 @@ condition obtains: .el o The duration from the last write to the replay cache before reboot to the point when the Kerberized server applications are running is less than the Kerberos -clockskew (see \fBkrb5.conf\fR(4)). +clockskew (see \fBkrb5.conf\fR(5)). .RE When specifying the \fBNONE\fR replay cache time you need to understand that this disables the replay cache, and all security risks that this presents. This @@ -208,7 +208,7 @@ another file specified by KRB5_CONFIG. For example (using kinit from .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 @@ -224,5 +224,5 @@ Interface Stability Uncommitted .SH SEE ALSO .sp .LP -\fBchmod\fR(1), \fBkinit\fR(1), \fBklist\fR(1), \fBksh\fR(1), \fBkadmin\fR(1M), -\fBkadmind\fR(1M), \fBkrb5.conf\fR(4), \fBattributes\fR(5), \fBkerberos\fR(5) +\fBchmod\fR(1), \fBkinit\fR(1), \fBklist\fR(1), \fBksh\fR(1), \fBkadmin\fR(8), +\fBkadmind\fR(8), \fBkrb5.conf\fR(5), \fBattributes\fR(7), \fBkerberos\fR(7) diff --git a/usr/src/man/man7/largefile.7 b/usr/src/man/man7/largefile.7 index dc4b2b22dd..94e6e18af0 100644 --- a/usr/src/man/man7/largefile.7 +++ b/usr/src/man/man7/largefile.7 @@ -98,7 +98,7 @@ l l l l l . .TE .LP -See the USAGE section of the \fBswap\fR(1M) manual page for limitations of +See the USAGE section of the \fBswap\fR(8) manual page for limitations of \fBswap\fR on block devices greater than 2 Gbyte on a 32-bit operating system. .sp .LP @@ -226,4 +226,4 @@ l l l l l . .SH SEE ALSO .LP -\fBlf64\fR(5), \fBlfcompile\fR(5), \fBlfcompile64\fR(5) +\fBlf64\fR(7), \fBlfcompile\fR(7), \fBlfcompile64\fR(7) diff --git a/usr/src/man/man7/lf64.7 b/usr/src/man/man7/lf64.7 index caef0970a0..059db5c0f5 100644 --- a/usr/src/man/man7/lf64.7 +++ b/usr/src/man/man7/lf64.7 @@ -10,7 +10,7 @@ lf64 \- transitional interfaces for 64-bit file offsets .SH DESCRIPTION The data types, interfaces, and macros described on this page provide explicit access to 64-bit file offsets. They are accessible through the transitional -compilation environment described on the \fBlfcompile64\fR(5) manual page. The +compilation environment described on the \fBlfcompile64\fR(7) manual page. The function prototype and semantics of a transitional interface are equivalent to those of the standard version of the call, except that relevant data types are 64-bit entities. @@ -344,4 +344,4 @@ int \fBtruncate\fR(..., \fBoff_t\fR); int \fBtruncate64\fR(..., \fBoff64_t\fR); .TE .SH SEE ALSO -\fBlfcompile\fR(5), \fBlfcompile64\fR(5) +\fBlfcompile\fR(7), \fBlfcompile64\fR(7) diff --git a/usr/src/man/man7/lfcompile.7 b/usr/src/man/man7/lfcompile.7 index 6b8c2d5b6e..fac4d24947 100644 --- a/usr/src/man/man7/lfcompile.7 +++ b/usr/src/man/man7/lfcompile.7 @@ -28,7 +28,7 @@ All relevant data types are defined to be of correct size (for example, An application compiled in this environment is able to use the \fIxxx\fR\fB()\fR source interfaces to access both large and small files, rather than having to explicitly utilize the transitional \fIxxx\fR\fB64()\fR -interface calls to access large files. See the \fBlfcompile64\fR(5) manual page +interface calls to access large files. See the \fBlfcompile64\fR(7) manual page for information regarding the transitional compilation environment. .sp .LP @@ -85,7 +85,7 @@ information about \fBfseeko()\fR and \fBftello()\fR. Applications wishing to access \fBfseeko()\fR and \fBftello()\fR as well as the POSIX and X/Open specification-conforming interfaces should define the macro \fB_LARGEFILE_SOURCE\fR to be 1 and set whichever feature test macros are -appropriate to obtain the desired environment (see \fBstandards\fR(5)). +appropriate to obtain the desired environment (see \fBstandards\fR(7)). .SH EXAMPLES .sp .LP @@ -147,8 +147,8 @@ $ c89 -D_LARGEFILE_SOURCE a.c .sp .LP \fBcsh\fR(1), \fBgetconf\fR(1), \fBksh\fR(1), \fByacc\fR(1), \fBsh\fR(1), -\fBfseek\fR(3C), \fBftell\fR(3C), \fBlf64\fR(5), \fBlfcompile64\fR(5), -\fBstandards\fR(5) +\fBfseek\fR(3C), \fBftell\fR(3C), \fBlf64\fR(7), \fBlfcompile64\fR(7), +\fBstandards\fR(7) .SH NOTES .sp .LP diff --git a/usr/src/man/man7/lfcompile64.7 b/usr/src/man/man7/lfcompile64.7 index d921dd5a24..b323168039 100644 --- a/usr/src/man/man7/lfcompile64.7 +++ b/usr/src/man/man7/lfcompile64.7 @@ -25,7 +25,7 @@ functions (\fIxxx\fR\fB64()\fR) and types in addition to all the regular functions (\fIxxx\fR\fB()\fR) and types. Both \fIxxx\fR\fB()\fR and \fIxxx\fR\fB64()\fR functions are available to the program source. A 32-bit application must use the \fIxxx\fR\fB64()\fR functions in order to access large -files. See the \fBlf64\fR(5) manual page for a complete listing of the 64-bit +files. See the \fBlf64\fR(7) manual page for a complete listing of the 64-bit transitional interfaces. .sp .LP @@ -35,7 +35,7 @@ functions, structures, and types. An application compiled in the large file compilation environment is able to use the \fIxxx\fR\fB()\fR source interfaces to access both large and small files, rather than having to explicitly utilize the transitional \fIxxx\fR\fB64()\fR interface calls to access large files. See -the \fBlfcompile\fR(5) manual page for more information regarding the large +the \fBlfcompile\fR(7) manual page for more information regarding the large file compilation environment. .sp .LP @@ -55,7 +55,7 @@ No compile-time flags need to be set. Applications that wish to access the transitional interfaces as well as the POSIX or X/Open specification-conforming interfaces should use the following compilation methods and set whichever feature test macros are appropriate to -obtain the desired environment (see \fBstandards\fR(5)). +obtain the desired environment (see \fBstandards\fR(7)). .RS +4 .TP .ie t \(bu @@ -130,5 +130,5 @@ interfaces: .SH SEE ALSO .sp .LP -\fBgetconf\fR(1), \fBlseek\fR(2), \fBfopen\fR(3C), \fBlf64\fR(5), -\fBstandards\fR(5) +\fBgetconf\fR(1), \fBlseek\fR(2), \fBfopen\fR(3C), \fBlf64\fR(7), +\fBstandards\fR(7) diff --git a/usr/src/man/man7/locale.7 b/usr/src/man/man7/locale.7 index 01c2116fde..f7c0958436 100644 --- a/usr/src/man/man7/locale.7 +++ b/usr/src/man/man7/locale.7 @@ -718,7 +718,7 @@ the mapping will be the reverse mapping of the one specified for \fBtoupper\fR. .SS "LC_COLLATE" The \fBLC_COLLATE\fR category provides a collation sequence definition for numerous utilities (such as \fBsort\fR(1), \fBuniq\fR(1), and so forth), -regular expression matching (see \fBregex\fR(5)), and the \fBstrcoll\fR(3C), +regular expression matching (see \fBregex\fR(7)), and the \fBstrcoll\fR(3C), \fBstrxfrm\fR(3C), \fBwcscoll\fR(3C), and \fBwcsxfrm\fR(3C) functions. .sp .LP @@ -2361,7 +2361,7 @@ four keywords. \fB\fByesexpr\fR\fR .ad .RS 11n -The operand consists of an extended regular expression (see \fBregex\fR(5)) +The operand consists of an extended regular expression (see \fBregex\fR(7)) that describes the acceptable affirmative response to a question expecting an affirmative or negative response. .RE @@ -2444,5 +2444,5 @@ In an application conforming to the SUSv3 standard, the information on \fBuniq\fR(1), \fBlocaleconv\fR(3C), \fBnl_langinfo\fR(3C), \fBsetlocale\fR(3C), \fBstrcoll\fR(3C), \fBstrftime\fR(3C), \fBstrptime\fR(3C), \fBstrxfrm\fR(3C), \fBwcscoll\fR(3C), \fBwcsftime\fR(3C), \fBwcsxfrm\fR(3C), -\fBwctype\fR(3C), \fBattributes\fR(5), \fBcharmap\fR(5), \fBextensions\fR(5), -\fBregex\fR(5) +\fBwctype\fR(3C), \fBattributes\fR(7), \fBcharmap\fR(7), \fBextensions\fR(7), +\fBregex\fR(7) diff --git a/usr/src/man/man7/mansun.7 b/usr/src/man/man7/mansun.7 index cd4dfc48d2..557dc3f644 100644 --- a/usr/src/man/man7/mansun.7 +++ b/usr/src/man/man7/mansun.7 @@ -311,4 +311,4 @@ Dale Dougherty and Tim O'Reilly, \fIUnix\fR \fIText\fR \fIProcessing\fR .SH NOTES .LP -New manual pages should be coded in the \fBmdoc\fR(5) format. +New manual pages should be coded in the \fBmdoc\fR(7) format. diff --git a/usr/src/man/man7/mdoc.7 b/usr/src/man/man7/mdoc.7 index 113b8cacfc..b1c1e15ce0 100644 --- a/usr/src/man/man7/mdoc.7 +++ b/usr/src/man/man7/mdoc.7 @@ -3315,7 +3315,7 @@ guide for advanced authors, and an alphabetic index helping to choose the best macros for various kinds of content. .Pp The manual page -.Lk https://man.voidlinux.org/groff_mdoc "groff_mdoc(7)" +.Lk https://man.voidlinux.org/groff_mdoc "groff_mdoc(4)" contained in the .Dq groff package documents exactly the same language in a somewhat different style. diff --git a/usr/src/man/man7/mech_spnego.7 b/usr/src/man/man7/mech_spnego.7 index f05ea7a18c..70e8c64600 100644 --- a/usr/src/man/man7/mech_spnego.7 +++ b/usr/src/man/man7/mech_spnego.7 @@ -30,7 +30,7 @@ server and neither side knows what mechanisms are supported by the other. .LP When SPNEGO is used, it selects the list of mechanisms to advertise by reading the \fBGSS\fR mechanism configuration file, \fB/etc/gss/mech\fR (see -\fBmech\fR(4)), and by listing all active mechanisms except for itself. +\fBmech\fR(5)), and by listing all active mechanisms except for itself. .SH OPTIONS .sp .LP @@ -97,7 +97,7 @@ x86 64-bit shared object 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 @@ -113,7 +113,7 @@ MT Level Safe .SH SEE ALSO .sp .LP -\fBIntro\fR(3), \fBlibgss\fR(3LIB), \fBmech\fR(4), \fBattributes\fR(5) +\fBIntro\fR(3), \fBlibgss\fR(3LIB), \fBmech\fR(5), \fBattributes\fR(7) .sp .LP \fISolaris Security for Developers Guide\fR diff --git a/usr/src/man/man7/mm.7 b/usr/src/man/man7/mm.7 index 466169bbf1..91217a11ad 100644 --- a/usr/src/man/man7/mm.7 +++ b/usr/src/man/man7/mm.7 @@ -433,7 +433,7 @@ these strings should come after, rather than before, the letter to be accented. .sp .LP \fBcol\fR(1), \fBeqn\fR(1), \fBnroff\fR(1), \fBrefer\fR(1), \fBtbl\fR(1), -\fBtroff\fR(1), \fBattributes\fR(5) +\fBtroff\fR(1), \fBattributes\fR(7) .SH BUGS .sp .LP diff --git a/usr/src/man/man7/mutex.7 b/usr/src/man/man7/mutex.7 index b112565183..c70083eab8 100644 --- a/usr/src/man/man7/mutex.7 +++ b/usr/src/man/man7/mutex.7 @@ -132,7 +132,7 @@ deadlocks, or worse, data inconsistencies. .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 @@ -153,7 +153,7 @@ MT-Level MT-Safe \fBpthread_create\fR(3C), \fBpthread_mutex_destroy\fR(3C), \fBpthread_mutex_init\fR(3C), \fBpthread_mutex_lock\fR(3C), \fBpthread_mutex_trylock\fR(3C), \fBpthread_mutex_unlock\fR(3C), -\fBpthread_mutexattr_init\fR(3C), \fBattributes\fR(5), \fBstandards\fR(5) +\fBpthread_mutexattr_init\fR(3C), \fBattributes\fR(7), \fBstandards\fR(7) .SH NOTES .sp .LP diff --git a/usr/src/man/man7/nfssec.7 b/usr/src/man/man7/nfssec.7 index 69f19afd8c..51f1aaeed8 100644 --- a/usr/src/man/man7/nfssec.7 +++ b/usr/src/man/man7/nfssec.7 @@ -9,18 +9,18 @@ nfssec \- overview of NFS security modes .SH DESCRIPTION .LP -The \fBmount_nfs\fR(1M) and \fBshare_nfs\fR(1M) commands each provide a way to +The \fBmount_nfs\fR(8) and \fBshare_nfs\fR(8) commands each provide a way to specify the security mode to be used on an \fBNFS\fR file system through the \fBsec=\fR\fImode\fR option. \fImode\fR can be \fBsys\fR, \fBdh\fR, \fBkrb5\fR, \fBkrb5i\fR, \fBkrb5p\fR, or \fBnone\fR. These security modes can also be added -to the automount maps. Note that \fBmount_nfs\fR(1M) and \fBautomount\fR(1M) do -not support \fBsec=none\fR at this time. \fBmount_nfs\fR(1M) allows you to -specify a single security mode; \fBshare_nfs\fR(1M) allows you to specify +to the automount maps. Note that \fBmount_nfs\fR(8) and \fBautomount\fR(8) do +not support \fBsec=none\fR at this time. \fBmount_nfs\fR(8) allows you to +specify a single security mode; \fBshare_nfs\fR(8) allows you to specify multiple modes (or \fBnone\fR). With multiple modes, an NFS client can choose any of the modes in the list. .sp .LP -The \fBsec=\fR\fImode\fR option on the \fBshare_nfs\fR(1M) command line +The \fBsec=\fR\fImode\fR option on the \fBshare_nfs\fR(8) command line establishes the security mode of \fBNFS\fR servers. If the \fBNFS\fR connection uses the \fBNFS\fR Version 3 protocol, the \fBNFS\fR clients must query the server for the appropriate \fImode\fR to use. If the \fBNFS\fR connection uses @@ -41,7 +41,7 @@ the client. The \fBNFS\fR security modes are described below. Of these, the \fBkrb5\fR, \fBkrb5i\fR, \fBkrb5p\fR modes use the Kerberos V5 protocol for authenticating and protecting the shared filesystems. Before these can be used, the system -must be configured to be part of a Kerberos realm. See \fBkerberos\fR(5). +must be configured to be part of a Kerberos realm. See \fBkerberos\fR(7). .sp .ne 2 .na @@ -118,7 +118,7 @@ the one with which a Solaris \fBNFS\fR server shares the file system has its security mode mapped to \fBAUTH_NONE.\fR In this case, if the file system is shared with \fBsec=none,\fR users from the client are mapped to the anonymous user. The \fBNFS\fR security mode \fBnone\fR is supported by -\fBshare_nfs\fR(1M), but not by \fBmount_nfs\fR(1M) or \fBautomount\fR(1M). +\fBshare_nfs\fR(8), but not by \fBmount_nfs\fR(8) or \fBautomount\fR(8). .RE .SH FILES @@ -132,10 +132,10 @@ anonymous user. The \fBNFS\fR security mode \fBnone\fR is supported by .SH SEE ALSO .LP -\fBautomount\fR(1M), \fBkclient\fR(1M), \fBmount_nfs\fR(1M), -\fBshare_nfs\fR(1M), \fBrpc_clnt_auth\fR(3NSL), \fBsecure_rpc\fR(3NSL), -\fBnfssec.conf\fR(4), \fBattributes\fR(5), \fBkerberos\fR(5) +\fBautomount\fR(8), \fBkclient\fR(8), \fBmount_nfs\fR(8), +\fBshare_nfs\fR(8), \fBrpc_clnt_auth\fR(3NSL), \fBsecure_rpc\fR(3NSL), +\fBnfssec.conf\fR(5), \fBattributes\fR(7), \fBkerberos\fR(7) .SH NOTES .LP \fB/etc/nfssec.conf\fR lists the \fBNFS\fR security services. Do not edit this -file. It is not intended to be user-configurable. See \fBkclient\fR(1M). +file. It is not intended to be user-configurable. See \fBkclient\fR(8). diff --git a/usr/src/man/man7/pam_allow.7 b/usr/src/man/man7/pam_allow.7 index 8ce6607264..47259e5f3b 100644 --- a/usr/src/man/man7/pam_allow.7 +++ b/usr/src/man/man7/pam_allow.7 @@ -18,10 +18,10 @@ module to allow operations .LP The \fBpam_allow\fR module implements all the PAM service module functions and returns \fBPAM_SUCCESS\fR for all calls. Opposite functionality is available in -the \fBpam_deny\fR(5) module. +the \fBpam_deny\fR(7) module. .sp .LP -Proper Solaris authentication operation requires \fBpam_unix_cred\fR(5) be +Proper Solaris authentication operation requires \fBpam_unix_cred\fR(7) be stacked above \fBpam_allow\fR. .sp .LP @@ -77,7 +77,7 @@ gdm-autologin auth sufficient pam_allow.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 @@ -96,8 +96,8 @@ MT Level MT-Safe with exceptions .sp .LP \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), \fBpam_sm\fR(3PAM), \fBsyslog\fR(3C), -\fBpam.conf\fR(4), \fBattributes\fR(5), \fBpam_deny\fR(5), -\fBpam_unix_cred\fR(5) +\fBpam.conf\fR(5), \fBattributes\fR(7), \fBpam_deny\fR(7), +\fBpam_unix_cred\fR(7) .SH NOTES .sp .LP diff --git a/usr/src/man/man7/pam_authtok_check.7 b/usr/src/man/man7/pam_authtok_check.7 index fadc7dd9c4..6fc3161a41 100644 --- a/usr/src/man/man7/pam_authtok_check.7 +++ b/usr/src/man/man7/pam_authtok_check.7 @@ -85,7 +85,7 @@ The password must not be based on a dictionary word. The list of words to be used for the site's dictionary can be specified with \fBDICTIONLIST\fR. It should contain a comma-separated list of filenames, one word per line. The database that is created from these files is stored in the directory named by -\fBDICTIONDBDIR\fR (defaults to \fB/var/passwd\fR). See \fBmkpwdict\fR(1M) for +\fBDICTIONDBDIR\fR (defaults to \fB/var/passwd\fR). See \fBmkpwdict\fR(8) for information on pre-generating the database. If neither \fBDICTIONLIST\fR nor \fBDICTIONDBDIR\fR is specified, no dictionary check is made. .RE @@ -153,7 +153,7 @@ See \fBpasswd\fR(1) for a description of the contents. .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 @@ -171,12 +171,12 @@ MT Level MT-Safe with exceptions .SH SEE ALSO .sp .LP -\fBpasswd\fR(1), \fBpam\fR(3PAM), \fBmkpwdict\fR(1M), +\fBpasswd\fR(1), \fBpam\fR(3PAM), \fBmkpwdict\fR(8), \fBpam_chauthtok\fR(3PAM), \fBsyslog\fR(3C), \fBlibpam\fR(3LIB), -\fBpam.conf\fR(4), \fBpasswd\fR(4), \fBshadow\fR(4), \fBattributes\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), -\fBpam_unix_session\fR(5) +\fBpam.conf\fR(5), \fBpasswd\fR(5), \fBshadow\fR(5), \fBattributes\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), +\fBpam_unix_session\fR(7) .SH NOTES .sp .LP @@ -184,8 +184,8 @@ The interfaces in \fBlibpam\fR(3LIB) are MT-Safe only if each thread within the multi-threaded application uses its own \fBPAM\fR handle. .sp .LP -The \fBpam_unix\fR(5) 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). +The \fBpam_unix\fR(7) module is no longer supported. Similar functionality is +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). diff --git a/usr/src/man/man7/pam_authtok_get.7 b/usr/src/man/man7/pam_authtok_get.7 index ea9bf2f2a0..950f6ed495 100644 --- a/usr/src/man/man7/pam_authtok_get.7 +++ b/usr/src/man/man7/pam_authtok_get.7 @@ -105,7 +105,7 @@ Authentication token manipulation error .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 @@ -123,18 +123,18 @@ MT Level MT-Safe with exceptions .SH SEE ALSO .LP \fBpam\fR(3PAM), \fBpam_authenticate\fR(3PAM), \fBsyslog\fR(3C), -\fBlibpam\fR(3LIB), \fBpam.conf\fR(4), \fBattributes\fR(5), -\fBpam_authtok_check\fR(5), pam_authtok_get(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), \fBpam_unix_session\fR(5) +\fBlibpam\fR(3LIB), \fBpam.conf\fR(5), \fBattributes\fR(7), +\fBpam_authtok_check\fR(7), pam_authtok_get(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), \fBpam_unix_session\fR(7) .SH NOTES .LP The interfaces in \fBlibpam\fR(3LIB) are MT-Safe only if each thread within the multi-threaded application uses its own PAM handle. .sp .LP -The \fBpam_unix\fR(5) 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). +The \fBpam_unix\fR(7) module is no longer supported. Similar functionality is +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). diff --git a/usr/src/man/man7/pam_authtok_store.7 b/usr/src/man/man7/pam_authtok_store.7 index 93862db6ca..9755ee838a 100644 --- a/usr/src/man/man7/pam_authtok_store.7 +++ b/usr/src/man/man7/pam_authtok_store.7 @@ -32,7 +32,7 @@ the user's valid password. .LP This module honors the \fBPAM_REPOSITORY\fR item, which, if set, specifies which repository is to be updated. If \fBPAM_REPOSITORY\fR is unset, it follows -the \fBnsswitch.conf\fR(4). +the \fBnsswitch.conf\fR(5). .sp .LP The following option can be passed to the module: @@ -78,7 +78,7 @@ null or empty, or password null. .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 @@ -97,10 +97,10 @@ MT Level MT-Safe with exceptions .sp .LP \fBpam\fR(3PAM), \fBpam_authenticate\fR(3PAM), \fBpam_chauthtok\fR(3PAM), -\fBsyslog\fR(3C), \fBlibpam\fR(3LIB), \fBpam.conf\fR(4), \fBattributes\fR(5), -\fBpam_authtok_check\fR(5), \fBpam_authtok_get\fR(5), \fBpam_dhkeys\fR(5), -\fBpam_passwd_auth\fR(5), \fBpam_unix_account\fR(5), \fBpam_unix_auth\fR(5), -\fBpam_unix_session\fR(5) +\fBsyslog\fR(3C), \fBlibpam\fR(3LIB), \fBpam.conf\fR(5), \fBattributes\fR(7), +\fBpam_authtok_check\fR(7), \fBpam_authtok_get\fR(7), \fBpam_dhkeys\fR(7), +\fBpam_passwd_auth\fR(7), \fBpam_unix_account\fR(7), \fBpam_unix_auth\fR(7), +\fBpam_unix_session\fR(7) .SH NOTES .sp .LP @@ -108,11 +108,11 @@ The interfaces in \fBlibpam\fR(3LIB) are MT-Safe only if each thread within the multi-threaded application uses its own \fBPAM\fR handle. .sp .LP -The \fBpam_unix\fR(5) 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). +The \fBpam_unix\fR(7) module is no longer supported. Similar functionality is +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 If the \fBPAM_REPOSITORY\fR \fIitem_type\fR is set and a service module does diff --git a/usr/src/man/man7/pam_deny.7 b/usr/src/man/man7/pam_deny.7 index b7f118c235..93e5958b6a 100644 --- a/usr/src/man/man7/pam_deny.7 +++ b/usr/src/man/man7/pam_deny.7 @@ -110,7 +110,7 @@ If \fBpam_sm_open_session\fR or \fBpam_sm_close_session\fR is called. .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 @@ -128,12 +128,12 @@ MT Level MT-Safe with exceptions .SH SEE ALSO .sp .LP -\fBsu\fR(1M), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), -\fBpam_sm_authenticate\fR(3PAM), \fBsyslog\fR(3C), \fBpam.conf\fR(4), -\fBnsswitch.conf\fR(4), \fBattributes\fR(5), \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), -\fBpam_unix_session\fR(5), \fBprivileges\fR(5) +\fBsu\fR(8), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), +\fBpam_sm_authenticate\fR(3PAM), \fBsyslog\fR(3C), \fBpam.conf\fR(5), +\fBnsswitch.conf\fR(5), \fBattributes\fR(7), \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), +\fBpam_unix_session\fR(7), \fBprivileges\fR(7) .SH NOTES .sp .LP diff --git a/usr/src/man/man7/pam_dhkeys.7 b/usr/src/man/man7/pam_dhkeys.7 index be8053e669..7653bab818 100644 --- a/usr/src/man/man7/pam_dhkeys.7 +++ b/usr/src/man/man7/pam_dhkeys.7 @@ -167,7 +167,7 @@ Module ran out of memory. .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 @@ -188,17 +188,17 @@ MT Level MT-Safe with exceptions \fBpam_authenticate\fR(3PAM), \fBpam_chauthtok\fR(3PAM), \fBpam_setcred\fR(3PAM), \fBpam_get_item\fR(3PAM), \fBpam_set_data\fR(3PAM), \fBpam_get_data\fR(3PAM), \fBsyslog\fR(3C), \fBlibpam\fR(3LIB), -\fBpam.conf\fR(4), \fBattributes\fR(5), \fBpam_authtok_check\fR(5), -\fBpam_authtok_get\fR(5), \fBpam_authtok_store\fR(5), \fBpam_passwd_auth\fR(5), -\fBpam_unix_account\fR(5), \fBpam_unix_auth\fR(5), \fBpam_unix_session\fR(5) +\fBpam.conf\fR(5), \fBattributes\fR(7), \fBpam_authtok_check\fR(7), +\fBpam_authtok_get\fR(7), \fBpam_authtok_store\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 interfaces in \fBlibpam\fR(3LIB) are MT-Safe only if each thread within the multi-threaded application uses its own PAM handle. .sp .LP -The \fBpam_unix\fR(5) 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). +The \fBpam_unix\fR(7) module is no longer supported. Similar functionality is +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). diff --git a/usr/src/man/man7/pam_dial_auth.7 b/usr/src/man/man7/pam_dial_auth.7 index 90c999b867..d870e9a162 100644 --- a/usr/src/man/man7/pam_dial_auth.7 +++ b/usr/src/man/man7/pam_dial_auth.7 @@ -17,7 +17,7 @@ pam_dial_auth \- authentication management PAM module for dialups .sp .LP The \fBpam_dial_auth\fR module implements \fBpam_sm_authenticate\fR(3PAM) which -authenticates the user according to the \fBdialups\fR(4) and \fBd_passwd\fR(4) +authenticates the user according to the \fBdialups\fR(5) and \fBd_passwd\fR(5) files configuration. .sp .LP @@ -27,8 +27,8 @@ returns \fBPAM_IGNORE\fR. .sp .LP The value of the \fBPAM_TTY\fR item is checked against entries in -\fBdialups\fR(4). If there is a match, the user's shell is compared against -entries in \fBd_passwd\fR(4). If there is a matching entry, the user is +\fBdialups\fR(5). If there is a match, the user's shell is compared against +entries in \fBd_passwd\fR(5). If there is a matching entry, the user is prompted for a password which is validated against the entry found. .sp .LP @@ -45,7 +45,7 @@ The following option may be passed in to this service module: .SH ERRORS .sp .LP -If \fBdialups\fR(4) is not present, \fBPAM_IGNORE\fR is returned. Upon +If \fBdialups\fR(5) is not present, \fBPAM_IGNORE\fR is returned. Upon successful completion of \fBpam_sm_authenticate()\fR, \fBPAM_SUCCESS\fR is returned. The following error codes are returned upon error: .sp @@ -72,7 +72,7 @@ Error in the calling service, \fBPAM_TTY\fR is not set. \fB\fBPAM_SYSTEM_ERR\fR\fR .ad .RS 20n -System error (\fBd_passwd\fR(4) is not present). +System error (\fBd_passwd\fR(5) is not present). .RE .sp @@ -87,7 +87,7 @@ No account is present for \fIuser\fR. .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 @@ -104,10 +104,10 @@ MT Level MT-Safe with exceptions .sp .LP \fBpam\fR(3PAM), \fBpam_authenticate\fR(3PAM), \fBpam_sm_authenticate\fR(3PAM), -\fBd_passwd\fR(4), \fBdialups\fR(4), \fBlibpam\fR(3LIB), \fBpam.conf\fR(4), -\fBattributes\fR(5), \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), \fBpam_unix_session\fR(5) +\fBd_passwd\fR(5), \fBdialups\fR(5), \fBlibpam\fR(3LIB), \fBpam.conf\fR(5), +\fBattributes\fR(7), \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), \fBpam_unix_session\fR(7) .SH NOTES .sp .LP @@ -115,8 +115,8 @@ The interfaces in \fBlibpam\fR(3LIB) are MT-Safe only if each thread within the multi-threaded application uses its own \fBPAM\fR handle. .sp .LP -The \fBpam_unix\fR(5) 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). +The \fBpam_unix\fR(7) module is no longer supported. Similar functionality is +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). diff --git a/usr/src/man/man7/pam_krb5.7 b/usr/src/man/man7/pam_krb5.7 index ddfa2c7d85..835e875fcd 100644 --- a/usr/src/man/man7/pam_krb5.7 +++ b/usr/src/man/man7/pam_krb5.7 @@ -42,7 +42,7 @@ default realm of the local host as defined in \fB/etc/krb5/krb5.conf\fR. If the host entry is not found in the keytab file, the authentication fails. Administrators may optionally disable this "strict" verification by setting "\fBverify_ap_req_nofail = false\fR" in \fB/etc/krb5/krb5.conf\fR. See -\fBkrb5.conf\fR(4) for more details on this option. This allows \fBTGT\fR +\fBkrb5.conf\fR(5) for more details on this option. This allows \fBTGT\fR verification to succeed in the absence of a keytab host principal entry. .sp .LP @@ -667,7 +667,7 @@ Non-Kerberos users should specify their respective repositories by using the .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 @@ -684,11 +684,11 @@ Interface Stability Evolving .sp .LP \fBkdestroy\fR(1), \fBkinit\fR(1), \fBkpasswd\fR(1), \fBpasswd\fR(1), -\fBktkt_warnd\fR(1M), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), \fBpam_sm\fR(3PAM), +\fBktkt_warnd\fR(8), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), \fBpam_sm\fR(3PAM), \fBpam_sm_acct_mgmt\fR(3PAM), \fBpam_sm_authenticate\fR(3PAM), \fBpam_sm_chauthtok\fR(3PAM), \fBpam_sm_close_session\fR(3PAM), \fBpam_sm_open_session\fR(3PAM), \fBpam_sm_setcred\fR(3PAM), \fBsyslog\fR(3C), -\fBpam.conf\fR(4), \fBattributes\fR(5), \fBkerberos\fR(5), \fBkrb5envvar\fR(5) +\fBpam.conf\fR(5), \fBattributes\fR(7), \fBkerberos\fR(7), \fBkrb5envvar\fR(7) .SH NOTES .sp .LP @@ -697,5 +697,5 @@ multi-threaded application uses its own \fBPAM\fR handle. .sp .LP On successful acquisition of initial credentials (ticket-granting ticket), -\fBktkt_warnd\fR(1M) will be notified, to alert the user when the initial +\fBktkt_warnd\fR(8) will be notified, to alert the user when the initial credentials are about to expire. diff --git a/usr/src/man/man7/pam_krb5_migrate.7 b/usr/src/man/man7/pam_krb5_migrate.7 index 0f6f83cfe4..426b12ece8 100644 --- a/usr/src/man/man7/pam_krb5_migrate.7 +++ b/usr/src/man/man7/pam_krb5_migrate.7 @@ -27,11 +27,11 @@ client. .LP \fBpam_sm_authenticate\fR(3PAM) uses a host-based client service principal, present in the local \fBkeytab\fR (\fB/etc/krb5/krb5.keytab\fR) to authenticate -to \fBkadmind\fR(1M) (defaults to the \fBhost/nodename.fqdn\fR service +to \fBkadmind\fR(8) (defaults to the \fBhost/nodename.fqdn\fR service principal), for the principal creation operation. Also, for successful creation of the \fBkrb5\fR user principal account, the host-based client service principal being used needs to be assigned the appropriate privilege on the -master KDC's \fBkadm5.acl\fR(4) file. \fBkadmind\fR(1M) checks for the +master KDC's \fBkadm5.acl\fR(5) file. \fBkadmind\fR(8) checks for the appropriate privilege and validates the user password using PAM by calling \fBpam_authenticate\fR(3PAM) and \fBpam_acct_mgmt\fR(3PAM) for the \fBk5migrate\fR service. @@ -44,9 +44,9 @@ unless instructed otherwise by the presence of the \fBquiet\fR option. .LP The authentication component always returns \fBPAM_IGNORE\fR and is meant to be stacked in \fBpam.conf\fR with a requirement that it be listed below -pam_authtok_get(5) in the authentication stack. Also, if \fBpam_krb5_migrate\fR +pam_authtok_get(7) in the authentication stack. Also, if \fBpam_krb5_migrate\fR is used in the authentication stack of a particular service, it is mandatory -that \fBpam_krb5\fR(5) be listed in the PAM account stack of that service for +that \fBpam_krb5\fR(7) be listed in the PAM account stack of that service for proper operation (see EXAMPLES). .SH OPTIONS The following options can be passed to the KerberosV5 auto-migrate @@ -68,7 +68,7 @@ Provides \fBsyslog\fR(3C) debugging information at \fBLOG_DEBUG\fR level. .ad .sp .6 .RS 4n -Name of the service used to authenticate to \fBkadmind\fR(1M) defaults to +Name of the service used to authenticate to \fBkadmind\fR(8) defaults to \fBhost\fR. This means that the module uses \fBhost/\fR\fI<nodename.fqdn>\fR as its client service principal name, KerberosV5 user principal creation operation or \fI<service>\fR/\fI<nodename.fqdn>\fR if this option is provided. @@ -107,7 +107,7 @@ to \fBnow\fR (current time). \fBExample 1 \fRSample Entries from \fBpam.conf\fR .sp .LP -The following entries from \fBpam.conf\fR(4) demonstrate the use of the +The following entries from \fBpam.conf\fR(5) demonstrate the use of the \fBpam_krb5_migrate.so.1\fR module: .sp @@ -139,7 +139,7 @@ available for use as a Kerberos V5 password. \fBExample 2 \fRSample Entries from \fBkadm5.acl\fR .sp .LP -The following entries from \fBkadm5.acl\fR(4) permit or deny privileges to the +The following entries from \fBkadm5.acl\fR(5) permit or deny privileges to the host client service principal: .sp @@ -161,7 +161,7 @@ principals for addition of the root user account. \fBExample 3 \fRSample Entries in \fBpam.conf\fR of the Master KDC .sp .LP -The entries below enable \fBkadmind\fR(1M) on the master KDC to use the +The entries below enable \fBkadmind\fR(8) on the master KDC to use the \fBk5migrate\fR PAM service in order to validate Unix user passwords for accounts that require migration to the Kerberos realm. @@ -174,7 +174,7 @@ k5migrate account required pam_unix_account.so.1 .in -2 .SH ATTRIBUTES -See \fBattributes\fR(5) for a description of the following attribute: +See \fBattributes\fR(7) for a description of the following attribute: .sp .sp @@ -188,7 +188,7 @@ Interface Stability Evolving .TE .SH SEE ALSO -\fBkadmind\fR(1M), \fBsyslog\fR(3C), \fBpam_authenticate\fR(3PAM), -\fBpam_acct_mgmt\fR(3PAM), \fBpam_sm_authenticate\fR(3PAM), \fBkadm5.acl\fR(4), -\fBpam.conf\fR(4), \fBattributes\fR(5), \fBpam_authtok_get\fR(5), -\fBpam_krb5\fR(5) +\fBkadmind\fR(8), \fBsyslog\fR(3C), \fBpam_authenticate\fR(3PAM), +\fBpam_acct_mgmt\fR(3PAM), \fBpam_sm_authenticate\fR(3PAM), \fBkadm5.acl\fR(5), +\fBpam.conf\fR(5), \fBattributes\fR(7), \fBpam_authtok_get\fR(7), +\fBpam_krb5\fR(7) diff --git a/usr/src/man/man7/pam_ldap.7 b/usr/src/man/man7/pam_ldap.7 index 42bbc2caa0..45dc3a2d22 100644 --- a/usr/src/man/man7/pam_ldap.7 +++ b/usr/src/man/man7/pam_ldap.7 @@ -31,8 +31,8 @@ policy. .LP \fBpam_ldap\fR must be used in conjunction with the modules that support the UNIX authentication, password, and account management, which are -\fBpam_authtok_get\fR(5), \fBpam_passwd_auth\fR(5), \fBpam_unix_account\fR(5), -and \fBpam_unix_auth\fR(5). \fBpam_ldap\fR is designed to be stacked directly +\fBpam_authtok_get\fR(7), \fBpam_passwd_auth\fR(7), \fBpam_unix_account\fR(7), +and \fBpam_unix_auth\fR(7). \fBpam_ldap\fR is designed to be stacked directly below these modules. If other modules are designed to be stacked in this manner, the modules can be stacked below the \fBpam_ldap\fR module. The Examples section shows how the UNIX modules are stacked with \fBpam_ldap\fR. @@ -51,7 +51,7 @@ authenticated. See NOTES for information on password prompting. .sp .LP The authentication method used is either defined in the client profile , or the -authentication method is configured by using the \fBldapclient\fR(1M) command. +authentication method is configured by using the \fBldapclient\fR(8) command. To determine the authentication method to use, this module first attempts to use the authentication method that is defined, for service \fBpam_ldap\fR, for example, \fBserviceAuthenticationMethod:pam_ldap:sasl/DIGEST-MD5\fR. If no @@ -119,9 +119,9 @@ presented here. .SS "LDAP Password Management Module" .LP LDAP password management is no longer supported by \fBpam_ldap\fR. Use -\fBpam_authtok_store\fR(5) instead of \fBpam_ldap\fR for password change. -\fBpam_authtok_store\fR(5) handles both the local and LDAP accounts and updates -the passwords in all the repositories configured by \fBnsswitch.conf\fR(4). +\fBpam_authtok_store\fR(7) instead of \fBpam_ldap\fR for password change. +\fBpam_authtok_store\fR(7) handles both the local and LDAP accounts and updates +the passwords in all the repositories configured by \fBnsswitch.conf\fR(5). .SH ERRORS .LP The authentication service returns the following error codes: @@ -349,7 +349,7 @@ other password required pam_authtok_store.so.1 server_policy .ad .RS 30n The LDAP configuration files of the client. Do not manually modify these files, -as these files might not be human readable. Use \fBldapclient\fR(1M) to update +as these files might not be human readable. Use \fBldapclient\fR(8) to update these files. .RE @@ -364,7 +364,7 @@ PAM configuration 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 @@ -381,14 +381,14 @@ MT-Level MT-Safe with exceptions .SH SEE ALSO .LP -\fBldap\fR(1), \fBidsconfig\fR(1M), \fBldap_cachemgr\fR(1M), -\fBldapclient\fR(1M), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), +\fBldap\fR(1), \fBidsconfig\fR(8), \fBldap_cachemgr\fR(8), +\fBldapclient\fR(8), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), \fBpam_sm_acct_mgmt\fR(3PAM), \fBpam_sm_authenticate\fR(3PAM), \fBpam_sm_chauthtok\fR(3PAM), \fBpam_sm_close_session\fR(3PAM), \fBpam_sm_open_session\fR(3PAM), \fBpam_sm_setcred\fR(3PAM), \fBsyslog\fR(3C), -\fBpam.conf\fR(4), \fBattributes\fR(5), \fBpam_authtok_check\fR(5), -\fBpam_authtok_get\fR(5), \fBpam_authtok_store\fR(5), \fBpam_passwd_auth\fR(5), -\fBpam_unix_account\fR(5), \fBpam_unix_auth\fR(5) +\fBpam.conf\fR(5), \fBattributes\fR(7), \fBpam_authtok_check\fR(7), +\fBpam_authtok_get\fR(7), \fBpam_authtok_store\fR(7), \fBpam_passwd_auth\fR(7), +\fBpam_unix_account\fR(7), \fBpam_unix_auth\fR(7) .SH NOTES .LP The interfaces in \fBlibpam\fR(3LIB) are MT-Safe only if each thread within the @@ -397,10 +397,10 @@ multi-threaded application uses its own \fBPAM\fR handle. .LP The previously supported \fBuse_first_pass\fR and \fBtry_first_pass\fR options are obsolete in this version, are no longer needed, can safely be removed from -\fBpam.conf\fR(4), and are silently ignored. They might be removed in a future +\fBpam.conf\fR(5), and are silently ignored. They might be removed in a future release. Password prompting must be provided for by stacking -\fBpam_authtok_get\fR(5) before \fBpam_ldap\fR in the \fBauth\fR and -\fBpassword\fR module stacks and \fBpam_passwd_auth\fR(5) in the \fBpasswd\fR +\fBpam_authtok_get\fR(7) before \fBpam_ldap\fR in the \fBauth\fR and +\fBpassword\fR module stacks and \fBpam_passwd_auth\fR(7) in the \fBpasswd\fR service \fBauth\fR stack (as described in the EXAMPLES section). The previously supported password update function is replaced in this release by the previously recommended use of \fBpam_authtok_store\fR with the diff --git a/usr/src/man/man7/pam_list.7 b/usr/src/man/man7/pam_list.7 index c9a0a203eb..ccfe27b138 100644 --- a/usr/src/man/man7/pam_list.7 +++ b/usr/src/man/man7/pam_list.7 @@ -29,7 +29,7 @@ as returned by \fBgethostname\fR(3C) is used. .LP If neither of the \fBallow\fR, \fBdeny\fR, or \fBcompat\fR options are specified, the module will look for +/- entries in the local \fB/etc/passwd\fR -file. If this style is used, \fBnsswitch.conf\fR(4) must not be configured +file. If this style is used, \fBnsswitch.conf\fR(5) must not be configured with \fBcompat\fR for the \fBpasswd\fR database. If no relevant +/- entry exists for the user, \fBpam_list\fR is not participating in result. .sp @@ -143,7 +143,7 @@ The following error values are returned: \fB\fBPAM_SERVICE_ERR\fR\fR .ad .RS 20n -An invalid set of module options was given in the \fBpam.conf\fR(4) for this +An invalid set of module options was given in the \fBpam.conf\fR(5) for this module, or the \fBuser/netgroup\fR file could not be opened. .RE @@ -278,7 +278,7 @@ root .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 @@ -299,5 +299,5 @@ The interfaces in \fBlibpam\fR(3LIB) are MT-Safe only if each thread within the multithreaded application uses its own PAM handle. .SH SEE ALSO \fBpam\fR(3PAM), \fBpam_authenticate\fR(3PAM), \fBpam_sm_acct_mgmt\fR(3PAM), -\fBsyslog\fR(3C), \fBlibpam\fR(3LIB), \fBnsswitch.conf\fR(4), -\fBpam.conf\fR(4), \fBattributes\fR(5) +\fBsyslog\fR(3C), \fBlibpam\fR(3LIB), \fBnsswitch.conf\fR(5), +\fBpam.conf\fR(5), \fBattributes\fR(7) diff --git a/usr/src/man/man7/pam_passwd_auth.7 b/usr/src/man/man7/pam_passwd_auth.7 index 7c98c346aa..b1d6ea0c2b 100644 --- a/usr/src/man/man7/pam_passwd_auth.7 +++ b/usr/src/man/man7/pam_passwd_auth.7 @@ -102,7 +102,7 @@ System error .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 @@ -122,10 +122,10 @@ MT Level MT-Safe with exceptions .LP \fBpasswd\fR(1), \fBpam\fR(3PAM), \fBpam_authenticate\fR(3PAM), \fBpam_start\fR(3PAM), \fBpam_set_item\fR(3PAM), \fBsyslog\fR(3C), -\fBlibpam\fR(3LIB), \fBpam.conf\fR(4), \fBattributes\fR(5), -\fBpam_authtok_check\fR(5), \fBpam_authtok_get\fR(5), -\fBpam_authtok_store\fR(5), \fBpam_dhkeys\fR(5), \fBpam_unix_account\fR(5), -\fBpam_unix_auth\fR(5), \fBpam_unix_session\fR(5) +\fBlibpam\fR(3LIB), \fBpam.conf\fR(5), \fBattributes\fR(7), +\fBpam_authtok_check\fR(7), \fBpam_authtok_get\fR(7), +\fBpam_authtok_store\fR(7), \fBpam_dhkeys\fR(7), \fBpam_unix_account\fR(7), +\fBpam_unix_auth\fR(7), \fBpam_unix_session\fR(7) .SH NOTES .sp .LP @@ -138,8 +138,8 @@ only safe for MT-applications that don't change \fBUID\fRs during the call to \fBpam_authenticate\fR(3PAM). .sp .LP -The \fBpam_unix\fR(5) 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). +The \fBpam_unix\fR(7) module is no longer supported. Similar functionality is +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). diff --git a/usr/src/man/man7/pam_rhosts_auth.7 b/usr/src/man/man7/pam_rhosts_auth.7 index 32b5c61eef..aa9a23141b 100644 --- a/usr/src/man/man7/pam_rhosts_auth.7 +++ b/usr/src/man/man7/pam_rhosts_auth.7 @@ -42,7 +42,7 @@ service module: .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 @@ -59,7 +59,7 @@ MT Level MT-Safe with exceptions .sp .LP \fBpam\fR(3PAM), \fBpam_authenticate\fR(3PAM), \fBruserok\fR(3SOCKET), -\fBsyslog\fR(3C), \fBlibpam\fR(3LIB), \fBpam.conf\fR(4), \fBattributes\fR(5) +\fBsyslog\fR(3C), \fBlibpam\fR(3LIB), \fBpam.conf\fR(5), \fBattributes\fR(7) .SH NOTES .sp .LP diff --git a/usr/src/man/man7/pam_roles.7 b/usr/src/man/man7/pam_roles.7 index 36de37980e..1137ff4c59 100644 --- a/usr/src/man/man7/pam_roles.7 +++ b/usr/src/man/man7/pam_roles.7 @@ -17,7 +17,7 @@ pam_roles.so.1 .LP The \fBpam_roles\fR module implements \fBpam_sm_acct_mgmt\fR(3PAM). It provides functionality to verify that a user is authorized to assume a role. It also -prevents direct logins to a role. The \fBuser_attr\fR(4) database is used to +prevents direct logins to a role. The \fBuser_attr\fR(5) database is used to determine which users can assume which roles. .sp .LP @@ -29,7 +29,7 @@ calling service implies that the user is asserting a new identity. Notice that root can never have roles. .sp .LP -This module is generally stacked above the \fBpam_unix_account\fR(5) module. +This module is generally stacked above the \fBpam_unix_account\fR(7) module. .sp .LP The following options are interpreted: @@ -91,7 +91,7 @@ identity name in its list of roles. \fBExample 1 \fRUsing the \fBpam_roles.so.1\fR Module .sp .LP -The following are sample entries from \fBpam.conf\fR(4). These entries +The following are sample entries from \fBpam.conf\fR(5). These entries demonstrate the use of the \fBpam_roles.so.1\fR module: .sp @@ -124,7 +124,7 @@ protocol (such as \fBsshd\fR-hostbased). .sp .LP -The following is a sample entry for a \fBpam.conf\fR(4) file. It demonstrates +The following is a sample entry for a \fBpam.conf\fR(5) file. It demonstrates the use of \fBpam_roles\fR configuration for remote roles for the \fBsshd\fR-hostbased service. @@ -140,7 +140,7 @@ sshd-hostbased account required pam_unix_account .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 @@ -158,13 +158,13 @@ MT Level MT-Safe with exceptions .SH SEE ALSO .sp .LP -\fBroles\fR(1), \fBsshd\fR(1M), \fBsu\fR(1M), \fBlibpam\fR(3LIB), +\fBroles\fR(1), \fBsshd\fR(8), \fBsu\fR(8), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), \fBpam_acct_mgmt\fR(3PAM), \fBpam_setcred\fR(3PAM), \fBpam_set_item\fR(3PAM), \fBpam_sm_acct_mgmt\fR(3PAM), \fBsyslog\fR(3C), -\fBpam.conf\fR(4), \fBuser_attr\fR(4), \fBattributes\fR(5), -\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), \fBpam_unix_session\fR(5) +\fBpam.conf\fR(5), \fBuser_attr\fR(5), \fBattributes\fR(7), +\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), \fBpam_unix_session\fR(7) .SH NOTES .sp .LP diff --git a/usr/src/man/man7/pam_sample.7 b/usr/src/man/man7/pam_sample.7 index ef4efce261..8f9e3aea75 100644 --- a/usr/src/man/man7/pam_sample.7 +++ b/usr/src/man/man7/pam_sample.7 @@ -26,7 +26,7 @@ The SAMPLE authentication module provides functions to test the \fBPAM\fR framework functionality using the \fBpam_sm_authenticate\fR(3PAM) call. The SAMPLE module implementation of the \fBpam_sm_authenticate\fR(3PAM) function compares the user entered password with the password set in the -\fBpam.conf\fR(4) file, or the string "test" if a default test password has not +\fBpam.conf\fR(5) file, or the string "test" if a default test password has not been set. The following options can be passed in to the SAMPLE Authentication module: .sp @@ -169,7 +169,7 @@ return \fBPAM_SUCCESS.\fR .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for description of the following attributes: +See \fBattributes\fR(7) for description of the following attributes: .sp .sp @@ -187,8 +187,8 @@ MT Level MT-Safe with exceptions .LP \fBpam\fR(3PAM), \fBpam_sm_authenticate\fR(3PAM), \fBpam_sm_chauthtok\fR(3PAM), \fBpam_sm_close_session\fR(3PAM), \fBpam_sm_open_session\fR(3PAM), -\fBpam_sm_setcred\fR(3PAM), \fBlibpam\fR(3LIB), \fBpam.conf\fR(4), -\fBattributes\fR(5) +\fBpam_sm_setcred\fR(3PAM), \fBlibpam\fR(3LIB), \fBpam.conf\fR(5), +\fBattributes\fR(7) .SH WARNINGS .sp .LP diff --git a/usr/src/man/man7/pam_smb_passwd.7 b/usr/src/man/man7/pam_smb_passwd.7 index 940b440ed3..c35920dea5 100644 --- a/usr/src/man/man7/pam_smb_passwd.7 +++ b/usr/src/man/man7/pam_smb_passwd.7 @@ -151,7 +151,7 @@ User is unknown .SH ATTRIBUTES .sp .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 @@ -170,9 +170,9 @@ MT Level MT-Safe with exceptions .SH SEE ALSO .sp .LP -\fBsmbd\fR(1M), \fBsyslog\fR(3C), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), +\fBsmbd\fR(8), \fBsyslog\fR(3C), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), \fBpam_chauthtok\fR(3PAM), \fBpam_sm\fR(3PAM), \fBpam_sm_chauthtok\fR(3PAM), -\fBpam.conf\fR(4), \fBattributes\fR(5) +\fBpam.conf\fR(5), \fBattributes\fR(7) .SH NOTES .sp .LP diff --git a/usr/src/man/man7/pam_smbfs_login.7 b/usr/src/man/man7/pam_smbfs_login.7 index 8541729893..51b135857c 100644 --- a/usr/src/man/man7/pam_smbfs_login.7 +++ b/usr/src/man/man7/pam_smbfs_login.7 @@ -195,7 +195,7 @@ System error. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attribute: +See \fBattributes\fR(7) for descriptions of the following attribute: .sp .sp @@ -215,8 +215,8 @@ MT Level MT-Safe with exceptions .LP \fBsmbutil\fR(1), \fBsyslog\fR(3C), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), \fBpam_setcred\fR(3PAM), \fBpam_sm\fR(3PAM), \fBpam_sm_authenticate\fR(3PAM), -\fBpam_sm_chauthtok\fR(3PAM), \fBpam_sm_setcred\fR(3PAM), \fBpam.conf\fR(4), -\fBattributes\fR(5), \fBsmbfs\fR(7FS) +\fBpam_sm_chauthtok\fR(3PAM), \fBpam_sm_setcred\fR(3PAM), \fBpam.conf\fR(5), +\fBattributes\fR(7), \fBsmbfs\fR(4FS) .SH NOTES .sp .LP diff --git a/usr/src/man/man7/pam_tsol_account.7 b/usr/src/man/man7/pam_tsol_account.7 index e7aa5df7cb..db7ccad311 100644 --- a/usr/src/man/man7/pam_tsol_account.7 +++ b/usr/src/man/man7/pam_tsol_account.7 @@ -25,13 +25,13 @@ upon demand. Its path is specified in the \fBPAM\fR configuration file. \fBpam_tsol_account.so.1\fR contains a function to perform account management, \fBpam_sm_acct_mgmt()\fR. The function checks for the allowed label range for the user. The allowable label range is set by the defaults in the -\fBlabel_encodings\fR(4) file. These defaults can be overridden by entries in -the \fBuser_attr\fR(4) database. +\fBlabel_encodings\fR(5) file. These defaults can be overridden by entries in +the \fBuser_attr\fR(5) database. .sp .LP By default, this module requires that remote hosts connecting to the global zone must have a CIPSO host type. To disable this policy, add the -\fBallow_unlabeled\fR keyword as an option to the entry in \fBpam.conf\fR(4), +\fBallow_unlabeled\fR keyword as an option to the entry in \fBpam.conf\fR(5), as in: .sp .in +2 @@ -101,7 +101,7 @@ information on error-related return values, see the \fBpam\fR(3PAM) man page. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for description of the following attributes: +See \fBattributes\fR(7) for description of the following attributes: .sp .sp @@ -125,8 +125,8 @@ multi-threaded application uses its own PAM handle. .LP \fBkeylogin\fR(1), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), \fBpam_sm_acct_mgmt\fR(3PAM), \fBpam_start\fR(3PAM), \fBsyslog\fR(3C), -\fBlabel_encodings\fR(4), \fBpam.conf\fR(4), \fBuser_attr\fR(4), -\fBattributes\fR(5) +\fBlabel_encodings\fR(5), \fBpam.conf\fR(5), \fBuser_attr\fR(5), +\fBattributes\fR(7) .sp .LP Chapter 17, \fIUsing PAM,\fR in \fISystem Administration Guide: Security diff --git a/usr/src/man/man7/pam_unix_account.7 b/usr/src/man/man7/pam_unix_account.7 index fffa3c69b1..75845b64e8 100644 --- a/usr/src/man/man7/pam_unix_account.7 +++ b/usr/src/man/man7/pam_unix_account.7 @@ -20,7 +20,7 @@ pam_unix_account \- PAM account management module for UNIX provides functionality to the \fBPAM\fR account management stack. The module provides functions to validate that the user's account is not locked or expired and that the user's password does not need to be changed. The module retrieves -account information from the configured databases in \fBnsswitch.conf\fR(4). +account information from the configured databases in \fBnsswitch.conf\fR(5). .sp .LP The following options can be passed to the module: @@ -141,7 +141,7 @@ No account is present for the user .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 @@ -160,8 +160,8 @@ MT Level MT-Safe with exceptions .sp .LP \fBpam\fR(3PAM), \fBpam_authenticate\fR(3PAM), \fBsyslog\fR(3C), -\fBlibpam\fR(3LIB), \fBpam.conf\fR(4), \fBnsswitch.conf\fR(4), -\fBattributes\fR(5) +\fBlibpam\fR(3LIB), \fBpam.conf\fR(5), \fBnsswitch.conf\fR(5), +\fBattributes\fR(7) .SH NOTES .sp .LP diff --git a/usr/src/man/man7/pam_unix_auth.7 b/usr/src/man/man7/pam_unix_auth.7 index 73c8bc0a3e..2e5cc7db83 100644 --- a/usr/src/man/man7/pam_unix_auth.7 +++ b/usr/src/man/man7/pam_unix_auth.7 @@ -20,19 +20,19 @@ provides functionality to the PAM authentication stack. It provides functions that use \fBcrypt\fR(3C) to verify that the password contained in the \fBPAM\fR item \fBPAM_AUTHTOK\fR is the correct password for the user specified in the item \fBPAM_USER\fR. If \fBPAM_REPOSITORY\fR is specified, then user's password -is fetched from that repository. Otherwise, the default \fBnsswitch.conf\fR(4) +is fetched from that repository. Otherwise, the default \fBnsswitch.conf\fR(5) repository is searched for that user. .sp .LP For accounts in the name services which support automatic account locking, the -account may be configured to be automatically locked (see \fBuser_attr\fR(4) -and \fBpolicy.conf\fR(4)) after multiple failed login attempts. For accounts +account may be configured to be automatically locked (see \fBuser_attr\fR(5) +and \fBpolicy.conf\fR(5)) after multiple failed login attempts. For accounts that are configured for automatic locking, if authentication failure is to be returned, the failed login counter is incremented upon each failure. If the number of successive failures equals or exceeds \fBRETRIES\fR as defined in \fBlogin\fR(1), the account is locked and \fBPAM_MAXTRIES\fR is returned. -Currently, only the "files" repository (see \fBpasswd\fR(4) and -\fBshadow\fR(4)) supports automatic account locking. A successful +Currently, only the "files" repository (see \fBpasswd\fR(5) and +\fBshadow\fR(5)) supports automatic account locking. A successful authentication by this module clears the failed login counter and reports the number of failed attempts since the last successful authentication. .sp @@ -41,7 +41,7 @@ Authentication service modules must implement both \fBpam_sm_authenticate()\fR and \fBpam_sm_setcred()\fR. To allow the authentication portion of UNIX authentication to be replaced, \fBpam_sm_setcred()\fR in this module always returns \fBPAM_IGNORE\fR. This module should be stacked with -\fBpam_unix_cred\fR(5) to ensure a successful return from +\fBpam_unix_cred\fR(7) to ensure a successful return from \fBpam_setcred\fR(3PAM). .sp .LP @@ -180,7 +180,7 @@ Ignores this module regardless of the control flag. .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 @@ -198,14 +198,14 @@ MT Level MT-Safe with exceptions .SH SEE ALSO .sp .LP -\fBlogin\fR(1), \fBpasswd\fR(1), \fBuseradd\fR(1M), \fBusermod\fR(1M), -\fBroleadd\fR(1M), \fBrolemod\fR(1M), \fBcrypt\fR(3C), \fBlibpam\fR(3LIB), +\fBlogin\fR(1), \fBpasswd\fR(1), \fBuseradd\fR(8), \fBusermod\fR(8), +\fBroleadd\fR(8), \fBrolemod\fR(8), \fBcrypt\fR(3C), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), \fBpam_authenticate\fR(3PAM), \fBpam_setcred\fR(3PAM), -\fBsyslog\fR(3C), \fBpam.conf\fR(4), \fBpasswd\fR(4), \fBpolicy.conf\fR(4), -\fBnsswitch.conf\fR(4), \fBshadow\fR(4), \fBuser_attr\fR(4), -\fBattributes\fR(5), \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_session\fR(5) +\fBsyslog\fR(3C), \fBpam.conf\fR(5), \fBpasswd\fR(5), \fBpolicy.conf\fR(5), +\fBnsswitch.conf\fR(5), \fBshadow\fR(5), \fBuser_attr\fR(5), +\fBattributes\fR(7), \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_session\fR(7) .SH NOTES .sp .LP @@ -213,11 +213,11 @@ The interfaces in \fBlibpam\fR(3LIB) are MT-Safe only if each thread within the multi-threaded application uses its own \fBPAM\fR handle. .sp .LP -The \fBpam_unix\fR(5) 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_setcred\fR(3PAM), \fBpam_unix_account\fR(5), -\fBpam_unix_cred\fR(5), \fBpam_unix_session\fR(5). +The \fBpam_unix\fR(7) module is no longer supported. Similar functionality is +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_setcred\fR(3PAM), \fBpam_unix_account\fR(7), +\fBpam_unix_cred\fR(7), \fBpam_unix_session\fR(7). .sp .LP If the \fBPAM_REPOSITORY\fR \fIitem_type\fR is set and a service module does diff --git a/usr/src/man/man7/pam_unix_cred.7 b/usr/src/man/man7/pam_unix_cred.7 index 2642ff6e11..5c5bacbd2d 100644 --- a/usr/src/man/man7/pam_unix_cred.7 +++ b/usr/src/man/man7/pam_unix_cred.7 @@ -17,7 +17,7 @@ pam_unix_cred \- PAM user credential authentication module for UNIX .LP The \fBpam_unix_cred\fR module implements \fBpam_sm_setcred\fR(3PAM). It provides functions that establish user credential information. It is a module -separate from the \fBpam_unix_auth\fR(5) module to allow replacement of the +separate from the \fBpam_unix_auth\fR(7) module to allow replacement of the authentication functionality independently from the credential functionality. .sp .LP @@ -66,7 +66,7 @@ can be identified as trustworthy. If the audit context is already initialized, the \fBPAM_REINITIALIZE_CRED\fR flag merges the current audit context with that of the user specified in \fBPAM_USER\fR. \fBPAM_REINITIALIZE_CRED\fR is useful when a user is assuming a -new identity, as with \fBsu\fR(1M). +new identity, as with \fBsu\fR(8). .RE .sp @@ -174,7 +174,7 @@ Ignores this module regardless of the control flag .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 @@ -192,14 +192,14 @@ MT Level MT-Safe with exceptions .SH SEE ALSO .sp .LP -\fBssh\fR(1), \fBsu\fR(1M), \fBsettaskid\fR(2), \fBlibpam\fR(3LIB), +\fBssh\fR(1), \fBsu\fR(8), \fBsettaskid\fR(2), \fBlibpam\fR(3LIB), \fBgetprojent\fR(3PROJECT), \fBpam\fR(3PAM), \fBpam_set_item\fR(3PAM), \fBpam_sm_authenticate\fR(3PAM), \fBsyslog\fR(3C), -\fBsetproject\fR(3PROJECT), \fBpam.conf\fR(4), \fBnsswitch.conf\fR(4), -\fBproject\fR(4), \fBattributes\fR(5), \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_auth\fR(5), \fBpam_unix_account\fR(5), -\fBpam_unix_session\fR(5), \fBprivileges\fR(5) +\fBsetproject\fR(3PROJECT), \fBpam.conf\fR(5), \fBnsswitch.conf\fR(5), +\fBproject\fR(5), \fBattributes\fR(7), \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_auth\fR(7), \fBpam_unix_account\fR(7), +\fBpam_unix_session\fR(7), \fBprivileges\fR(7) .SH NOTES .sp .LP diff --git a/usr/src/man/man7/pam_unix_session.7 b/usr/src/man/man7/pam_unix_session.7 index 9c312fa4d9..2f07f08c56 100644 --- a/usr/src/man/man7/pam_unix_session.7 +++ b/usr/src/man/man7/pam_unix_session.7 @@ -23,7 +23,7 @@ and \fBpam_sm_close_session\fR(3PAM). .LP \fBpam_sm_open_session()\fR updates the \fB/var/adm/lastlog\fR file with the information contained in the \fBPAM_USER\fR, \fBPAM_TTY\fR, and -\fBPAM_RHOSTS\fR items. \fBpam_unix_account\fR(5) uses this account to +\fBPAM_RHOSTS\fR items. \fBpam_unix_account\fR(7) uses this account to determine the previous time the user logged in. .sp .LP @@ -76,7 +76,7 @@ No account is present for \fIuser\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 @@ -95,10 +95,10 @@ MT Level MT-Safe with exceptions .sp .LP \fBpam\fR(3PAM), \fBpam_authenticate\fR(3PAM), \fBsyslog\fR(3C), -\fBlibpam\fR(3LIB), \fBpam.conf\fR(4), \fBnsswitch.conf\fR(4), -\fBattributes\fR(5), \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) +\fBlibpam\fR(3LIB), \fBpam.conf\fR(5), \fBnsswitch.conf\fR(5), +\fBattributes\fR(7), \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) .SH NOTES .sp .LP @@ -106,8 +106,8 @@ The interfaces in \fBlibpam\fR(3LIB) are MT-Safe only if each thread within the multi-threaded application uses its own PAM handle. .sp .LP -The \fBpam_unix\fR(5) 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). +The \fBpam_unix\fR(7) module is no longer supported. Similar functionality is +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). diff --git a/usr/src/man/man7/pkcs11_kernel.7 b/usr/src/man/man7/pkcs11_kernel.7 index 479b1ba93f..d0f894904a 100644 --- a/usr/src/man/man7/pkcs11_kernel.7 +++ b/usr/src/man/man7/pkcs11_kernel.7 @@ -77,7 +77,7 @@ in the RSA PKCS#11 v2.20 specification. See http://www.rsasecurity.com. .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 @@ -97,8 +97,8 @@ T} .SH SEE ALSO .sp .LP -\fBcryptoadm\fR(1M), \fBrctladm\fR(1M), \fBlibpkcs11\fR(3LIB), -\fBattributes\fR(5), \fBpkcs11_softtoken\fR(5) +\fBcryptoadm\fR(8), \fBrctladm\fR(8), \fBlibpkcs11\fR(3LIB), +\fBattributes\fR(7), \fBpkcs11_softtoken\fR(7) .sp .LP RSA PKCS#11 v2.20 http://www.rsasecurity.com diff --git a/usr/src/man/man7/pkcs11_softtoken.7 b/usr/src/man/man7/pkcs11_softtoken.7 index bb174efd7d..018e622f2a 100644 --- a/usr/src/man/man7/pkcs11_softtoken.7 +++ b/usr/src/man/man7/pkcs11_softtoken.7 @@ -251,7 +251,7 @@ alternate token object store .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 @@ -273,8 +273,8 @@ Standard PKCS#11 v2.20 .SH SEE ALSO .sp .LP -\fBpktool\fR(1), \fBcryptoadm\fR(1M), \fBlibpkcs11\fR(3LIB), -\fBattributes\fR(5), \fBpkcs11_kernel\fR(5) +\fBpktool\fR(1), \fBcryptoadm\fR(8), \fBlibpkcs11\fR(3LIB), +\fBattributes\fR(7), \fBpkcs11_kernel\fR(7) .sp .LP RSA PKCS#11 v2.20 http://www.rsasecurity.com diff --git a/usr/src/man/man7/pkcs11_tpm.7 b/usr/src/man/man7/pkcs11_tpm.7 index 0cb6610549..c850393115 100644 --- a/usr/src/man/man7/pkcs11_tpm.7 +++ b/usr/src/man/man7/pkcs11_tpm.7 @@ -243,7 +243,7 @@ Alternate token object store. .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 @@ -266,8 +266,8 @@ Exceptions to MT-Safe attribute are documented in section 6.5.2 of RSA PKCS#11 v2.20. .SH SEE ALSO .LP -\fBpktool\fR(1), \fBcryptoadm\fR(1M), \fBlibpkcs11\fR(3LIB), -\fBattributes\fR(5) +\fBpktool\fR(1), \fBcryptoadm\fR(8), \fBlibpkcs11\fR(3LIB), +\fBattributes\fR(7) .sp .LP TCG Software Stack (TSS) Specifications: \fBhttps://www.trustedcomputinggroup.org/specs/TSS\fR (as of the date of publication) diff --git a/usr/src/man/man7/privileges.7 b/usr/src/man/man7/privileges.7 index dbdd6156ec..b86b11fcca 100644 --- a/usr/src/man/man7/privileges.7 +++ b/usr/src/man/man7/privileges.7 @@ -619,7 +619,7 @@ Allow a process to assign a new task ID to the calling process. .sp .6 .RS 4n Allow a process to trace or send signals to processes in other zones. See -\fBzones\fR(5). +\fBzones\fR(7). .RE .sp @@ -641,7 +641,7 @@ Allow a process to enable and disable and manage accounting through .sp .6 .RS 4n Allow a process to perform system administration tasks such as setting node and -domain name and managing \fBfmd\fR(1M) and \fBnscd\fR(1M). +domain name and managing \fBfmd\fR(8) and \fBnscd\fR(8). .RE .sp @@ -782,8 +782,8 @@ locking operations, bind to NFS reserved ports: ports 2049 (\fBnfs\fR) and port .ad .sp .6 .RS 4n -Allow a process to create, configure, and destroy PPP instances with pppd(1M) -\fBpppd\fR(1M) and control PPPoE plumbing with \fBsppptun\fR(1M)sppptun(1M). +Allow a process to create, configure, and destroy PPP instances with pppd(8) +\fBpppd\fR(8) and control PPPoE plumbing with \fBsppptun\fR(8). This privilege is granted by default to exclusive IP stack instance zones. .RE @@ -880,7 +880,7 @@ Extensions. .ad .sp .6 .RS 4n -Allows a process to manage virtualized environments such as \fBxVM\fR(5). +Allows a process to manage virtualized environments such as \fBxVM\fR(7). .RE .sp @@ -1076,7 +1076,7 @@ Extensions. .ad .sp .6 .RS 4n -Allows a process access to the \fBxVM\fR(5) control devices for managing guest +Allows a process access to the \fBxVM\fR(7) control devices for managing guest domains and the hypervisor. This privilege is used only if booted into xVM on x86 platforms. .RE @@ -1306,7 +1306,7 @@ called \fBprivilege debugging\fR. When privilege debugging is enabled for a process, the kernel reports missing privileges on the controlling terminal of the process. (Enable debugging for a process with the \fB-D\fR option of \fBppriv\fR(1).) Additionally, the administrator can enable system-wide -privilege debugging by setting the \fBsystem\fR(4) variable \fBpriv_debug\fR +privilege debugging by setting the \fBsystem\fR(5) variable \fBpriv_debug\fR using: .sp .in +2 @@ -1319,14 +1319,14 @@ set priv_debug = 1 .LP On a running system, you can use \fBmdb\fR(1) to change this variable. .SS "Privilege Administration" -Use \fBusermod\fR(1M) or \fBrolemod\fR(1M) +Use \fBusermod\fR(8) or \fBrolemod\fR(8) to assign privileges to or modify privileges for, respectively, a user or a role. Use \fBppriv\fR(1) to enumerate the privileges supported on a system and \fBtruss\fR(1) to determine which privileges a program requires. .SH SEE ALSO -\fBmdb\fR(1), \fBppriv\fR(1), \fBadd_drv\fR(1M), \fBifconfig\fR(1M), -\fBlockd\fR(1M), \fBnfsd\fR(1M), \fBpppd\fR(1M), \fBrem_drv\fR(1M), -\fBsmbd\fR(1M), \fBsppptun\fR(1M), \fBupdate_drv\fR(1M), \fBIntro\fR(2), +\fBmdb\fR(1), \fBppriv\fR(1), \fBadd_drv\fR(8), \fBifconfig\fR(8), +\fBlockd\fR(8), \fBnfsd\fR(8), \fBpppd\fR(8), \fBrem_drv\fR(8), +\fBsmbd\fR(8), \fBsppptun\fR(8), \fBupdate_drv\fR(8), \fBIntro\fR(2), \fBaccess\fR(2), \fBacct\fR(2), \fBacl\fR(2), \fBadjtime\fR(2), \fBaudit\fR(2), \fBauditon\fR(2), \fBchmod\fR(2), \fBchown\fR(2), \fBchroot\fR(2), \fBcreat\fR(2), \fBexec\fR(2), \fBfcntl\fR(2), \fBfork\fR(2), @@ -1347,8 +1347,8 @@ role. Use \fBppriv\fR(1) to enumerate the privileges supported on a system and \fBpriv_addset\fR(3C), \fBpriv_set\fR(3C), \fBpriv_getbyname\fR(3C), \fBpriv_getbynum\fR(3C), \fBpriv_set_to_str\fR(3C), \fBpriv_str_to_set\fR(3C), \fBsocket\fR(3SOCKET), \fBt_bind\fR(3NSL), \fBtimer_create\fR(3C), -\fBucred_get\fR(3C), \fBexec_attr\fR(4), \fBproc\fR(4), \fBsystem\fR(4), -\fBuser_attr\fR(4), \fBxVM\fR(5), \fBddi_cred\fR(9F), \fBdrv_priv\fR(9F), +\fBucred_get\fR(3C), \fBexec_attr\fR(5), \fBproc\fR(5), \fBsystem\fR(5), +\fBuser_attr\fR(5), \fBxVM\fR(7), \fBddi_cred\fR(9F), \fBdrv_priv\fR(9F), \fBpriv_getbyname\fR(9F), \fBpriv_policy\fR(9F), \fBpriv_policy_choice\fR(9F), \fBpriv_policy_only\fR(9F) .sp diff --git a/usr/src/man/man7/rbac.7 b/usr/src/man/man7/rbac.7 index 96cd97a2c7..42dec22c6c 100644 --- a/usr/src/man/man7/rbac.7 +++ b/usr/src/man/man7/rbac.7 @@ -41,7 +41,7 @@ how to code for them. .LP An authorization is a unique string that represents a user's right to perform some operation or class of operations. Authorization definitions are stored in -a database called \fBauth_attr\fR(4). For programming authorization checks, +a database called \fBauth_attr\fR(5). For programming authorization checks, only the authorization name is significant. .sp .LP @@ -77,8 +77,8 @@ int chkauthattr(const char *authname, const char *username); .sp .LP -The \fBchkauthattr()\fR function checks the \fBpolicy.conf\fR(4), -\fBuser_attr\fR(4), and \fBprof_attr\fR(4) databases in order for a match to +The \fBchkauthattr()\fR function checks the \fBpolicy.conf\fR(5), +\fBuser_attr\fR(5), and \fBprof_attr\fR(5) databases in order for a match to the given authorization. .sp .LP @@ -231,8 +231,8 @@ fi .SH SEE ALSO .sp .LP -\fBld.so.1\fR(1), \fBchkauthattr\fR(3SECDB), \fBauth_attr\fR(4), -\fBpolicy.conf\fR(4), \fBprof_attr\fR(4), \fBuser_attr\fR(4) +\fBld.so.1\fR(1), \fBchkauthattr\fR(3SECDB), \fBauth_attr\fR(5), +\fBpolicy.conf\fR(5), \fBprof_attr\fR(5), \fBuser_attr\fR(5) .sp .LP \fISystem Administration Guide: Security Services\fR diff --git a/usr/src/man/man7/regexp.7 b/usr/src/man/man7/regexp.7 index 83d1270c9b..7018b96636 100644 --- a/usr/src/man/man7/regexp.7 +++ b/usr/src/man/man7/regexp.7 @@ -81,7 +81,7 @@ extern char *\fIloc1\fR, *\fIloc2\fR, *\fIlocs\fR; Regular Expressions (REs) provide a mechanism to select specific strings from a set of character strings. The Simple Regular Expressions described below differ from the Internationalized Regular Expressions described on the -\fBregex\fR(5) manual page in the following ways: +\fBregex\fR(7) manual page in the following ways: .RS +4 .TP .ie t \(bu @@ -747,4 +747,4 @@ regular expression overflow. .SH SEE ALSO .sp .LP -\fBregex\fR(5) +\fBregex\fR(7) diff --git a/usr/src/man/man7/resource_controls.7 b/usr/src/man/man7/resource_controls.7 index 714998ed76..389c99fd1e 100644 --- a/usr/src/man/man7/resource_controls.7 +++ b/usr/src/man/man7/resource_controls.7 @@ -9,7 +9,7 @@ resource_controls \- resource controls available through project database .SH DESCRIPTION The resource controls facility is configured through the project database. See -\fBproject\fR(4). You can set and modify resource controls through the +\fBproject\fR(5). You can set and modify resource controls through the following utilities: .RS +4 .TP @@ -21,19 +21,19 @@ following utilities: .TP .ie t \(bu .el o -\fBprojadd\fR(1M) +\fBprojadd\fR(8) .RE .RS +4 .TP .ie t \(bu .el o -\fBprojmod\fR(1M) +\fBprojmod\fR(8) .RE .RS +4 .TP .ie t \(bu .el o -\fBrctladm\fR(1M) +\fBrctladm\fR(8) .RE .sp .LP @@ -41,7 +41,7 @@ In a program, you use \fBsetrctl\fR(2) to set resource control values. .sp .LP In addition to the preceding resource controls, there are resource pools, -accessible through the \fBpooladm\fR(1M) and \fBpoolcfg\fR(1M) utilities. In a +accessible through the \fBpooladm\fR(8) and \fBpoolcfg\fR(8) utilities. In a program, resource pools can be manipulated through the \fBlibpool\fR(3LIB) library. .sp @@ -225,7 +225,7 @@ action. .sp .6 .RS 4n Number of CPU shares granted to a project for use with the fair share scheduler -(see \fBFSS\fR(7)). The unit used is the number of shares (an integer). This +(see \fBFSS\fR(4)). The unit used is the number of shares (an integer). This resource control does not support the \fBsyslog\fR action. .RE @@ -524,7 +524,7 @@ mappings and \fBtmpfs\fR mounts for this zone. .sp .LP -See \fBzones\fR(5). +See \fBzones\fR(7). .SS "Units Used in Resource Controls" Resource controls can be expressed as in units of size (bytes), time (seconds), or as a count (integer). These units use the strings specified below. @@ -607,7 +607,7 @@ The preceding examples use the scaling factors specified in the table above. .sp .LP Note that unit modifiers (for example, \fB5G\fR) are accepted by the -\fBprctl\fR(1), \fBprojadd\fR(1M), and \fBprojmod\fR(1M) commands. You cannot +\fBprctl\fR(1), \fBprojadd\fR(8), and \fBprojmod\fR(8) commands. You cannot use unit modifiers in the project database itself. .SS "Resource Control Values and Privilege Levels" A threshold value on a resource control constitutes a point at which local @@ -682,7 +682,7 @@ local. .sp .LP Global actions apply to resource control values for every resource control on -the system. You can use \fBrctladm\fR(1M) to perform the following actions: +the system. You can use \fBrctladm\fR(8) to perform the following actions: .RS +4 .TP .ie t \(bu @@ -809,7 +809,7 @@ it is a member. Therefore, a deny action is not allowed on the .LP Due to implementation restrictions, the global properties of each control can restrict the range of available actions that can be set on the threshold value. -(See \fBrctladm\fR(1M).) A list of available signal actions is presented in the +(See \fBrctladm\fR(8).) A list of available signal actions is presented in the following list. For additional information about signals, see \fBsignal\fR(3HEAD). .sp @@ -904,7 +904,7 @@ controls with the \fBRCTL_GLOBAL_CPUTIME\fR property Each resource control on the system has a certain set of associated properties. This set of properties is defined as a set of flags, which are associated with all controlled instances of that resource. Global flags cannot be modified, but -the flags can be retrieved by using either \fBrctladm\fR(1M) or the +the flags can be retrieved by using either \fBrctladm\fR(8) or the \fBsetrctl\fR(2) system call. .sp .LP @@ -1011,7 +1011,7 @@ container's control is enforced first. Thus, action is taken on \fBprocess.max-cpu-time\fR before \fBtask.max-cpu-time\fR if both controls are encountered simultaneously. .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 @@ -1025,10 +1025,10 @@ Interface Stability Evolving .TE .SH SEE ALSO -\fBprctl\fR(1), \fBpooladm\fR(1M), \fBpoolcfg\fR(1M), \fBprojadd\fR(1M), -\fBprojmod\fR(1M), \fBrctladm\fR(1M), \fBsetrctl\fR(2), -\fBrctlblk_set_value\fR(3C), \fBlibpool\fR(3LIB), \fBproject\fR(4), -\fBattributes\fR(5), \fBFSS\fR(7) +\fBprctl\fR(1), \fBpooladm\fR(8), \fBpoolcfg\fR(8), \fBprojadd\fR(8), +\fBprojmod\fR(8), \fBrctladm\fR(8), \fBsetrctl\fR(2), +\fBrctlblk_set_value\fR(3C), \fBlibpool\fR(3LIB), \fBproject\fR(5), +\fBattributes\fR(7), \fBFSS\fR(4) .sp .LP \fISystem Administration Guide: Virtualization Using the Solaris Operating diff --git a/usr/src/man/man7/smf.7 b/usr/src/man/man7/smf.7 index 30a5389c7d..57e88089ea 100644 --- a/usr/src/man/man7/smf.7 +++ b/usr/src/man/man7/smf.7 @@ -24,7 +24,7 @@ scope. .sp .LP Each service instance is named with a fault management resource identifier -(FMRI) with the scheme \fBsvc:\fR. For example, the \fBsyslogd\fR(1M) daemon +(FMRI) with the scheme \fBsvc:\fR. For example, the \fBsyslogd\fR(8) daemon started at system startup is the default service instance named: .sp .in +2 @@ -49,7 +49,7 @@ a category beginning with 'site'. .sp .LP A service instance is either enabled or disabled. All services can be enabled -or disabled with the \fBsvcadm\fR(1M) command. +or disabled with the \fBsvcadm\fR(8) command. .sp .LP The list of managed service instances on a system can be displayed with the @@ -134,45 +134,45 @@ started and the \fBrestart_on\fR attribute is not \fBnone\fR. .sp .LP The dependencies on a service can be listed with \fBsvcs\fR(1)\ or -\fBsvccfg\fR(1M), and modified with \fBsvccfg\fR(1M). +\fBsvccfg\fR(8), and modified with \fBsvccfg\fR(8). .SS "Restarters" .sp .LP Each service is managed by a restarter. The master restarter, -\fBsvc.startd\fR(1M) manages states for the entire set of service instances and +\fBsvc.startd\fR(8) manages states for the entire set of service instances and their dependencies. The master restarter acts on behalf of its services and on delegated restarters that can provide specific execution environments for -certain application classes. For instance, \fBinetd\fR(1M) is a delegated +certain application classes. For instance, \fBinetd\fR(8) is a delegated restarter that provides its service instances with an initial environment composed of a network connection as input and output file descriptors. Each -instance delegated to \fBinetd\fR(1M) is in the online state. While the daemon +instance delegated to \fBinetd\fR(8) is in the online state. While the daemon of a particular instance might not be running, the instance is available to run. .sp .LP As dependencies are satisfied when instances move to the online state, -\fBsvc.startd\fR(1M) invokes start methods of other instances or directs the +\fBsvc.startd\fR(8) invokes start methods of other instances or directs the delegated restarter to do so. These operations might overlap. .sp .LP The current set of services and associated restarters can be examined using \fBsvcs\fR(1). A description of the common configuration used by all restarters -is given in \fBsmf_restarter\fR(5). +is given in \fBsmf_restarter\fR(7). .SS "Methods" .sp .LP Each service or service instance must define a set of methods that start, stop, -and, optionally, refresh the service. See \fBsmf_method\fR(5) for a more -complete description of the method conventions for \fBsvc.startd\fR(1M) and +and, optionally, refresh the service. See \fBsmf_method\fR(7) for a more +complete description of the method conventions for \fBsvc.startd\fR(8) and similar \fBfork\fR(2)-\fBexec\fR(2) restarters. .sp .LP Administrative methods, such as for the capture of legacy configuration -information into the repository, are discussed on the \fBsvccfg\fR(1M) manual +information into the repository, are discussed on the \fBsvccfg\fR(8) manual page. .sp .LP -The methods for a service can be listed and modified using the \fBsvccfg\fR(1M) +The methods for a service can be listed and modified using the \fBsvccfg\fR(8) command. .SS "States" .sp @@ -188,7 +188,7 @@ contracts events. The following states are defined: .RS 17n This is the initial state for all service instances. Instances are moved to maintenance, offline, or a disabled state upon evaluation by -\fBsvc.startd\fR(1M) or the appropriate restarter. +\fBsvc.startd\fR(8) or the appropriate restarter. .RE .sp @@ -279,7 +279,7 @@ service instance. A service or service instance has an arbitrary number of property groups in which to store application data. Using property groups in this way allows the configuration of the application to derive the attributes that the repository provides for all data in the facility. The application can -also use the appropriate subset of the \fBservice_bundle\fR(4) DTD to represent +also use the appropriate subset of the \fBservice_bundle\fR(5) DTD to represent its configuration data within the framework. .sp .LP @@ -292,7 +292,7 @@ relationship between the service instance and its parent service. .sp .LP Properties are protected from modification by unauthorized processes. See -\fBsmf_security\fR(5). +\fBsmf_security\fR(7). .SS "General Property Group" .sp .LP @@ -343,7 +343,7 @@ during package installation. .ad .RS 15n Configuration as prescribed by the manifest of the service that is taken during -\fBsvccfg\fR(1M) import operation. This snapshot provides a baseline for +\fBsvccfg\fR(8) import operation. This snapshot provides a baseline for determining property customization. .RE @@ -377,7 +377,7 @@ Configuration captured during a successful transition to the online state. .sp .LP -The \fBsvccfg\fR(1M) command can be used to interact with snapshots. +The \fBsvccfg\fR(8) command can be used to interact with snapshots. .SS "Special Property Groups" .sp .LP @@ -390,13 +390,13 @@ system restart. .LP The current state of each service instance, as well as the properties associated with services and service instances, is stored in a system -repository managed by \fBsvc.configd\fR(1M). This repository is transactional +repository managed by \fBsvc.configd\fR(8). This repository is transactional and able to provide previous versions of properties and property groups associated with each service or service instance. .sp .LP The repository for service management facility data is managed by -\fBsvc.configd\fR(1M). +\fBsvc.configd\fR(8). .SS "Service Bundles, Manifests, and Profiles" .sp .LP @@ -430,7 +430,7 @@ instances. Template elements cannot be defined in a profile. .sp .LP Service bundles can be imported or exported from a repository using the -\fBsvccfg\fR(1M) command. See \fBservice_bundle\fR(4) for a description of the +\fBsvccfg\fR(8) command. See \fBservice_bundle\fR(5) for a description of the service bundle file format with guidelines for authoring service bundles. .sp .LP @@ -487,13 +487,13 @@ legacy-run state. .LP These instances do not have an enabled property (type \fBboolean\fR in the general property group) and, generally, cannot be manipulated with the -\fBsvcadm\fR(1M) command. No error diagnosis or restart is done for these +\fBsvcadm\fR(8) command. No error diagnosis or restart is done for these programs. .SH SEE ALSO .sp .LP -\fBsvcs\fR(1), \fBinetd\fR(1M), \fBsvcadm\fR(1M), \fBsvccfg\fR(1M), -\fBsvc.configd\fR(1M), \fBsvc.startd\fR(1M), \fBexec\fR(2), \fBfork\fR(2), -\fBlibscf\fR(3LIB), \fBstrftime\fR(3C), \fBcontract\fR(4), -\fBservice_bundle\fR(4), \fBsmf_bootstrap\fR(5), \fBsmf_method\fR(5), -\fBsmf_restarter\fR(5), \fBsmf_security\fR(5) +\fBsvcs\fR(1), \fBinetd\fR(8), \fBsvcadm\fR(8), \fBsvccfg\fR(8), +\fBsvc.configd\fR(8), \fBsvc.startd\fR(8), \fBexec\fR(2), \fBfork\fR(2), +\fBlibscf\fR(3LIB), \fBstrftime\fR(3C), \fBcontract\fR(5), +\fBservice_bundle\fR(5), \fBsmf_bootstrap\fR(7), \fBsmf_method\fR(7), +\fBsmf_restarter\fR(7), \fBsmf_security\fR(7) diff --git a/usr/src/man/man7/smf_bootstrap.7 b/usr/src/man/man7/smf_bootstrap.7 index 57af969a62..fa44f1ef9d 100644 --- a/usr/src/man/man7/smf_bootstrap.7 +++ b/usr/src/man/man7/smf_bootstrap.7 @@ -17,7 +17,7 @@ service profiles. .SS "Manifest Loading at Boot" .sp .LP -The \fBsvc:/system/manifest-import:default\fR service uses \fBsvccfg\fR(1M) to +The \fBsvc:/system/manifest-import:default\fR service uses \fBsvccfg\fR(8) to import certain manifest files from the \fB/var/svc/manifest\fR directory tree into the service configuration repository. The service imports files that it has not imported previously and those files which have changed since the last @@ -25,46 +25,46 @@ time they were imported by the service. When a manifest is imported by the service, a hash of the file that includes its contents is recorded in a property group of the \fBsvc:/smf/manifest\fR service. The \fBmanifest-import\fR service uses the hash to determine whether the file has -changed. See \fBsvccfg\fR(1M) for information on the \fBsvccfg import\fR +changed. See \fBsvccfg\fR(8) for information on the \fBsvccfg import\fR behavior for services that already exist in the repository. .SS "Manifest Handling During Packaging Operations" .sp .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. Instances in the manifest that are online or degraded are disabled first and then 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 will be done when the system is next rebooted with that alternate root path. .SS "Stability Declarations" .sp .LP Each service group and each property group delivered in a manifest should -declare a stability level based on \fBattributes\fR(5) definitions. With +declare a stability level based on \fBattributes\fR(7) definitions. With knowledge of the stability level, an application developer can determine the likelihood that feature development based on the existence or components of a service or object is likely to remain functional across a release boundary. .sp .LP -In an \fBsmf\fR(5) context, the stability value also identifies the expected +In an \fBsmf\fR(7) context, the stability value also identifies the expected scope of the changes to properties within the property group across a release boundary for the service, which can include patches for that service. The following two sections discuss this in more detail. .SS "Property Overrides" .sp .LP -The \fBservice_bundle\fR(4) document type definition includes an override +The \fBservice_bundle\fR(5) document type definition includes an override attribute that is applicable to each property in a service manifest. If set to -\fBtrue\fR, the attribute instructs \fBsvccfg\fR(1M) and other manifest import +\fBtrue\fR, the attribute instructs \fBsvccfg\fR(8) and other manifest import tools to replace the current value of a property in the repository with the one from the manifest. If the override attribute is absent or present but set to \fBfalse\fR, the current value in the repository is preserved. @@ -79,9 +79,9 @@ interface presented by the service. .SS "Property Group Deletion" .sp .LP -The \fBservice_bundle\fR(4) document type definition includes a delete +The \fBservice_bundle\fR(5) document type definition includes a delete attribute, applicable to each property group in a service manifest. If set to -\fBtrue\fR, the delete attribute instructs \fBsvccfg\fR(1M) and other manifest +\fBtrue\fR, the delete attribute instructs \fBsvccfg\fR(8) and other manifest import tools to delete this property group from the repository. If the delete attribute is absent or present but set to \fBfalse\fR, the property group in the repository is preserved. @@ -93,7 +93,7 @@ declared as Unstable can be deleted across any release boundary. .sp .LP The first time the existence of each of the three service profiles listed below -is detected, \fBsvc.startd\fR(1M) automatically applies the profile. +is detected, \fBsvc.startd\fR(8) automatically applies the profile. .sp .in +2 .nf @@ -111,14 +111,14 @@ The \fBsvc:/smf/manifest\fR service is used in a similar fashion. Additional service profiles that characterize the activation of various groups of service instances might be present in \fB/var/svc/profile\fR. None of the \fB/var/svc/profile\fR profiles are automatically applied to the repository. A -profile can be manually applied or re-applied using \fBsvccfg\fR(1M). +profile can be manually applied or re-applied using \fBsvccfg\fR(8). .SH SEE ALSO .sp .LP -\fBpkgadd\fR(1M), \fBpkgrm\fR(1M), \fBsvcadm\fR(1M), \fBsvccfg\fR(1M), -\fBsvc.startd\fR(1M), \fBlibscf\fR(3LIB), \fBservice_bundle\fR(4), -\fBattributes\fR(5), \fBsmf\fR(5), \fBsmf_security\fR(5) +\fBpkgadd\fR(8), \fBpkgrm\fR(8), \fBsvcadm\fR(8), \fBsvccfg\fR(8), +\fBsvc.startd\fR(8), \fBlibscf\fR(3LIB), \fBservice_bundle\fR(5), +\fBattributes\fR(7), \fBsmf\fR(7), \fBsmf_security\fR(7) .SH NOTES .sp .LP -The present version of \fBsmf\fR(5) does not support multiple repositories. +The present version of \fBsmf\fR(7) does not support multiple repositories. diff --git a/usr/src/man/man7/smf_method.7 b/usr/src/man/man7/smf_method.7 index 93ca3a6ece..4f11f0ecf7 100644 --- a/usr/src/man/man7/smf_method.7 +++ b/usr/src/man/man7/smf_method.7 @@ -9,11 +9,11 @@ smf_method \- service management framework conventions for methods .SH DESCRIPTION .LP -The class of services managed by \fBsvc.startd\fR(1M) in the service management -framework, \fBsmf\fR(5), consists of applications that fit a simple -\fBfork\fR(2)-\fBexec\fR(2) model. The \fBsvc.startd\fR(1M) master daemon and +The class of services managed by \fBsvc.startd\fR(8) in the service management +framework, \fBsmf\fR(7), consists of applications that fit a simple +\fBfork\fR(2)-\fBexec\fR(2) model. The \fBsvc.startd\fR(8) master daemon and other restarters support the \fBfork\fR(2)-\fBexec\fR(2) model, potentially -with additional capabilities. The \fBsvc.startd\fR(1M) daemon and other +with additional capabilities. The \fBsvc.startd\fR(8) daemon and other restarters require that the methods which activate, manipulate, or examine a service instance follow the conventions described in this manual page. .SS "Invocation form" @@ -34,7 +34,7 @@ form: .LP The \fIabbr_method_name\fR used for the recommended form is a supported method such as \fBstart\fR or \fBstop\fR. The set of methods supported by a restarter -is given on the related restarter page. The \fBsvc.startd\fR(1M) daemon +is given on the related restarter page. The \fBsvc.startd\fR(8) daemon supports \fBstart\fR, \fBstop\fR, and \fBrefresh\fR methods. .sp .LP @@ -141,7 +141,7 @@ the method. See the \fBMethod Context\fR section for more information. When defined in the \fBexec\fR string of the method by the restarter \fBsvc.startd\fR, a set of tokens are parsed and expanded with appropriate value. Other restarters might not support method tokens. The delegated -restarter for inet services, \fBinetd\fR(1M), does not support the following +restarter for inet services, \fBinetd\fR(8), does not support the following method expansions. .sp .ne 2 @@ -281,7 +281,7 @@ T} Unrecoverable configuration error. A common condition that returns this exit status is the absence of required configuration files for an enabled service instance. T} \fBSMF_EXIT_ERR_NOSMF\fR \fB99\fR T{ -Method has been mistakenly invoked outside the \fBsmf\fR(5) facility. Services that depend on \fBsmf\fR(5) capabilities should exit with this status value. +Method has been mistakenly invoked outside the \fBsmf\fR(7) facility. Services that depend on \fBsmf\fR(7) capabilities should exit with this status value. T} \fBSMF_EXIT_ERR_PERM\fR \fB100\fR T{ Method requires a form of permission such as file access, privilege, authorization, or other credential that is not available when invoked. @@ -322,7 +322,7 @@ suitable for inclusion via the source operator in any Bourne-compatible shell. .LP To assist in the composition of scripts that can serve as SMF methods as well as \fB/etc/init.d\fR scripts, the \fBsmf_present()\fR shell function is -provided. If the \fBsmf\fR(5) facility is not available, \fBsmf_present()\fR +provided. If the \fBsmf\fR(7) facility is not available, \fBsmf_present()\fR returns a non-zero exit status. .sp .LP @@ -388,7 +388,7 @@ of a number of \fBNAME=value\fR strings. .sp .6 .RS 4n The name of an RBAC (role-based access control) profile which, along with the -method executable, identifies an entry in \fBexec_attr\fR(4). +method executable, identifies an entry in \fBexec_attr\fR(5). .RE .sp @@ -430,7 +430,7 @@ numeric or text form. .sp .6 .RS 4n An optional string specifying the privilege set as defined in -\fBprivileges\fR(5). +\fBprivileges\fR(7). .RE .sp @@ -441,7 +441,7 @@ An optional string specifying the privilege set as defined in .sp .6 .RS 4n An optional string specifying the limit privilege set as defined in -\fBprivileges\fR(5). +\fBprivileges\fR(7). .RE .sp @@ -463,7 +463,7 @@ launch the method. If the property is unset, \fB:home\fR is used. .ad .sp .6 .RS 4n -The security flags to apply when launching the method. See \fBsecurity-flags\fR(5). +The security flags to apply when launching the method. See \fBsecurity-flags\fR(7). .sp .LP The "default" keyword specifies those flags specified in @@ -485,7 +485,7 @@ include further flags which may harm poorly implemented software. .sp .6 .RS 4n An optional string that specifies the corefile pattern to use for the service, -as per \fBcoreadm\fR(1M). Most restarters supply a default. Setting this +as per \fBcoreadm\fR(8). Most restarters supply a default. Setting this property overrides local customizations to the global core pattern. .RE @@ -509,7 +509,7 @@ whose \fBuid\fR is used to launch the method. .sp .6 .RS 4n The resource pool name on which to launch the method. \fB:default\fR can be -used as a token to indicate the pool specified in the \fBproject\fR(4) entry +used as a token to indicate the pool specified in the \fBproject\fR(5) entry given in the \fBproject\fR attribute above. .RE @@ -572,15 +572,15 @@ Definitions of exit status codes. .SH SEE ALSO .LP -\fBzonename\fR(1), \fBcoreadm\fR(1M), \fBinetd\fR(1M), \fBsvccfg\fR(1M), -\fBsvc.startd\fR(1M), \fBexec\fR(2), \fBfork\fR(2), -\fBgetdefaultproj\fR(3PROJECT), \fBexec_attr\fR(4), \fBproject\fR(4), -\fBservice_bundle\fR(4), \fBattributes\fR(5), \fBprivileges\fR(5), -\fBrbac\fR(5), \fBsmf\fR(5), \fBsmf_bootstrap\fR(5), \fBzones\fR(5), -\fBsecurity-flags\fR(5) +\fBzonename\fR(1), \fBcoreadm\fR(8), \fBinetd\fR(8), \fBsvccfg\fR(8), +\fBsvc.startd\fR(8), \fBexec\fR(2), \fBfork\fR(2), +\fBgetdefaultproj\fR(3PROJECT), \fBexec_attr\fR(5), \fBproject\fR(5), +\fBservice_bundle\fR(5), \fBattributes\fR(7), \fBprivileges\fR(7), +\fBrbac\fR(7), \fBsmf\fR(7), \fBsmf_bootstrap\fR(7), \fBzones\fR(7), +\fBsecurity-flags\fR(7) .SH NOTES .LP -The present version of \fBsmf\fR(5) does not support multiple repositories. +The present version of \fBsmf\fR(7) does not support multiple repositories. .sp .LP When a service is configured to be started as root but with privileges diff --git a/usr/src/man/man7/smf_restarter.7 b/usr/src/man/man7/smf_restarter.7 index d58db1ebca..3530faceb4 100644 --- a/usr/src/man/man7/smf_restarter.7 +++ b/usr/src/man/man7/smf_restarter.7 @@ -41,7 +41,7 @@ maintain availability of the service. .RS 19n This is an optional property that allows the specification of an alternate restarter to manage the service instance. If the restarter property is empty or -absent, the restarter defaults to \fBsvc.startd\fR(1M). +absent, the restarter defaults to \fBsvc.startd\fR(8). .RE .sp @@ -65,7 +65,7 @@ includes the following properties: .ad .RS 19n The current state and next state, if currently in transition, for instances -stored in these properties. See \fBsmf\fR(5) for a description of the potential +stored in these properties. See \fBsmf\fR(7) for a description of the potential states. .RE @@ -102,5 +102,5 @@ executing. .RE .SH SEE ALSO -\fBsvcs\fR(1), \fBsvc.startd\fR(1M), \fBservice_bundle\fR(4), \fBsmf\fR(5), -\fBsmf_method\fR(5) +\fBsvcs\fR(1), \fBsvc.startd\fR(8), \fBservice_bundle\fR(5), \fBsmf\fR(7), +\fBsmf_method\fR(7) diff --git a/usr/src/man/man7/smf_security.7 b/usr/src/man/man7/smf_security.7 index 8a3694144b..cc7c9ed907 100644 --- a/usr/src/man/man7/smf_security.7 +++ b/usr/src/man/man7/smf_security.7 @@ -8,10 +8,10 @@ smf_security \- service management facility security behavior .SH DESCRIPTION .LP -The configuration subsystem for the service management facility, \fBsmf\fR(5), +The configuration subsystem for the service management facility, \fBsmf\fR(7), requires privilege to modify the configuration of a service. Privileges are granted to a user by associating the authorizations described below to the user -through \fBuser_attr\fR(4) and \fBprof_attr\fR(4). See \fBrbac\fR(5). +through \fBuser_attr\fR(5) and \fBprof_attr\fR(5). See \fBrbac\fR(7). .sp .LP The following authorization is used to manipulate services and service @@ -28,11 +28,11 @@ properties, and to read protected property values. .SS "Property Group Authorizations" .LP -The \fBsmf\fR(5) configuration subsystem associates properties with each +The \fBsmf\fR(7) configuration subsystem associates properties with each service and service instance. Related properties are grouped. Groups can represent an execution method, credential information, application data, or restarter state. The ability to create or modify property groups can cause -\fBsmf\fR(5) components to perform actions that can require operating system +\fBsmf\fR(7) components to perform actions that can require operating system privilege. Accordingly, the framework requires appropriate authorization to manipulate property groups. .sp @@ -40,7 +40,7 @@ manipulate property groups. Each property group has a type corresponding to its purpose. The core property group types are \fBmethod\fR, \fBdependency\fR, \fBapplication\fR, and \fBframework\fR. Additional property group types can be introduced, provided -they conform to the extended naming convention in \fBsmf\fR(5). The following +they conform to the extended naming convention in \fBsmf\fR(7). The following basic authorizations, however, apply only to the core property group types: .sp .ne 2 @@ -155,7 +155,7 @@ is retrievable only as described in \fBProperty Group Authorizations\fR. Administrative domains with policies that prohibit backup of data considered sensitive should exclude the SMF repository databases from their backups. In the face of such a policy, non-protected property values can be backed up by -using the \fBsvccfg\fR(1M) archive command to create an archive of the +using the \fBsvccfg\fR(8) archive command to create an archive of the repository without protected property values. .SS "Service Action Authorization" .LP @@ -184,7 +184,7 @@ modify this property. .SS "Defined Rights Profiles" .LP Two rights profiles are included that offer grouped authorizations for -manipulating typical \fBsmf\fR(5) operations. +manipulating typical \fBsmf\fR(7) operations. .sp .ne 2 .na @@ -217,11 +217,11 @@ privilege checks. See NOTES. .SH SEE ALSO .LP \fBauths\fR(1), \fBprofiles\fR(1), -\fBsvccfg\fR(1M), \fBprof_attr\fR(4), \fBuser_attr\fR(4), \fBrbac\fR(5), -\fBsmf\fR(5) +\fBsvccfg\fR(8), \fBprof_attr\fR(5), \fBuser_attr\fR(5), \fBrbac\fR(7), +\fBsmf\fR(7) .SH NOTES .LP -The present version of \fBsmf\fR(5) does not support remote repositories. +The present version of \fBsmf\fR(7) does not support remote repositories. .sp .LP When a service is configured to be started as root but with privileges diff --git a/usr/src/man/man7/smf_template.7 b/usr/src/man/man7/smf_template.7 index 2a91c1008b..7db8be660b 100644 --- a/usr/src/man/man7/smf_template.7 +++ b/usr/src/man/man7/smf_template.7 @@ -32,7 +32,7 @@ The \fBsvcs -lv\fR and \fBsvccfg describe\fR commands can be used to access metadata about properties in a human-readable format. .sp .LP -\fBsvccfg\fR(1M)'s \fBvalidate\fR subcommand can be used to validate a service +\fBsvccfg\fR(8)'s \fBvalidate\fR subcommand can be used to validate a service instance or manifest against template data. A set of \fBlibscf\fR(3LIB) interfaces is available to access template data. .SS "Template Definition" @@ -799,5 +799,5 @@ service-specific configuration. .SH SEE ALSO .sp .LP -\fBsvcs\fR(1), \fBsvccfg\fR(1M), \fBlibscf\fR(3LIB), \fBservice_bundle\fR(4), -\fBsmf\fR(5) +\fBsvcs\fR(1), \fBsvccfg\fR(8), \fBlibscf\fR(3LIB), \fBservice_bundle\fR(5), +\fBsmf\fR(7) diff --git a/usr/src/man/man7/standards.7 b/usr/src/man/man7/standards.7 index c5723774d0..52c2a461b7 100644 --- a/usr/src/man/man7/standards.7 +++ b/usr/src/man/man7/standards.7 @@ -397,7 +397,7 @@ provides full support for ISO C, POSIX, and X/Open namespace reservations. If this pragma feature is not supported by the compiler, the headers use the \fB#define\fR directive to map internal function names onto appropriate library entry point names. In this instance, applications should avoid using the -explicit 64-bit file offset symbols listed on the \fBlf64\fR(5) manual page, +explicit 64-bit file offset symbols listed on the \fBlf64\fR(7) manual page, since these names are used by the implementation to name the alternative entry points. .sp @@ -484,4 +484,4 @@ c99 $(getconf POSIX_V6_LP64_OFF64_CFLAGS) -D_XOPEN_SOURCE=600 \e .SH SEE ALSO .LP \fBcsh\fR(1), \fBksh\fR(1), \fBsh\fR(1), \fBexec\fR(2), \fBsysconf\fR(3C), -\fBsystem\fR(3C), \fBenviron\fR(5), \fBlf64\fR(5) +\fBsystem\fR(3C), \fBenviron\fR(7), \fBlf64\fR(7) diff --git a/usr/src/man/man7/tecla.7 b/usr/src/man/man7/tecla.7 index 9d9496a6ae..b85fab1af1 100644 --- a/usr/src/man/man7/tecla.7 +++ b/usr/src/man/man7/tecla.7 @@ -3641,7 +3641,7 @@ The personal tecla customization 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 @@ -3658,4 +3658,4 @@ Interface Stability Evolving .LP \fBvi\fR(1), \fBcpl_complete_word\fR(3TECLA), \fBef_expand_file\fR(3TECLA), \fBgl_get_line\fR(3TECLA), \fBgl_io_mode\fR(3TECLA), \fBlibtecla\fR(3LIB), -\fBpca_lookup_file\fR(3TECLA), \fBattributes\fR(5) +\fBpca_lookup_file\fR(3TECLA), \fBattributes\fR(7) diff --git a/usr/src/man/man7/term.7 b/usr/src/man/man7/term.7 index d0b2035830..7c9f8c3fb0 100644 --- a/usr/src/man/man7/term.7 +++ b/usr/src/man/man7/term.7 @@ -11,22 +11,22 @@ term \- conventional names for terminals .LP Terminal names are maintained as part of the shell environment in the environment variable \fB\fR\fBTERM\fR\fB\&. \fR See \fBsh\fR(1), -\fBprofile\fR(4), and \fBenviron\fR(5). These names are used by certain +\fBprofile\fR(5), and \fBenviron\fR(7). These names are used by certain commands (for example, \fBtabs\fR, \fBtput\fR, and \fBvi\fR) and certain functions (for example, see \fBcurses\fR(3CURSES)). .sp .LP Files under \fB/usr/share/lib/terminfo\fR are used to name terminals and describe their capabilities. These files are in the format described in -\fBterminfo\fR(4). Entries in \fBterminfo\fR source files consist of a number +\fBterminfo\fR(5). Entries in \fBterminfo\fR source files consist of a number of comma-separated fields. To print a description of a terminal \fIterm\fR, -use the command \fBinfocmp\fR \fB-I\fR \fIterm\fR. See \fBinfocmp\fR(1M). +use the command \fBinfocmp\fR \fB-I\fR \fIterm\fR. See \fBinfocmp\fR(8). White space after each comma is ignored. The first line of each terminal description in the \fBterminfo\fR database gives the names by which \fBterminfo\fR knows the terminal, separated by bar (\fB|\fR) characters. The first name given is the most common abbreviation for the terminal (this is the one to use to set the environment variable \fBTERMINFO\fR in -\fB$HOME/.profile\fR; see \fBprofile\fR(4)), the last name given should be a +\fB$HOME/.profile\fR; see \fBprofile\fR(5)), the last name given should be a long name fully identifying the terminal, and all others are understood as synonyms for the terminal name. All names but the last should contain no blanks and must be unique in the first 14 characters; the last name may contain blanks @@ -67,7 +67,7 @@ Suffix Meaning Example To avoid conflicts with the naming conventions used in describing the different modes of a terminal (for example, \fB-w\fR), it is recommended that a terminal's root name not contain hyphens. Further, it is good practice to make -all terminal names used in the \fBterminfo\fR(4) database unique. Terminal +all terminal names used in the \fBterminfo\fR(5) database unique. Terminal entries that are present only for inclusion in other entries via the \fBuse=\fR facilities should have a '\fB+\fR' in their name, as in \fB4415+nl\fR. .sp @@ -204,5 +204,5 @@ compiled terminal description database .sp .LP \fBsh\fR(1), \fBstty\fR(1), \fBtabs\fR(1), \fBtput\fR(1), \fBvi\fR(1), -\fBinfocmp\fR(1M), \fBcurses\fR(3CURSES), \fBprofile\fR(4), \fBterminfo\fR(4), -\fBenviron\fR(5) +\fBinfocmp\fR(8), \fBcurses\fR(3CURSES), \fBprofile\fR(5), \fBterminfo\fR(5), +\fBenviron\fR(7) diff --git a/usr/src/man/man7/threads.7 b/usr/src/man/man7/threads.7 index 7826d99500..bd1841bea1 100644 --- a/usr/src/man/man7/threads.7 +++ b/usr/src/man/man7/threads.7 @@ -473,7 +473,7 @@ Users of other compilers such as gcc and clang should manually set \(mi\fBD_REENTRANT\fR on the compilation line. There are no other libraries or flags necessary. .SH ATTRIBUTES -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -489,7 +489,7 @@ MT-Level MT-Safe, Fork 1-Safe .SH SEE ALSO \fBcrle\fR(1), \fBfork\fR(2), \fBpriocntl\fR(2), \fBlibpthread\fR(3LIB), \fBlibrt\fR(3LIB), \fBlibthread\fR(3LIB), \fBpthread_atfork\fR(3C), -\fBpthread_create\fR(3C), \fBattributes\fR(5), \fBstandards\fR(5) +\fBpthread_create\fR(3C), \fBattributes\fR(7), \fBstandards\fR(7) .sp .LP \fILinker and Libraries Guide\fR diff --git a/usr/src/man/man7/trusted_extensions.7 b/usr/src/man/man7/trusted_extensions.7 index 83283cbfa0..62583cf820 100644 --- a/usr/src/man/man7/trusted_extensions.7 +++ b/usr/src/man/man7/trusted_extensions.7 @@ -21,7 +21,7 @@ policy enforced by Trusted Extensions is an example of Mandatory Access Control .sp .LP By default, Trusted Extensions software is disabled. It is enabled and disabled -(but not configured) by the \fBlabeld\fR(1M) service, identified by the FMRI: +(but not configured) by the \fBlabeld\fR(8) service, identified by the FMRI: .sp .in +2 .nf @@ -37,4 +37,4 @@ rebooted after enabling or disabling \fBlabeld\fR to activate or deactivate Trusted Extensions software. .SH SEE ALSO .LP -\fBlabeld\fR(1M), \fBlabel_encodings\fR(4), \fBlabels\fR(5) +\fBlabeld\fR(8), \fBlabel_encodings\fR(5), \fBlabels\fR(7) diff --git a/usr/src/man/man7/zones.7 b/usr/src/man/man7/zones.7 index e3aae61806..0cd5ac4ce7 100644 --- a/usr/src/man/man7/zones.7 +++ b/usr/src/man/man7/zones.7 @@ -18,15 +18,15 @@ zones. .sp .LP The privileges available within a zone are restricted to prevent operations -with system-wide impact. See \fBprivileges\fR(5). +with system-wide impact. See \fBprivileges\fR(7). .sp .LP -You can configure and administer zones with the \fBzoneadm\fR(1M) and -\fBzonecfg\fR(1M) utilities. You can specify the configuration details a zone, +You can configure and administer zones with the \fBzoneadm\fR(8) and +\fBzonecfg\fR(8) utilities. You can specify the configuration details a zone, install file system contents including software packages into the zone, and manage the runtime state of the zone. You can use the \fBzlogin\fR(1) to run commands within an active zone. You can do this without logging in through a -network-based login server such as \fBsshd\fR(1M). +network-based login server such as \fBsshd\fR(8). .sp .LP The autobooting of zones is enabled and disabled by the zones service, @@ -36,16 +36,16 @@ identified by the FMRI: svc:/system/zones:default .sp .LP -See \fBzoneadm\fR(1M). Note that a zone has an \fBautoboot\fR property, which +See \fBzoneadm\fR(8). Note that a zone has an \fBautoboot\fR property, which can be set to \fBtrue\fR (always autoboot). However, if the zones service is disabled, autoboot will not occur, regardless of the setting of the autoboot -property for a given zone. See \fBzonecfg\fR(1M). +property for a given zone. See \fBzonecfg\fR(8). .sp .LP An alphanumeric name and numeric ID identify each active zone. Alphanumeric -names are configured using the \fBzonecfg\fR(1M) utility. Numeric IDs are +names are configured using the \fBzonecfg\fR(8) utility. Numeric IDs are automatically assigned when the zone is booted. The \fBzonename\fR(1) utility -reports the current zone name, and the \fBzoneadm\fR(1M) utility can be used to +reports the current zone name, and the \fBzoneadm\fR(8) utility can be used to report the names and IDs of configured zones. .sp .LP @@ -120,7 +120,7 @@ cannot be destroyed. Such cases require operator intervention. .SS "Process Access Restrictions" Processes running inside a zone (aside from the global zone) have restricted access to other processes. Only processes in the same zone are visible through -\fB/proc\fR (see \fBproc\fR(4) or through system call interfaces that take +\fB/proc\fR (see \fBproc\fR(5) or through system call interfaces that take process IDs such as \fBkill\fR(2) and \fBpriocntl\fR(2). Attempts to access processes that exist in other zones (including the global zone) fail with the same error code that would be issued if the specified process did not exist. @@ -131,7 +131,7 @@ that might affect other zones. The set of privileges limits the capabilities of privileged users (such as the super-user or root user) within the zone. The list of privileges available within a zone can be displayed using the \fBppriv\fR(1) utility. For more information about privileges, see -\fBprivileges\fR(5). +\fBprivileges\fR(7). .SS "Device Restrictions" The set of devices available within a zone is restricted, to prevent a process in one zone from interfering with processes in other zones. For example, a @@ -139,33 +139,33 @@ process in a zone should not be able to modify kernel memory using \fB/dev/kmem\fR, or modify the contents of the root disk. Thus, by default, only a few pseudo devices considered safe for use within a zone are available. Additional devices can be made available within specific zones using the -\fBzonecfg\fR(1M) utility. +\fBzonecfg\fR(8) utility. .sp .LP The device and privilege restrictions have a number of effects on the utilities -that can run in a non-global zone. For example, the \fBeeprom\fR(1M), -\fBprtdiag\fR(1M), and \fBprtconf\fR(1M) utilities do not work in a zone since +that can run in a non-global zone. For example, the \fBeeprom\fR(8), +\fBprtdiag\fR(8), and \fBprtconf\fR(8) utilities do not work in a zone since they rely on devices that are not normally available. .SS "Brands" A zone may be assigned a brand when it is initially created. A branded zone is one whose software does not match that software found in the global zone. The software may include Solaris software configured or laid out differently, or it may include non-Solaris software. The particular collection of software is -called a "brand" (see \fBbrands\fR(5)). Once installed, a zone's brand may not +called a "brand" (see \fBbrands\fR(7)). Once installed, a zone's brand may not be changed unless the zone is first uninstalled. .SS "File Systems" Each zone has its own section of the file system hierarchy, rooted at a directory known as the zone root. Processes inside the zone can access only files within that part of the hierarchy, that is, files that are located beneath the zone root. This prevents processes in one zone from corrupting or -examining file system data associated with another zone. The \fBchroot\fR(1M) +examining file system data associated with another zone. The \fBchroot\fR(8) utility can be used within a zone, but can only restrict the process to a root path accessible within the zone. .sp .LP In order to preserve file system space, sections of the file system can be mounted into one or more zones using the read-only option of the -\fBlofs\fR(7FS) file system. This allows the same file system data to be shared +\fBlofs\fR(4FS) file system. This allows the same file system data to be shared in multiple zones, while preserving the security guarantees supplied by zones. .sp .LP @@ -174,11 +174,11 @@ cannot be accessed from other zones, including the global zone. The mounts are removed when the zone is halted or rebooted. .sp .LP -A zone can share filesystems using \fBnfs\fR(4) or \fBsmb\fR(4) +A zone can share filesystems using \fBnfs\fR(5) or \fBsmb\fR(5) subject to the restrictions earlier in this section, plus the additional restriction that file sharing can only be done from filesystems a zone -completely controls. Some \fBbrands\fR(5) do not have the zone root set to a -filesystem boundary. \fBsharefs\fR(7FS) can instantiate per-zone subject to +completely controls. Some \fBbrands\fR(7) do not have the zone root set to a +filesystem boundary. \fBsharefs\fR(4FS) can instantiate per-zone subject to the brand restrictions. .SS "Networking" A zone has its own port number space for \fBTCP\fR, \fBUDP\fR, and \fBSCTP\fR @@ -212,12 +212,12 @@ its \fBIP\fR address and spoof \fBARP\fR packets. .sp .LP The shared-\fBIP\fR zones are assigned one or more network interface names and -\fBIP\fR addresses in \fBzonecfg\fR(1M). The network interface name(s) must +\fBIP\fR addresses in \fBzonecfg\fR(8). The network interface name(s) must also be configured in the global zone. .sp .LP The exclusive-\fBIP\fR zones are assigned one or more network interface names -in \fBzonecfg\fR(1M). The network interface names must be exclusively assigned +in \fBzonecfg\fR(8). The network interface names must be exclusively assigned to that zone, that is, it (or they) can not be assigned to some other running zone, nor can they be used by the global zone. .sp @@ -227,16 +227,16 @@ The full \fBIP\fR-level functionality in the form of \fBDHCP\fR client, not in shared-\fBIP\fR zones. .SS "Host Identifiers" A zone is capable of emulating a 32-bit host identifier, which can be -configured via \fBzonecfg\fR(1M), for the purpose of system consolidation. If a +configured via \fBzonecfg\fR(8), for the purpose of system consolidation. If a zone emulates a host identifier, then commands such as \fBhostid\fR(1) and -\fBsysdef\fR(1M) as well as C interfaces such as \fBsysinfo\fR(2) and +\fBsysdef\fR(8) as well as C interfaces such as \fBsysinfo\fR(2) and \fBgethostid\fR(3C) that are executed within the context of the zone will display or return the zone's emulated host identifier rather than the host machine's identifier. .SH SEE ALSO \fBhostid\fR(1), \fBzlogin\fR(1), \fBzonename\fR(1), -\fBsshd\fR(1M), \fBsysdef\fR(1M), \fBzoneadm\fR(1M), \fBzonecfg\fR(1M), +\fBsshd\fR(8), \fBsysdef\fR(8), \fBzoneadm\fR(8), \fBzonecfg\fR(8), \fBkill\fR(2), \fBpriocntl\fR(2), \fBsysinfo\fR(2), \fBgethostid\fR(3C), -\fBgetzoneid\fR(3C), \fBucred_get\fR(3C), \fBnfs\fR(4), \fBproc\fR(4), -\fBsmb\fR(4), \fBattributes\fR(5), \fBbrands\fR(5), \fBprivileges\fR(5), -\fBsharefs\fR(7FS), \fBcrgetzoneid\fR(9F) +\fBgetzoneid\fR(3C), \fBucred_get\fR(3C), \fBnfs\fR(5), \fBproc\fR(5), +\fBsmb\fR(5), \fBattributes\fR(7), \fBbrands\fR(7), \fBprivileges\fR(7), +\fBsharefs\fR(4FS), \fBcrgetzoneid\fR(9F) diff --git a/usr/src/man/man7/zpool-features.7 b/usr/src/man/man7/zpool-features.7 index 6b26add4bf..7ef520737f 100644 --- a/usr/src/man/man7/zpool-features.7 +++ b/usr/src/man/man7/zpool-features.7 @@ -23,7 +23,7 @@ zpool\-features \- ZFS pool feature descriptions ZFS pool on\-disk format versions are specified via "features" which replace the old on\-disk format numbers (the last supported on\-disk format number is 28). To enable a feature on a pool use the \fBupgrade\fR subcommand of the -\fBzpool\fR(1M) command, or set the \fBfeature@\fR\fIfeature_name\fR property +\fBzpool\fR(8) command, or set the \fBfeature@\fR\fIfeature_name\fR property to \fBenabled\fR. .sp .LP @@ -100,7 +100,7 @@ Some features may make on\-disk format changes that do not interfere with other software's ability to read from the pool. These features are referred to as "read\-only compatible". If all unsupported features on a pool are read\-only compatible, the pool can be imported in read\-only mode by setting the -\fBreadonly\fR property during import (see \fBzpool\fR(1M) for details on +\fBreadonly\fR property during import (see \fBzpool\fR(8) for details on importing pools). .SS "Unsupported features" .LP @@ -237,7 +237,7 @@ giving approximately 10% better compression ratio. When the \fBlz4_compress\fR feature is set to \fBenabled\fR, the administrator can turn on \fBlz4\fR compression on any dataset on the -pool using the \fBzfs\fR(1M) command. Also, all newly written metadata +pool using the \fBzfs\fR(8) command. Also, all newly written metadata will be compressed with \fBlz4\fR algorithm. Since this feature is not read-only compatible, this operation will render the pool unimportable on systems without support for the \fBlz4_compress\fR feature. Booting @@ -285,7 +285,7 @@ of multiple vdevs. Those vdevs may be arranged in any mirrored or raidz configuration. When the \fBmulti_vdev_crash_dump\fR feature is set to \fBenabled\fR, -the administrator can use the \fBdumpadm\fR(1M) command to configure a +the administrator can use the \fBdumpadm\fR(8) command to configure a dump device on a pool comprised of multiple vdevs. .RE @@ -460,7 +460,7 @@ This feature is an enhancement of device_removal, which will over time reduce the memory used to track removed devices. When indirect blocks are freed or remapped, we note that their part of the indirect mapping is "obsolete", i.e. no longer needed. See also the \fBzfs remap\fR -subcommand in \fBzfs\fR(1M). +subcommand in \fBzfs\fR(8). This feature becomes \fBactive\fR when the "zpool remove" command is used on a top-level vdev, and will never return to being \fBenabled\fR. @@ -831,4 +831,4 @@ return to being \fBenabled\fR. .RE .SH "SEE ALSO" -\fBzfs\fR(1M), \fBzpool\fR(1M) +\fBzfs\fR(8), \fBzpool\fR(8) |