diff options
Diffstat (limited to 'usr/src')
29 files changed, 76 insertions, 373 deletions
diff --git a/usr/src/man/man1/ar.1 b/usr/src/man/man1/ar.1 index f783fea190..5a2ff989f2 100644 --- a/usr/src/man/man1/ar.1 +++ b/usr/src/man/man1/ar.1 @@ -44,11 +44,10 @@ .\" Portions Copyright (c) 1992, X/Open Company Limited All Rights Reserved .\" Copyright (c) 2009, Sun Microsystems, Inc. All Rights Reserved. .\" -.TH AR 1 "Sep 10, 2013" +.TH AR 1 "December 28, 2020" .SH NAME ar \- maintain portable archive or library .SH SYNOPSIS -.LP .nf \fB/usr/bin/ar\fR \fB-d\fR [\fB-Vv\fR] \fIarchive\fR \fIfile\fR... .fi @@ -119,8 +118,6 @@ ar \- maintain portable archive or library .fi .SH DESCRIPTION -.sp -.LP The \fBar\fR utility maintains groups of files combined into a single archive file. Its main use is to create and update library files. However, it can be used for any similar purpose. The magic string and the file headers used by @@ -140,8 +137,6 @@ accessible to the user. Whenever the \fBar\fR command is used to create or update the contents of such an archive, the symbol table is rebuilt. The \fB-s\fR option described below forces the symbol table to be rebuilt. .SH OPTIONS -.sp -.LP The following options are supported: .sp .ne 2 @@ -200,7 +195,7 @@ Deletes one or more \fIfile\fRs from \fIarchive\fR. .ad .RS 6n Positions new \fIfile\fRs in \fIarchive\fR before the file named by the -\fIposname\fR operand. This option is quivalent to \fB-b\fR. +\fIposname\fR operand. This option is equivalent to \fB-b\fR. .RE .sp @@ -331,8 +326,6 @@ Prints its version number on standard error. .RE .SS "\fB/usr/xpg4/bin/ar\fR" -.sp -.LP The following options are supported for \fB/usr/xpg4/bin/ar\fR: .sp .ne 2 @@ -360,8 +353,6 @@ is being extracted, the results are undefined. The modification time of each .RE .SH OPERANDS -.sp -.LP The following operands are supported: .sp .ne 2 @@ -396,8 +387,6 @@ options \fB-m\fR and \fB-r\fR. .RE .SH ENVIRONMENT VARIABLES -.sp -.LP See \fBenviron\fR(5) for descriptions of the following environment variables that affect the execution of \fBar\fR: \fBLANG\fR, \fBLC_ALL\fR, \fBLC_CTYPE\fR, \fBLC_MESSAGES\fR, \fBLC_TIME\fR, and \fBNLSPATH\fR. @@ -423,8 +412,6 @@ timezone is used. .RE .SH EXIT STATUS -.sp -.LP The following exit values are returned: .sp .ne 2 @@ -445,13 +432,8 @@ An error occurred. .RE .SH ATTRIBUTES -.sp -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .SS "\fB/usr/bin/ar\fR" -.sp - -.sp .TS box; c | c @@ -462,9 +444,6 @@ Interface Stability Committed .TE .SS "\fB/usr/xpg4/bin/ar\fR" -.sp - -.sp .TS box; c | c @@ -477,14 +456,10 @@ Standard See \fBstandards\fR(5). .TE .SH SEE ALSO -.sp -.LP \fBbasename\fR(1), \fBcpio\fR(1), \fBld\fR(1), \fBlorder\fR(1), \fBstrip\fR(1), \fBtar\fR(1), \fBar.h\fR(3HEAD), \fBa.out\fR(4), \fBattributes\fR(5), \fBenviron\fR(5), \fBstandards\fR(5) .SH NOTES -.sp -.LP If the same file is mentioned twice in an argument list, it may be put in the archive twice. .sp diff --git a/usr/src/man/man1/ctfdump.1 b/usr/src/man/man1/ctfdump.1 index b80c856eaf..8d63b2a0a5 100644 --- a/usr/src/man/man1/ctfdump.1 +++ b/usr/src/man/man1/ctfdump.1 @@ -11,7 +11,7 @@ .\" .\" Copyright 2018, Joyent, Inc. .\" -.Dd Oct 2, 2018 +.Dd December 28, 2020 .Dt CTFDUMP 1 .Os .Sh NAME @@ -141,7 +141,7 @@ container. .Bd -filled -compact Dump the type information contained in the .Sy CTF -conatiner. +container. .Ed .It Fl u Ar outfile .Bd -filled -compact diff --git a/usr/src/man/man1/demangle.1 b/usr/src/man/man1/demangle.1 index ca2dbef35a..20037f6721 100644 --- a/usr/src/man/man1/demangle.1 +++ b/usr/src/man/man1/demangle.1 @@ -15,7 +15,7 @@ .\" .\" Copyright 2020 Joyent, Inc. .\" -.Dd March 3, 2020 +.Dd December 28, 2020 .Dt DEMANGLE 1 .Os .Sh NAME @@ -63,7 +63,7 @@ is output unchanged. In the second method, .Nm reads standard in, and whenever it encounters a potential symbol, it will -attempt to replace the symbol in stdandard out with the demangled version. +attempt to replace the symbol in standard out with the demangled version. If the symbol cannot be demangled, it is output unchanged. .Pp For either method, if an error other than attempting to demangle an non-mangled diff --git a/usr/src/man/man1/lari.1 b/usr/src/man/man1/lari.1 index 39e4ff3531..ae51c87363 100644 --- a/usr/src/man/man1/lari.1 +++ b/usr/src/man/man1/lari.1 @@ -3,11 +3,10 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH LARI 1 "Nov 28, 2007" +.TH LARI 1 "December 28, 2020" .SH NAME lari \- link analysis of runtime interfaces .SH SYNOPSIS -.LP .nf \fBlari\fR [\fB-bCDsVv\fR] [\fB-a\fR | \fB-i\fR | \fB-o\fR] \fIfile\fR | \fIdirectory\fR... .fi @@ -18,8 +17,6 @@ lari \- link analysis of runtime interfaces .fi .SH DESCRIPTION -.sp -.LP The \fBlari\fR utility analyzes the interface requirements of dynamic \fBELF\fR objects. Two basic modes of operation are available. The first mode displays runtime interface information. The second mode generates interface definitions. @@ -99,8 +96,6 @@ associated \fImapfile\fR directives. See the \fILinker and Libraries Guide\fR for more details on using \fImapfiles\fR to version objects. An initial version of these \fImapfiles\fR can be created by \fBlari\fR. .SH OPTIONS -.sp -.LP The following options are supported. .sp .ne 2 @@ -295,7 +290,7 @@ This symbol definition has been directly bound to. .ad .RS 11n This symbol definition provides for an interposer. An object that explicitly -identifies itself as an interposor defines all global symbols as interposers. +identifies itself as an interposer defines all global symbols as interposers. See the \fB-z\fR \fBinterpose\fR option of \fBld\fR(1), and the \fBLD_PRELOAD\fR variable of \fBld.so.1\fR(1). Individual symbols within a dynamic executable can be defined as interposers by using the \fBINTERPOSE\fR @@ -391,8 +386,6 @@ See the \fILinker and Libraries Guide\fR for more details of these symbol classifications. .SH EXTENDED DESCRIPTION .SS "Interesting Information" -.sp -.LP By default, or specifically using the \fB-i\fR option, \fBlari\fR filters any runtime interface information to present interesting events. This filtering is carried out mainly to reduce the amount of information that can be generated @@ -473,8 +466,6 @@ explicitly established, instances can exist that are unexpected and surprising. Directly bound symbols, and symbols with protected visibility, are output as interesting information. .SS "Overhead Information" -.sp -.LP When using the \fB-o\fR option, \fBlari\fR displays symbol definitions that might be considered overhead. .sp @@ -555,7 +546,6 @@ bindings of this type require relocation processing at application start up, rather than the deferred relocation processing used when calling functions directly. Use of this address also requires an indirection at runtime. .SH EXAMPLES -.LP \fBExample 1 \fRAnalyzing a case of multiple bindings .sp .LP @@ -649,7 +639,6 @@ foo.so { .sp .SH FILES -.sp .ne 2 .na \fB\fB$TMPDIR/lari.dbg.\fIfile\fR\fR\fR @@ -659,8 +648,6 @@ Binding output produced by \fBldd\fR(1). .RE .SH ATTRIBUTES -.sp -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp @@ -678,8 +665,6 @@ Interface Stability See below. .LP The human readable output is Uncommitted. The options are Committed. .SH SEE ALSO -.sp -.LP \fBld\fR(1), \fBldd\fR(1), \fBld.so.1\fR(1), \fBdlopen\fR(3C), \fBdlsym\fR(3C), \fBattributes\fR(5) .sp diff --git a/usr/src/man/man1/ld.so.1.1 b/usr/src/man/man1/ld.so.1.1 index 4b14ca4f1a..2fa525dae5 100644 --- a/usr/src/man/man1/ld.so.1.1 +++ b/usr/src/man/man1/ld.so.1.1 @@ -3,11 +3,10 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. .\" See the License for the specific language governing permissions and limitations under the License. When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with .\" the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH LD.SO.1 1 "Oct 5, 2012" +.TH LD.SO.1 1 "December 28, 2020" .SH NAME ld.so.1 \- runtime linker for dynamic objects .SH SYNOPSIS -.LP .nf \fB/lib/ld.so.1\fR .fi @@ -18,8 +17,6 @@ ld.so.1 \- runtime linker for dynamic objects .fi .SH DESCRIPTION -.sp -.LP Dynamic applications consist of one or more dynamic objects. A dynamic application is typically a dynamic executable and one or more shared object dependencies. As part of the initialization and execution of a dynamic @@ -39,7 +36,7 @@ link-editor is the name of the runtime linker, \fBld.so.1\fR. During the process of executing a dynamic executable, the kernel maps the file, and locates the required interpreter. See \fBexec\fR(2) and \fBmmapobj\fR(2). The kernel maps in, and transfers control to, this interpreter. Sufficient -information is passed to the interpretor to allow the interpreter to continue +information is passed to the interpreter to allow the interpreter to continue to bind, and then execute the application. .sp .LP @@ -142,8 +139,6 @@ runpath is specified when the dynamic object is constructed using the \fB-R\fR option to \fBld\fR(1). The environment variable \fBLD_LIBRARY_PATH\fR can be used to indicate directories to be searched before the default directories. .SS "Command Line Usage" -.sp -.LP Typically, the runtime linker is invoked indirectly through executing a dynamic executable that declares the runtime linker as its interpreter. The runtime linker can also be executed directly from the command line. This mechanism is @@ -167,8 +162,6 @@ VARIABLES. .RE .SH ENVIRONMENT VARIABLES -.sp -.LP Each environment variable can be specified with a \fB_32\fR or \fB_64\fR suffix. This makes the environment variable specific, respectively, to 32-bit or 64-bit processes. This environment variable overrides any non-suffixed @@ -579,8 +572,6 @@ Notice that environment variable names beginning with the characters '\fBLD_\fR' are reserved for possible future enhancements to \fBld\fR(1) and \fBld.so.1\fR. .SH SECURITY -.sp -.LP Secure processes have some restrictions applied to the evaluation of their dependencies and runpaths to prevent malicious dependency substitution or symbol interposition. @@ -652,7 +643,6 @@ When creating a secure process, relative path names should \fBnot\fR be used to express dependencies, or to construct \fBdlopen\fR(3C) path names. This restriction should be applied to the application and to \fBall\fR dependencies. .SH EXAMPLES -.LP \fBExample 1 \fRUsing LD_FLAGS to group environment variable information .sp .LP @@ -683,7 +673,6 @@ example% \fBLD_FLAGS_64=library_path=/lib/one/64,preload=foo.so\fR .sp .SH FILES -.sp .ne 2 .na \fB\fB/lib/ld.so.1\fR\fR @@ -784,8 +773,6 @@ Default configuration file for 64-bit applications. .RE .SH SEE ALSO -.sp -.LP \fBcrle\fR(1), \fBgprof\fR(1), \fBlari\fR(1), \fBld\fR(1), \fBldd\fR(1), \fBexec\fR(2), \fBissetugid\fR(2), \fBmmapobj\fR(2), \fBprofil\fR(2), \fBdladdr\fR(3C), \fBdlclose\fR(3C), \fBdldump\fR(3C), \fBdlerror\fR(3C), @@ -795,8 +782,6 @@ Default configuration file for 64-bit applications. .LP \fILinker and Libraries Guide\fR .SH NOTES -.sp -.LP Care should be exercised when using \fBLD_PROFILE\fR in combination with other process monitoring techniques, such as users of \fBproc\fR(4). Multiple process monitoring techniques can result in deadlock conditions that leave the profile diff --git a/usr/src/man/man1/pktool.1 b/usr/src/man/man1/pktool.1 index 491d7c6493..52869c4106 100644 --- a/usr/src/man/man1/pktool.1 +++ b/usr/src/man/man1/pktool.1 @@ -3,18 +3,15 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. .\" See the License for the specific language governing permissions and limitations under the License. When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the .\" fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH PKTOOL 1 "Mar 23, 2009" +.TH PKTOOL 1 "December 28, 2020" .SH NAME pktool \- manage certificates and keys .SH SYNOPSIS -.LP .nf \fBpktool\fR [\fB-f\fR \fIoption_file\fR] [\fB-i\fR] \fIsubcommand\fR \fIsubcommand_options\fR ... .fi .SH DESCRIPTION -.sp -.LP The \fBpktool\fR command allows users to manage the certificates and keys on multiple keystores including PKCS#11 tokens (that is, Cryptographic Framework), Netscape Security Services (NSS) tokens, and standard file based keystore for @@ -26,8 +23,6 @@ Revocation List (CRL). \fBpktool\fR does not provide support for creating CRLs, signing CRLs, or exporting CRLs. The CRL support for the PKCS#11 keystore is file-based. .SH OPTIONS -.sp -.LP The following command options are supported: .sp .ne 2 @@ -97,8 +92,6 @@ The resulting \fBsubject-DN\fR is: .RE .SH SUBCOMMANDS -.sp -.LP The following subcommands are supported: .sp .ne 2 @@ -719,8 +712,6 @@ synonym for \fB-?\fR. .RE .SH USAGE -.sp -.LP The \fBpktool\fR subcommands support the following options: .sp .ne 2 @@ -887,7 +878,7 @@ For the \fBgencert\fR and \fBgencsr\fR subcommands, the valid private key types are: \fBrsa\fR, or \fBdsa\fR. The default key type is \fBrsa\fR. .sp For the \fBgenkey\fR subcommand, the valid symmetric key types are: \fBaes\fR, -\fBarcfou\fRr, \fBdes\fR, \fB3des\fR, or \fBgeneric\fR. The default key type is +\fBarcfour\fR, \fBdes\fR, \fB3des\fR, or \fBgeneric\fR. The default key type is \fBaes\fR. .sp .in +2 @@ -1249,7 +1240,6 @@ command line option has a higher priority than the environment variable. .RE .SH EXAMPLES -.LP \fBExample 1 \fRGenerating a Self-Signed Certificate .sp .LP @@ -1301,8 +1291,6 @@ file into the keystore indicated in the command: .sp .SH EXIT STATUS -.sp -.LP The following exit values are returned: .sp .ne 2 @@ -1323,8 +1311,6 @@ An error occurred. .RE .SH ATTRIBUTES -.sp -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp @@ -1339,8 +1325,6 @@ Interface Stability Committed .TE .SH SEE ALSO -.sp -.LP \fBattributes\fR(5), \fBpkcs11_softtoken\fR(5) .sp .LP diff --git a/usr/src/man/man1/print.1 b/usr/src/man/man1/print.1 index 3aefc897c8..d872fa475d 100644 --- a/usr/src/man/man1/print.1 +++ b/usr/src/man/man1/print.1 @@ -5,38 +5,32 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH PRINT 1 "Mar 27, 2008" +.TH PRINT 1 "December 28, 2020" .SH NAME print \- shell built-in function to output characters to the screen or window .SH SYNOPSIS .SS "ksh" -.LP .nf \fBprint\fR [\fB-Rnprsu\fR [\fIn\fR]] [\fIarg\fR]... .fi .SS "ksh93" -.LP .nf \fBprint\fR [\fB-Renprs\fR] [\fB-f\fR \fIformat\fR] [\fB-u\fR \fIfd\fR] [\fIstring\fR...] .fi .SH DESCRIPTION .SS "ksh" -.sp -.LP The shell output mechanism. When no options are specified, or when an option followed by \fB\&'\fR a \fB\(mi\fR is specified, or when just \fB-\fR is specified, the arguments are printed on standard output as described by \fBecho\fR(1). .SS "ksh93" -.sp -.LP By default, \fBprint\fR writes each string operand to standard output and appends a NEWLINE character. .sp .LP -Unless, the \fB-r\fR, \fB-R\fR, or \fB-f\fR option is speciifed, each \fB\e\fR +Unless, the \fB-r\fR, \fB-R\fR, or \fB-f\fR option is specified, each \fB\e\fR character in each string operand is processed specially as follows: .sp .ne 2 @@ -132,8 +126,6 @@ The 8-bit character whose \fBASCII\fR code is the \fB1\fR-, \fB2\fR-, or .SH OPTIONS .SS "ksh" -.sp -.LP The following options are supported by \fBksh\fR: .sp .ne 2 @@ -185,8 +177,6 @@ placed. The default is 1. .RE .SS "ksh93" -.sp -.LP The following options are supported by \fBksh93\fR: .sp .ne 2 @@ -271,8 +261,6 @@ default value is \fB1\fR. .RE .SH EXIT STATUS -.sp -.LP The following exit values are returned: .sp .ne 2 @@ -293,7 +281,5 @@ Output file is not open for writing. .RE .SH SEE ALSO -.sp -.LP \fBecho\fR(1), \fBksh\fR(1), \fBksh93\fR(1), \fBprintf\fR(1), \fBattributes\fR(5) diff --git a/usr/src/man/man1/tnfdump.1 b/usr/src/man/man1/tnfdump.1 index 77cfb22b6b..6093cf7dc4 100644 --- a/usr/src/man/man1/tnfdump.1 +++ b/usr/src/man/man1/tnfdump.1 @@ -3,24 +3,21 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH TNFDUMP 1 "Jan 22, 2001" +.TH TNFDUMP 1 "December 28, 2020" .SH NAME tnfdump \- convert binary TNF file to ASCII .SH SYNOPSIS -.LP .nf \fBtnfdump\fR [\fB-r\fR] [\fB-x\fR] \fItnf_file\fR... .fi .SH DESCRIPTION -.LP The \fBtnfdump\fR utility converts the specified binary \fBTNF\fR trace files to \fBASCII\fR. The \fBASCII\fR output can be used to do performance analysis. The default mode (without the \fB-r\fR option) prints all the event records (that were generated by \fBTNF_PROBE\fR(3TNF)) and the event descriptor records only. It also orders the events by time. .SH OPTIONS -.LP The following option is supported: .sp .ne 2 @@ -29,7 +26,7 @@ The following option is supported: .ad .RS 6n Does a raw conversion of \fBTNF\fR to \fBASCII\fR. The output is a literal -transalation of the binary \fBTNF\fR file and includes all the records in the +translation of the binary \fBTNF\fR file and includes all the records in the file. This output is useful only if you have a good understanding of \fBTNF\fR. A sample output is listed in EXAMPLES below. .RE @@ -45,10 +42,8 @@ instead of decimal format. .RE .SH RETURN VALUES -.LP \fBtnfdump\fR returns \fB0\fR on successful exit. .SH EXAMPLES -.LP \fBExample 1 \fRConverting a file into ASCII .sp .LP @@ -345,6 +340,5 @@ unsigned arguments. Their values are printed in hexadecimal when requested by option \fB-x\fR. .SH SEE ALSO -.LP \fBprex\fR(1), \fBgethrtime\fR(3C), \fBTNF_DECLARE_RECORD\fR(3TNF), \fBTNF_PROBE\fR(3TNF), \fBtnf_process_disable\fR(3TNF), \fBattributes\fR(5) diff --git a/usr/src/man/man1m/wificonfig.1m b/usr/src/man/man1m/wificonfig.1m index 1772ec890f..3bfe7132ab 100644 --- a/usr/src/man/man1m/wificonfig.1m +++ b/usr/src/man/man1m/wificonfig.1m @@ -3,11 +3,10 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH WIFICONFIG 1M "Oct 31, 2007" +.TH WIFICONFIG 1M "December 28, 2020" .SH NAME wificonfig \- WLAN configuration .SH SYNOPSIS -.LP .nf \fBwificonfig\fR [\fB-R\fR \fIroot_path\fR] [\fB-i\fR \fIinterface\fR] autoconf [\fIwait\fR={\fIn\fR|\fIforever\fR}] @@ -117,8 +116,6 @@ wificonfig \- WLAN configuration .fi .SH DESCRIPTION -.sp -.LP \fBwificonfig\fR defines a set of subcommands and parameters to configure \fBWiFi\fR interfaces in the system. A driver may support all parameters or a subset of these parameters. @@ -167,8 +164,6 @@ configure the interface. (See the \fBautoconf\fR subcommand for the heuristics). A few subcommands (\fBlistprefer\fR, \fBsetprefer\fR, \fBremoveprefer\fR) are defined to manipulate the Preference List. .SH OPTIONS -.sp -.LP The following options are supported: .sp .ne 2 @@ -191,8 +186,6 @@ Configuration Profiles and \fBWEP\fR keys. .RE .SS "OPERANDS" -.sp -.LP The following operand is supported: .sp .ne 2 @@ -207,8 +200,6 @@ profile name. .RE .SS "SUBCOMMANDS" -.sp -.LP The following subcommands are supported: .sp .ne 2 @@ -265,7 +256,7 @@ parameter is set as "profile". .sp If the \fBWLAN\fRs in the Preference list are available, the user can specify the number of seconds to wait before \fBconnect\fR returns using the wait -option. By default (without the wait option), \fBconnect\fR trys for 10 +option. By default (without the wait option), \fBconnect\fR tries for 10 seconds. If "\fIforever\fR" or -1 follows the wait option, \fBwificonfig\fR tries until the \fBNIC\fR is successfully connected to the profile or essid that was specified. @@ -275,7 +266,7 @@ whether or not a Configuration Profile was found for the specified name: .sp .in +2 .nf -Connecting to profile <name> +Connecting to profile <name> Connecting to essid <name> .fi .in -2 @@ -781,7 +772,6 @@ subcommand. .RE .SH EXAMPLES -.LP \fBExample 1 \fRListing the Parameters Supported by a Driver .sp .LP @@ -884,10 +874,10 @@ To display the history of the \fBWLAN\fRs: WLAN history: essid bssid encryption last seen - myXXX 00:0f:24:11:12:14 WEP Fri Sep 13 09:15:24 2004 - my_office_ssid 00:0f:24:11:12:15 WEP Fri Sep 13 13:20:04 2004 - my_neighbor1 00:0f:24:11:12:16 NONE Fri Sep 14 08:01:26 2004 - my_neighbor2 00:0f:24:11:12:17 WEP Fri Sep 18 21:33:12 2004 + myXXX 00:0f:24:11:12:14 WEP Fri Sep 13 09:15:24 2004 + my_office_ssid 00:0f:24:11:12:15 WEP Fri Sep 13 13:20:04 2004 + my_neighbor1 00:0f:24:11:12:16 NONE Fri Sep 14 08:01:26 2004 + my_neighbor2 00:0f:24:11:12:17 WEP Fri Sep 18 21:33:12 2004 .fi .in -2 .sp @@ -910,7 +900,7 @@ To configure the interface according to the previously saved Preference List: .sp .LP If the Preference List is empty, or none of the \fBWLAN\fRs listed by the -Proference List can be found, \fBwificonfig\fR uses the default configuration, +Preference List can be found, \fBwificonfig\fR uses the default configuration, directs the interface to scan and join the \fBWLAN\fR using the built-in heuristics specified above. @@ -1011,7 +1001,6 @@ roomlinx 00:40:96:a0:ab:39 access point none 8 .sp .SH EXIT STATUS -.sp .ne 2 .na \fB\fB0\fR\fR @@ -1049,8 +1038,6 @@ Minor error .RE .SH ATTRIBUTES -.sp -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp @@ -1065,6 +1052,4 @@ Interface Stability Unstable .TE .SH SEE ALSO -.sp -.LP \fBps\fR(1), \fBifconfig\fR(1M), \fBattributes\fR(5), \fBath\fR(7D) diff --git a/usr/src/man/man3c/cond_init.3c b/usr/src/man/man3c/cond_init.3c index d90296e420..198594167c 100644 --- a/usr/src/man/man3c/cond_init.3c +++ b/usr/src/man/man3c/cond_init.3c @@ -44,7 +44,7 @@ .\" Copyright (c) 2001, The IEEE and The Open Group. All Rights Reserved. .\" Copyright (c) 2007, Sun Microsystems, Inc. All Rights Reserved. .\" -.TH COND_INIT 3C "February 15, 2020" +.TH COND_INIT 3C "December 28, 2020" .SH NAME cond_init, cond_wait, cond_timedwait, cond_reltimedwait, cond_signal, cond_broadcast, cond_destroy \- condition variables @@ -435,7 +435,7 @@ The \fBcond_timedwait()\fR and \fBcond_reltimedwait()\fR functions are similar to \fBcond_wait()\fR, except that the calling thread will not wait for the condition to become true past the absolute time specified by \fIabstime\fR or the relative time specified by \fIreltime\fR. Note that \fBcond_timedwait()\fR -or \fBcond_reltimedwait()\fR might continue to block as it trys to reacquire +or \fBcond_reltimedwait()\fR might continue to block as it tries to reacquire the mutex pointed to by \fImp\fR, which may be locked by another thread. If either \fBcond_timedwait()\fR or \fBcond_reltimedwait()\fR returns because of a timeout, it returns the error value \fBETIME\fR. diff --git a/usr/src/man/man3c/mbsrtowcs.3c b/usr/src/man/man3c/mbsrtowcs.3c index bf4d3a04d9..05efa21401 100644 --- a/usr/src/man/man3c/mbsrtowcs.3c +++ b/usr/src/man/man3c/mbsrtowcs.3c @@ -44,12 +44,11 @@ .\" Portions Copyright (c) 2003, Sun Microsystems, Inc. All Rights Reserved. .\" Copyright 2014 Garrett D'Amore <garrett@damore.org> .\" -.TH MBSRTOWCS 3C "Jun 28, 2014" +.TH MBSRTOWCS 3C "December 28, 2020" .SH NAME mbsnrtowcs, mbsnrtowcs_l, mbsrtowcs, mbsrtowcs_l \- convert a character string to a wide-character string (restartable) .SH SYNOPSIS -.LP .nf #include <wchar.h> @@ -75,7 +74,6 @@ to a wide-character string (restartable) \fBsize_t\fR \fIlen\fR, \fBmbstate_t *restrict\fR \fIps\fR, \fBlocale_t\fR \fIloc\fR); .fi .SH DESCRIPTION -.LP These function converts a sequence of characters, beginning in the conversion state described by the object pointed to by \fIps\fR, from the array indirectly pointed to by \fIsrc\fR into a sequence of corresponding @@ -124,7 +122,6 @@ current locale. See \fBenviron\fR(5). The functions \fBmbsrtowcs_l()\fR and \fBmbsnrtowcs()\fR, except that instead of using the current locale, they use the locale specified by \fIloc\fR. .SH RETURN VALUES -.LP If the input conversion encounters a sequence of bytes that do not form a valid character, an encoding error occurs. In this case, these functions store the value of the macro \fBEILSEQ\fR in \fBerrno\fR and return @@ -132,8 +129,7 @@ functions store the value of the macro \fBEILSEQ\fR in \fBerrno\fR and return the number of characters successfully converted, not including the terminating null (if any). .SH ERRORS -.LP -Theses functions may fail if: +These functions may fail if: .sp .ne 2 .na @@ -153,7 +149,6 @@ state. Invalid character sequence is detected. .RE .SH ATTRIBUTES -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .TS box; @@ -183,7 +178,6 @@ multithreaded applications, otherwise they use an internal \fBmbstate_t\fR object and are Unsafe in multithreaded applications. .SH SEE ALSO -.LP \fBmbrtowc\fR(3C), \fBmbsinit\fR(3C), \fBnewlocale\fR(3C), \fBsetlocale\fR(3C), \fBuselocale()\fR, \fBattributes\fR(5), \fBenviron\fR(5), \fBstandards\fR(5) diff --git a/usr/src/man/man3curses/curs_kernel.3curses b/usr/src/man/man3curses/curs_kernel.3curses index 34c4e63d9d..2c8a38b49f 100644 --- a/usr/src/man/man3curses/curs_kernel.3curses +++ b/usr/src/man/man3curses/curs_kernel.3curses @@ -4,13 +4,12 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH CURS_KERNEL 3CURSES "Dec 31, 1996" +.TH CURS_KERNEL 3CURSES "December 28, 2020" .SH NAME curs_kernel, def_prog_mode, def_shell_mode, reset_prog_mode, reset_shell_mode, resetty, savetty, getsyx, setsyx, ripoffline, curs_set, napms \- low-level curses routines .SH SYNOPSIS -.LP .nf \fBcc\fR [ \fIflag\fR ... ] \fIfile\fR ... \fB-lcurses\fR [ \fIlibrary\fR ... ] #include <curses.h> @@ -69,10 +68,8 @@ curses routines .fi .SH DESCRIPTION -.sp -.LP The following routines give low-level access to various \fBcurses\fR -functionality. Theses routines typically are used inside library routines. +functionality. These routines typically are used inside library routines. .sp .LP The \fBdef_prog_mode()\fR and \fBdef_shell_mode()\fR routines save the current @@ -139,14 +136,10 @@ the previous \fIcursor\fR state is returned; otherwise, \fBERR\fR is returned. .LP The \fBnapms()\fR routine is used to sleep for \fIms\fR milliseconds. .SH RETURN VALUES -.sp -.LP Except for \fBcurs_set()\fR, these routines always return \fBOK\fR. \fBcurs_set()\fR returns the previous cursor state, or \fBERR\fR if the requested \fIvisibility\fR is not supported. .SH ATTRIBUTES -.sp -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp @@ -161,14 +154,10 @@ MT-Level Unsafe .TE .SH SEE ALSO -.sp -.LP \fBcurs_initscr\fR(3CURSES), \fBcurs_outopts\fR(3CURSES), \fBcurs_refresh\fR(3CURSES), \fBcurs_scr_dump\fR(3CURSES), \fBcurs_slk\fR(3CURSES), \fBcurses\fR(3CURSES), \fBattributes\fR(5) .SH NOTES -.sp -.LP The header <\fBcurses.h\fR> automatically includes the headers <\fBstdio.h\fR> and <\fBunctrl.h\fR>. .sp diff --git a/usr/src/man/man3iscsit/it_portal_create.3iscsit b/usr/src/man/man3iscsit/it_portal_create.3iscsit index ef12705a7a..e6c387ef3c 100644 --- a/usr/src/man/man3iscsit/it_portal_create.3iscsit +++ b/usr/src/man/man3iscsit/it_portal_create.3iscsit @@ -3,11 +3,10 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH IT_PORTAL_CREATE 3ISCSIT "Oct 1, 2008" +.TH IT_PORTAL_CREATE 3ISCSIT "December 28, 2020" .SH NAME it_portal_create, it_portal_delete \- create and delete iSCSI portals .SH SYNOPSIS -.LP .nf cc [ \fIflag\fR\&.\|.\|. ] \fIfile\fR\&.\|.\|. \fB-liscsit\fR [ \fIlibrary\fR\&.\|.\|. ] #include <libiscsit.h> @@ -23,7 +22,6 @@ cc [ \fIflag\fR\&.\|.\|. ] \fIfile\fR\&.\|.\|. \fB-liscsit\fR [ \fIlibrary\fR\&. .fi .SH PARAMETERS -.sp .ne 2 .na \fB\fIcfg\fR\fR @@ -56,14 +54,12 @@ a pointer to the \fBit_portal_t\fR structure representing the portal \fB\fIportal_ip_port\fR\fR .ad .RS 18n -a string containing an appropriatedly formatted IP address:port. Both IPv4 and +a string containing an appropriately formatted IP address:port. Both IPv4 and IPv6 addresses are permitted. IPv6 addresses should be enclosed in square brackets ('[', ']'). .RE .SH DESCRIPTION -.sp -.LP The \fBit_portal_create()\fR function adds an \fBit_portal_t\fR structure representing a new portal to the specified target portal group. A portal may belong to one and only one target portal group. @@ -77,13 +73,9 @@ Configuration changes as a result of these functions are not instantiated until the modified configuration is committed by calling \fBit_config_commit\fR(3ISCSIT). .SH RETURN VALUES -.sp -.LP The \fBit_portal_create()\fR function returns 0 on success and an error value on failure. .SH ERRORS -.sp -.LP The \fBit_portal_create()\fR function will fail if: .sp .ne 2 @@ -113,8 +105,6 @@ Resources could not be allocated. .RE .SH ATTRIBUTES -.sp -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp @@ -131,8 +121,6 @@ MT-Level MT-Safe .TE .SH SEE ALSO -.sp -.LP \fBit_ini_create\fR(3ISCSIT), \fBit_tgt_create\fR(3ISCSIT), \fBit_tpg_create\fR(3ISCSIT), \fBlibiscsit\fR(3LIB), \fBit_config_commit\fR(3ISCSIT), \fBlibiscsit\fR(3LIB), \fBlibnvpair\fR(3LIB), diff --git a/usr/src/man/man3lgrp/lgrp_affinity_get.3lgrp b/usr/src/man/man3lgrp/lgrp_affinity_get.3lgrp index d9d5315c4e..3fed0a871f 100644 --- a/usr/src/man/man3lgrp/lgrp_affinity_get.3lgrp +++ b/usr/src/man/man3lgrp/lgrp_affinity_get.3lgrp @@ -3,11 +3,10 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH LGRP_AFFINITY_GET 3LGRP "Apr 16, 2003" +.TH LGRP_AFFINITY_GET 3LGRP "December 28, 2020" .SH NAME -lgrp_affinity_get, lgrp_affinity_set \- get of set lgroup affinity +lgrp_affinity_get, lgrp_affinity_set \- get or set lgroup affinity .SH SYNOPSIS -.LP .nf cc [ \fIflag \&.\|.\|.\fR ] \fIfile\fR\&.\|.\|. \fB-llgrp\fR [ \fIlibrary \&.\|.\|.\fR ] #include <sys/lgrp_user.h> @@ -23,7 +22,6 @@ cc [ \fIflag \&.\|.\|.\fR ] \fIfile\fR\&.\|.\|. \fB-llgrp\fR [ \fIlibrary \&.\|. .fi .SH DESCRIPTION -.LP The \fBlgrp_affinity_get()\fR function returns the affinity that the LWP or set of LWPs specified by the \fIidtype\fR and \fIid\fR arguments have for the given lgroup. @@ -86,7 +84,7 @@ home lgroup for which it has a strong affinity. .LP The \fBLGRP_AFF_WEAK\fR affinity is a hint to the operating system that the calling thread has a weak affinity for the given lgroup. If a thread has a -weak affinity for its home lgroup, the operating system interpets this to mean +weak affinity for its home lgroup, the operating system interprets this to mean that thread does not mind whether it is rehomed, unlike \fBLGRP_AFF_STRONG\fR. Load balancing, dynamic reconfiguration, processor binding, or processor set binding and manipulation are examples of events that can cause the operating @@ -98,7 +96,6 @@ remove a thread's affinity for a particular lgroup. Initially, each thread has no affinity to any lgroup. If a thread has no lgroup affinities set, the operating system chooses a home lgroup for the thread with no affinity set. .SH RETURN VALUES -.LP Upon successful completion, \fBlgrp_affinity_get()\fR returns the affinity for the given lgroup. .sp @@ -109,7 +106,6 @@ Upon successful completion, \fBlgrp_affinity_set()\fR return 0. Otherwise, both functions return \(mi1 and set \fBerrno\fR to indicate the error. .SH ERRORS -.LP The \fBlgrp_affinity_get()\fR and \fBlgrp_affinity_set()\fR functions will fail if: .sp @@ -142,7 +138,6 @@ The specified lgroup or LWP(s) was not found. .RE .SH ATTRIBUTES -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp @@ -159,5 +154,4 @@ MT-Level MT-Safe .TE .SH SEE ALSO -.LP \fBlgrp_home\fR(3LGRP), \fBliblgrp\fR(3LIB), \fBattributes\fR(5) diff --git a/usr/src/man/man3m/fex_set_handling.3m b/usr/src/man/man3m/fex_set_handling.3m index ba74f0f159..3a2585025b 100644 --- a/usr/src/man/man3m/fex_set_handling.3m +++ b/usr/src/man/man3m/fex_set_handling.3m @@ -3,12 +3,11 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH FEX_SET_HANDLING 3M "Jul 12, 2006" "SunOS 5.11" "Mathematical Library Functions" +.TH FEX_SET_HANDLING 3M "December 28, 2020" "SunOS 5.11" "Mathematical Library Functions" .SH NAME fex_set_handling, fex_get_handling, fex_getexcepthandler, fex_setexcepthandler \- control floating point exception handling modes .SH SYNOPSIS -.LP .nf c99 [ \fIflag\fR... ] \fIfile\fR... -lm [ \fIlibrary\fR... ] #include <fenv.h> @@ -32,8 +31,6 @@ c99 [ \fIflag\fR... ] \fIfile\fR... -lm [ \fIlibrary\fR... ] .fi .SH DESCRIPTION -.sp -.LP These functions provide control of floating point exception handling modes. For each function, the \fIex\fR argument specifies one or more exceptions indicated by a bitwise-OR of any of the following values defined in <\fBfenv.h\fR>: @@ -307,7 +304,7 @@ the value contained in \fBinfo->res\fR on exit is substituted for the result of the operation, the flags indicated by \fBinfo->flags\fR are set, and execution resumes at the point where the exception occurred. The handler might modify \fBinfo->res\fR and \fBinfo->flags\fR to supply any desired result value and -flags. Alternatively, if the exception is underflow or overflow, the hander +flags. Alternatively, if the exception is underflow or overflow, the handler might set .sp .LP @@ -348,13 +345,9 @@ structure pointed to by \fIbuf\fR. This data structure must have been set by a previous call to \fBfex_getexcepthandler()\fR. Otherwise the effect on the indicated modes is undefined. .SH RETURN VALUES -.sp -.LP The \fBfex_set_handling()\fR function returns a non-zero value if the requested exception handling mode is established. Otherwise, it returns 0. .SH EXAMPLES -.sp -.LP The following example demonstrates how to substitute a predetermined value for the result of a 0/0 invalid operation. .sp @@ -424,8 +417,6 @@ When \fIx\fR = 0, \fIf(x)\fR is computed as 0/0 and an invalid operation exception occurs. In this example, the value 2.0 is substituted for the result. .SH ATTRIBUTES -.sp -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp @@ -442,16 +433,12 @@ MT-Level MT-Safe (see Notes) .TE .SH SEE ALSO -.sp -.LP \fBsigfpe\fR(3C), \fBfeclearexcept\fR(3M), \fBfegetenv\fR(3M), \fBfex_set_log\fR(3M), \fBattributes\fR(5) .sp .LP \fINumerical Computation Guide\fR .SH NOTES -.sp -.LP In a multithreaded application, the preceding functions affect exception handling modes only for the calling thread. .sp diff --git a/usr/src/man/man3resolv/resolver.3resolv b/usr/src/man/man3resolv/resolver.3resolv index f54bda17d1..cf5b7037da 100644 --- a/usr/src/man/man3resolv/resolver.3resolv +++ b/usr/src/man/man3resolv/resolver.3resolv @@ -1,7 +1,7 @@ '\" te .\" Portions Copyright 1989 AT&T Portions Copyright (c) 1985, 1995 Regents of the University of California. .\" Copyright (C) 2006, Sun Microsystems, Inc. All Rights Reserved -.TH RESOLVER 3RESOLV "April 9, 2016" +.TH RESOLVER 3RESOLV "December 28, 2020" .SH NAME resolver, res_ninit, fp_resstat, res_hostalias, res_nquery, res_nsearch, res_nquerydomain, res_nmkquery, res_nsend, res_nclose, res_nsendsigned, @@ -9,7 +9,6 @@ dn_comp, dn_expand, hstrerror, res_init, res_query, res_search, res_mkquery, res_send, herror, res_getservers, res_setservers, res_ndestroy \- resolver routines .SH SYNOPSIS -.LP .nf BIND 8.2.2 Interfaces .fi @@ -163,7 +162,6 @@ Deprecated Interfaces .fi .SH DESCRIPTION -.LP These routines are used for making, sending, and interpreting query and reply messages with Internet domain name servers. .sp @@ -326,7 +324,6 @@ the header would be updated. .RE .SS "\fBres_ninit()\fR, \fBres_init()\fR" -.LP The \fBres_ninit()\fR and \fBres_init()\fR routines read the configuration file, if any is present, to get the default domain name, search list and the Internet address of the local name server(s). See \fBresolv.conf\fR(4). If no @@ -345,7 +342,6 @@ are inherited from the configuration file's \fBoptions\fR command. See \fBRES_OPTIONS\fR environment variable. Initialization normally occurs on the first call to one of the other resolver routines. .SS "\fBres_nquery()\fR, \fBres_query()\fR" -.LP The \fBres_nquery()\fR and \fBres_query()\fR functions provide interfaces to the server query mechanism. They construct a query, send it to the local server, await a response, and make preliminary checks on the reply. The query @@ -364,12 +360,11 @@ by the previous query. \fIanswer\fR must be large enough to receive a maximum \fBUDP\fR response from the server or parts of the \fIanswer\fR will be silently discarded. The default maximum \fBUDP\fR response size is 512 bytes. .SS "\fBres_nsearch()\fR, \fBres_search()\fR" -.LP The \fBres_nsearch()\fR and \fBres_search()\fR routines make a query and await a response, just like like \fBres_nquery()\fR and \fBres_query()\fR. In addition, they implement the default and search rules controlled by the \fBRES_DEFNAMES\fR and \fBRES_DNSRCH\fR options. They return the length of the -first successful reply which is stored in \fIanswer\fR. On error, they reurn +first successful reply which is stored in \fIanswer\fR. On error, they return -1. .sp .LP @@ -381,12 +376,10 @@ by the previous query. \fIanswer\fR must be large enough to receive a maximum \fBUDP\fR response from the server or parts of the \fIanswer\fR will be silently discarded. The default maximum \fBUDP\fR response size is 512 bytes. .SS "\fBres_nquerydomain()\fR" -.LP The \fBres_nquerydomain()\fR function calls \fBres_query()\fR on the concatenation of \fIname\fR and \fIdomain\fR, removing a trailing dot from \fIname\fR if \fIdomain\fR is \fINULL\fR. .SS "\fBres_nmkquery()\fR, \fBres_mkquery()\fR" -.LP These routines are used by \fBres_nquery()\fR and \fBres_query()\fR. The \fBres_nmkquery()\fR and \fBres_mkquery()\fR functions construct a standard query message and place it in \fIbuf\fR. The routine returns the \fIsize\fR of @@ -395,7 +388,6 @@ the query, or -1 if the query is larger than \fIbuflen\fR. The query type <\fBarpa/nameser.h\fR>. The domain name for the query is given by \fIdname\fR. \fInewrr\fR is currently unused but is intended for making update messages. .SS "\fBres_nsend()\fR, \fBres_send()\fR, \fBres_nsendsigned()\fR" -.LP The \fBres_nsend()\fR, \fBres_send()\fR, and \fBres_nsendsigned()\fR routines send a pre-formatted query that returns an \fIanswer\fR. The routine calls \fBres_ninit()\fR or \fBres_init()\fR. If \fBRES_INIT\fR is not set, the @@ -414,26 +406,21 @@ by the previous query. \fIanswer\fR must be large enough to receive a maximum \fBUDP\fR response from the server or parts of the \fIanswer\fR will be silently discarded. The default maximum \fBUDP\fR response size is 512 bytes. .SS "\fBfp_resstat()\fR" -.LP The function \fBfp_resstat()\fR prints out the active flag bits in \fIstatp\fR->\fBoptions\fR preceded by the text "\fB;; res options:\fR" on \fIfile\fR. .SS "\fBres_hostalias()\fR" -.LP The function \fBres_hostalias()\fR looks up \fIname\fR in the file referred to by the \fBHOSTALIASES\fR environment variable and returns the fully qualified host name. If \fIname\fR is not found or an error occurs, \fBNULL\fR is returned. \fBres_hostalias()\fR stores the result in \fIbuf\fR. .SS "\fBres_nclose()\fR" -.LP The \fBres_nclose()\fR function closes any open files referenced through \fIstatp\fR. .SS "\fBres_ndestroy()\fR" -.LP The \fBres_ndestroy()\fR function calls \fBres_nclose()\fR, then frees any memory allocated by \fBres_ninit()\fR referenced through \fIstatp\fR. .SS "\fBdn_comp()\fR" -.LP The \fBdn_comp()\fR function compresses the domain name \fIexp_dn\fR and stores it in \fIcomp_dn\fR. The \fBdn_comp()\fR function returns the size of the compressed name, or \fB\(mi1\fR if there were errors. \fIlength\fR is the size @@ -451,7 +438,6 @@ labels inserted into the message by \fBdn_comp()\fR as the name is compressed. If \fIdnptrs\fR is \fINULL\fR, names are not compressed. If \fIlastdnptr\fR is \fINULL\fR, \fBdn_comp()\fR does not update the list of labels. .SS "\fBdn_expand()\fR" -.LP The \fBdn_expand()\fR function expands the compressed domain name \fIcomp_dn\fR to a full domain name. The compressed name is contained in a query or reply message. \fImsg\fR is a pointer to the beginning of that message. The @@ -459,7 +445,6 @@ uncompressed name is placed in the buffer indicated by \fIexp_dn\fR, which is of size \fIlength\fR. The \fBdn_expand()\fR function returns the size of the compressed name, or \fB\(mi1\fR if there was an error. .SS "\fBhstrerror()\fR, \fBherror()\fR" -.LP The variables \fIstatp->res_h_errno\fR and \fI_res.res_h_errno\fR and external variable \fIh_errno\fR are set whenever an error occurs during a resolver operation. The following definitions are given in <\fBnetdb.h\fR>: @@ -486,7 +471,6 @@ message corresponding to the value of \fIh_errno\fR. The \fBhstrerror()\fR function returns a string, which is the message text that corresponds to the value of the \fIerr\fR parameter. .SS "\fBres_setservers()\fR, \fBres_getservers()\fR" -.LP The functions \fBres_getservers()\fR and \fBres_setservers()\fR are used to get and set the list of servers to be queried. .SH FILES @@ -499,7 +483,6 @@ resolver configuration file .RE .SH ATTRIBUTES -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp @@ -517,7 +500,6 @@ T} .TE .SH SEE ALSO -.LP \fBdomainname\fR(1M), \fBgethostbyname\fR(3NSL), \fBlibresolv\fR(3LIB), \fBresolv.conf\fR(4), \fBattributes\fR(5) .sp @@ -545,7 +527,6 @@ November 1987. Vixie, Paul, Dunlap, Kevin J., Karels, Michael J. \fIName Server Operations Guide for BIND\fR. Internet Software Consortium, 1996. .SH NOTES -.LP When the caller supplies a work buffer, for example the \fIanswer\fR buffer argument to \fBres_nsend()\fR or \fBres_send()\fR, the buffer should be aligned on an eight byte boundary. Otherwise, an error such as a \fBSIGBUS\fR may diff --git a/usr/src/man/man4/bart_manifest.4 b/usr/src/man/man4/bart_manifest.4 index 133b85a6d6..dd2950a25f 100644 --- a/usr/src/man/man4/bart_manifest.4 +++ b/usr/src/man/man4/bart_manifest.4 @@ -3,12 +3,10 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH BART_MANIFEST 4 "Sep 9, 2003" +.TH BART_MANIFEST 4 "December 28, 2020" .SH NAME bart_manifest \- system audit manifest file .SH DESCRIPTION -.sp -.LP The \fBbart\fR(1M) command generates a manifest that describes the contents of a managed host. A manifest consists of a header and entries. Each entry represents a single file. Entries are sorted in ascending order by file name. @@ -33,8 +31,6 @@ This comment block lists the attributes reported for each file type. .LP To see the format of a manifest file, see \fBEXAMPLES\fR. .SS "Manifest File Entries" -.sp -.LP Each manifest file entry is a single line of one of the following forms, depending on the file type: .sp @@ -243,14 +239,12 @@ block device files only. .RE .SS "Quoting Syntax" -.sp -.LP The rules file supports a quoting syntax for representing nonstandard file names. .sp .LP -When generating a manifest for file names that embeded TAB, SPACE, or NEWLINE -characters, the special characters are encoded in their octal forms. +When generating a manifest for file names that contain embedded TAB, SPACE, or +NEWLINE characters, the special characters are encoded in their octal forms. .sp .sp @@ -274,7 +268,6 @@ _ .TE .SH EXAMPLES -.LP \fBExample 1 \fRSample Manifest File .sp .LP @@ -310,6 +303,4 @@ the encoded versions of the file names to correctly handle special characters. .in -2 .SH SEE ALSO -.sp -.LP \fBdate\fR(1), \fBbart\fR(1M), \fBbart_rules\fR(4), \fBattributes\fR(5) diff --git a/usr/src/man/man4/crypt.conf.4 b/usr/src/man/man4/crypt.conf.4 index 58134ea715..f86fdf8d2c 100644 --- a/usr/src/man/man4/crypt.conf.4 +++ b/usr/src/man/man4/crypt.conf.4 @@ -3,18 +3,15 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH CRYPT.CONF 4 "Jun 10, 2002" +.TH CRYPT.CONF 4 "December 28, 2020" .SH NAME crypt.conf \- configuration file for pluggable crypt modules .SH SYNOPSIS -.LP .nf /etc/security/crypt.conf .fi .SH DESCRIPTION -.sp -.LP \fBcrypt.conf\fR is the configuration file for the pluggable crypt architecture. Each crypt module must provide a function to generate a password hash, \fBcrypt_genhash_impl\fR(3C), and a function to generate the salt, @@ -42,7 +39,6 @@ is the responsibility of the module to parse and interpret the options. The any module-specific parameters that control the output of the hashing algorithm. .SH EXAMPLES -.LP \fBExample 1 \fRProvide compatibility for md5crypt-generated passwords. .sp .LP @@ -78,7 +74,7 @@ algorithm names 1 and 2. md5 /usr/lib/security/$ISA/crypt_md5.so rot13 /usr/lib/security/$ISA/crypt_rot13.so -# For *BSD/Linux compatibilty +# For *BSD/Linux compatibility # 1 is md5, 2 is Blowfish 1 /usr/lib/security/$ISA/crypt_bsdmd5.so 2 /usr/lib/security/$ISA/crypt_bsdbf.so @@ -86,8 +82,6 @@ rot13 /usr/lib/security/$ISA/crypt_rot13.so .in -2 .SH ATTRIBUTES -.sp -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp @@ -102,8 +96,6 @@ Interface Stability Evolving .TE .SH SEE ALSO -.sp -.LP \fBpasswd\fR(1), \fBcrypt\fR(3C), \fBcrypt_genhash_impl\fR(3C), \fBcrypt_gensalt\fR(3C), \fBcrypt_gensalt_impl\fR(3C), \fBgetpassphrase\fR(3C), \fBpasswd\fR(4), \fBattributes\fR(5), \fBcrypt_unix\fR(5) diff --git a/usr/src/man/man4/nfs.4 b/usr/src/man/man4/nfs.4 index 29b60bf5e2..95822c75e6 100644 --- a/usr/src/man/man4/nfs.4 +++ b/usr/src/man/man4/nfs.4 @@ -20,7 +20,7 @@ .\" Copyright 2016 Nexenta Systems, Inc. .\" Copyright 2020 Joyent, Inc. .\" -.Dd February 4, 2020 +.Dd December 28, 2020 .Dt NFS 4 .Os .Sh NAME @@ -134,7 +134,7 @@ is equivalent to on the .Nm nfsd command line. -Mutually exlusive of +Mutually exclusive of .Sy device . For the UDP protocol, only version 2 and version 3 service is established. NFS Version 4 is not supported for the UDP protocol. diff --git a/usr/src/man/man4/process.4 b/usr/src/man/man4/process.4 index 50f80efca2..de168cfbcb 100644 --- a/usr/src/man/man4/process.4 +++ b/usr/src/man/man4/process.4 @@ -3,18 +3,15 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH PROCESS 4 "Mar 25, 2008" +.TH PROCESS 4 "December 28, 2020" .SH NAME process \- process contract type .SH SYNOPSIS -.LP .nf \fB/system/contract/process\fR .fi .SH DESCRIPTION -.sp -.LP Process contracts allow processes to create a fault boundary around a set of subprocesses and observe events which occur within that boundary. .sp @@ -23,8 +20,6 @@ Process contracts are managed using the \fBcontract\fR(4) file system and the \fBlibcontract\fR(3LIB) library. The process contract type directory is \fB/system/contract/process\fR. .SS "CREATION" -.sp -.LP A process contract is created when an LWP that has an active process contract template calls \fBfork\fR(2). Initially, the child process created by \fBfork()\fR is the only resource managed by the contract. When an LWP that @@ -32,8 +27,6 @@ does not have an active process contract template calls \fBfork()\fR, the child process created by \fBfork()\fR is added as a resource to the process contract of which the parent was a member. .SS "EVENT TYPES" -.sp -.LP The following events types are defined: .sp .ne 2 @@ -99,8 +92,6 @@ A process was killed because of an uncorrectable hardware error. .RE .SS "TERMS" -.sp -.LP The following common contract terms, defined in \fBcontract\fR(4), have process-contract specific attributes: .sp @@ -286,7 +277,7 @@ in its effective set. .RS 4n Specifies the ID of an empty process contract held by the caller whose inherited process contracts are to be transferred to the newly created -contract. Use \fBct_pr_tmpl_set_transfer\fR(3CONTRACT) to set the tranfer +contract. Use \fBct_pr_tmpl_set_transfer\fR(3CONTRACT) to set the transfer contract. Attempts to specify a contract not held by the calling process, or a contract which still has processes in it, fail. .sp @@ -294,8 +285,6 @@ The default transfer term is \fB0\fR, that is, no contract. .RE .SS "STATUS" -.sp -.LP In addition to the standard items, the status object read from a status file descriptor contains the following items to obtain this information respectively: @@ -421,8 +410,6 @@ when observed by processes in the non-global zone. .RE .SS "EVENTS" -.sp -.LP In addition to the standard items, an event generated by a process contract contains the following information: .sp @@ -534,7 +521,6 @@ The PID of the process which sent the signal. Use .RE .SH FILES -.sp .ne 2 .na \fB\fB/usr/include/sys/contract/process.h\fR\fR @@ -545,8 +531,6 @@ Contains definitions of event-type macros. .RE .SH SEE ALSO -.sp -.LP \fBctrun\fR(1), \fBctstat\fR(1), \fBctwatch\fR(1), \fBcoreadm\fR(1M), \fBclose\fR(2), \fBfork\fR(2), \fBioctl\fR(2), \fBopen\fR(2), \fBpoll\fR(2), \fBct_pr_event_get_exitstatus\fR(3CONTRACT), diff --git a/usr/src/man/man4/smb.4 b/usr/src/man/man4/smb.4 index d6296f2ea8..cecabe8179 100644 --- a/usr/src/man/man4/smb.4 +++ b/usr/src/man/man4/smb.4 @@ -17,7 +17,7 @@ .\" fields enclosed by brackets "[]" replaced with your own identifying .\" information: Portions Copyright [yyyy] [name of copyright owner] .\" -.TH SMB 4 "May 16, 2020" +.TH SMB 4 "December 28, 2020" .SH NAME smb \- configuration properties for Solaris CIFS server .SH DESCRIPTION @@ -162,7 +162,7 @@ when encryption is On (see \fBencrypt\fR property) and negotiated SMB dialect is .sp When the property is set the valid values are aes-128-ccm and aes-128-gcm. If aes-128-gcm is selected both CCM and GCM are allowed, but GCM is preferred. -If aes-128-ccm is seelcted it is the only allowed cipher. If the property is not +If aes-128-ccm is selected it is the only allowed cipher. If the property is not set explicitly the default value is used - aes-128-gcm. .sp The property can be set to one of these values: diff --git a/usr/src/man/man4/sysbus.4 b/usr/src/man/man4/sysbus.4 index 4c171db2e4..77970edacc 100644 --- a/usr/src/man/man4/sysbus.4 +++ b/usr/src/man/man4/sysbus.4 @@ -3,16 +3,14 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH SYSBUS 4 "Nov 18, 2004" +.TH SYSBUS 4 "December 28, 2020" .SH NAME sysbus, isa \- device tree properties for ISA bus device drivers .SH DESCRIPTION -.sp -.LP -Solaris for x86 supports the \fBISA\fR bus as the system bus. Drivers for -devices on this buse use the device tree built by the booting system to +Solaris for x86 supports the \fBISA\fR bus as the system bus. Drivers for +devices on this bus use the device tree built by the booting system to retrieve the necessary system resources used by the driver. These resources -include device I/O port addresses, any interrupt capabilities that the device +include device I/O port addresses, any interrupt capabilities that the device can have, any DMA channels it can require, and any memory-mapped addresses it can occupy. .sp @@ -42,7 +40,7 @@ file for the driver. Each entry in the array of integers for the the \fBinterrupts\fR property to specify the \fBIPL\fR value that is used by the system for this interrupt in this driver. This is the priority that this device's interrupt handler receives relative to the interrupt handlers of other -drivers. The priority is an integer from \fB1\fR to \fB16\fR. Generally, +drivers. The priority is an integer from \fB1\fR to \fB16\fR. Generally, disks are assigned a priority of \fB5\fR, while mice and printers are lower, and serial communication devices are higher, typically \fB7\fR. \fB10\fR is reserved by the system and must not be used. Priorities \fB11\fR and greater @@ -69,14 +67,14 @@ associated with the device on the bus. The first integer of the tuple specifies the memory type, \fB0\fR specifies a memory range and \fB1\fR specifies an I/O range. The second integer specifies the base address of the memory range. The third integer of each 3-tuple -specifies the size, in bytes, of the mappable region. +specifies the size, in bytes, of the mappable region. .sp The driver can refer to the elements of this array by index, and construct kernel mappings to these addresses using \fBddi_map_regs\fR(9F). The index into -the array is passed as the \fIrnumber\fR argument of \fBddi_map_regs()\fR. +the array is passed as the \fIrnumber\fR argument of \fBddi_map_regs()\fR. .sp -All \fBsysbus\fR devices have \fBreg\fR properties. The first tuple of this -property is used to construct the address part of the device name under +All \fBsysbus\fR devices have \fBreg\fR properties. The first tuple of this +property is used to construct the address part of the device name under \fB/devices\fR. In the case of \fBPlug and Play ISA\fR devices, the first tuple is a special tuple that does not denote a memory range, but is used by the system only to create the address part of the device name. This special tuple @@ -106,8 +104,6 @@ devices that use DMA channels have a \fBdma-channels\fR property. .RE .SH ATTRIBUTES -.sp -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp @@ -122,8 +118,6 @@ Architecture x86 .TE .SH SEE ALSO -.sp -.LP \fBprtconf\fR(1M), \fBdriver.conf\fR(4), \fBscsi\fR(4), \fBattributes\fR(5), \fBddi_add_intr\fR(9F), \fBddi_intr_hilevel\fR(9F), \fBddi_map_regs\fR(9F), \fBddi_prop_op\fR(9F) diff --git a/usr/src/man/man4/terminfo.4 b/usr/src/man/man4/terminfo.4 index d1d5577d62..cadbccc0ef 100644 --- a/usr/src/man/man4/terminfo.4 +++ b/usr/src/man/man4/terminfo.4 @@ -4,17 +4,15 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH TERMINFO 4 "April 9, 2016" +.TH TERMINFO 4 "December 28, 2020" .SH NAME terminfo \- terminal and printer capability database .SH SYNOPSIS -.LP .nf \fB/usr/share/lib/terminfo/?/*\fR .fi .SH DESCRIPTION -.LP The \fBterminfo\fR database describes the capabilities of devices such as terminals and printers. Devices are described in \fBterminfo\fR source files by specifying a set of capabilities, by quantifying certain aspects of the device, @@ -109,7 +107,6 @@ The \fBterminfo\fR reference manual page is organized in two sections: \fBPART 2: PRINTER CAPABILITIES\fR .RE .SS "PART 1: DEVICE CAPABILITIES" -.LP Capabilities in \fBterminfo\fR are of three types: Boolean capabilities (which show that a device has or does not have a particular feature), numeric capabilities (which quantify particular features of a device), and string @@ -443,7 +440,6 @@ insert_padding ip ip Insert pad after .sp .SS "key_Strings" -.LP The ``\fBkey_\fR'' strings are sent by specific keys. The ``\fBkey_\fR'' descriptions include the macro, defined in \fB<curses.h>\fR, for the code returned by the \fBcurses\fR routine \fBgetch\fR when the key is pressed (see @@ -905,7 +901,6 @@ zero_motion zerom Zx No motion for the .sp .SS "Sample Entry" -.LP The following entry, which describes the AT&T 610 terminal, is among the more complex entries in the \fBterminfo\fR file as of this writing. .sp @@ -946,7 +941,6 @@ complex entries in the \fBterminfo\fR file as of this writing. .in -2 .SS "Types of Capabilities in the Sample Entry" -.LP The sample entry shows the formats for the three types of \fBterminfo\fR capabilities listed: Boolean, numeric, and string. All capabilities specified in the \fBterminfo\fR source file must be followed by commas, including the @@ -1008,7 +1002,6 @@ period before the capability name. For example, see the second \fBind\fR in the example above. Note that capabilities are defined in a left-to-right order and, therefore, a prior definition will override a later definition. .SS "Preparing Descriptions" -.LP The most effective way to prepare a device description is by imitating the description of a similar device in \fBterminfo\fR and building up a description gradually, using partial descriptions with \fBvi\fR to check that they are @@ -1024,7 +1017,6 @@ from the middle of the screen, and then press the \fBu\fR key several times quickly. If the display is corrupted, more padding is usually needed. A similar test can be used for insert-character. .SS "Section 1-1: Basic Capabilities" -.LP The number of columns on each line for the device is given by the \fBcols\fR numeric capability. If the device has a screen, then the number of lines on the screen is given by the \fBlines\fR capability. If the device wraps around to @@ -1113,7 +1105,6 @@ adm3 | lsi adm3, .sp .SS "Section 1-2: Parameterized Strings" -.LP Cursor addressing and other strings requiring parameters are described by a parameterized string capability, with \fBprintf\fR-like escapes (\fB%\fR\fIx\fR) in it. For example, to address the cursor, the \fBcup\fR @@ -1348,7 +1339,6 @@ space (32), adds them (pushing the sum on the stack in place of the two previous values), and outputs that value as a character. Then the same is done for the second parameter. More complex arithmetic is possible using the stack. .SS "Section 1-3: Cursor Motions" -.LP If the terminal has a fast way to home the cursor (to very upper left corner of screen) then this can be given as \fBhome\fR; similarly a fast way of getting to the lower left-hand corner can be given as \fBll\fR; this may involve going @@ -1382,7 +1372,6 @@ command character to be the one used by \fBterminfo\fR. If the \fBsmcup\fR sequence will not restore the screen after an \fBrmcup\fR sequence is output (to the state prior to outputting \fBrmcup\fR), specify \fBnrrmc\fR. .SS "Section 1-4: Area Clears" -.LP If the terminal can clear from the current position to the end of the line, leaving the cursor where it is, this should be given as \fBel\fR. If the terminal can clear from the beginning of the line to the current position @@ -1392,7 +1381,6 @@ then this should be given as \fBed\fR. \fBed\fR is only defined from the first column of a line. (Thus, it can be simulated by a request to delete a large number of lines, if a true \fBed\fR is not available.) .SS "Section 1-5: Insert/Delete Line" -.LP If the terminal can open a new blank line before the line where the cursor is, this should be given as \fBil1\fR; this is done only from the first position of a line. The cursor must then appear on the newly blank line. If the terminal @@ -1438,7 +1426,6 @@ be given. These indicate that deleting a line or scrolling a full screen may bring non-blank lines up from below or that scrolling back with \fBri\fR may bring down non-blank lines. .SS "Section 1-6: Insert/Delete Character" -.LP There are two basic kinds of intelligent terminals with respect to insert/delete character operations which can be described using \fBterminfo.\fR The most common insert/delete character operations affect only the characters @@ -1500,7 +1487,6 @@ terminal needs to be placed in for \fBdch1\fR to work). A command to erase \fIn\fR characters (equivalent to outputting \fIn\fR blanks without moving the cursor) can be given as \fBech\fR with one parameter. .SS "Section 1-7: Highlighting, Underlining, and Visible Bells" -.LP Your device may have one or more kinds of display attributes that allow you to highlight selected characters when they appear on the screen. The following display modes (shown with the names by which they are set) may be available: a @@ -1582,7 +1568,7 @@ needs the following escape sequences to turn on various modes. .TS c c c c c c . -tparm +tparm parameter attribute escape sequence _ none \eE[0m @@ -1645,7 +1631,6 @@ Putting this all together into the \fBsgr\fR sequence gives: .LP Remember that \fBsgr\fR and \fBsgr0\fR must always be specified. .SS "Section 1-8: Keypad" -.LP If the device has a keypad that transmits sequences when the keys are pressed, this information can also be specified. Note that it is not possible to handle devices where the keypad only works in local (this applies, for example, to the @@ -1687,7 +1672,6 @@ and off, give them in \fBsmln\fR and \fBrmln\fR. \fBsmln\fR is normally output after one or more \fBpln\fR sequences to make sure that the change becomes visible. .SS "Section 1-9: Tabs and Initialization" -.LP If the device has hardware tabs, the command to advance to the next tab stop can be given as \fBht\fR (usually control I). A ``backtab'' command that moves leftward to the next tab stop can be given as \fBcbt\fR. By convention, if tty @@ -1743,7 +1727,6 @@ Any margin can be cleared with \fBmgc\fR. (For instructions on how to specify commands to set and clear margins, see "Margins" below under "PRINTER CAPABILITIES".) .SS "Section 1-10: Delays" -.LP Certain capabilities control padding in the \fBtty\fR driver. These are primarily needed by hard-copy terminals, and are used by \fBtput\fR \fBinit\fR to set tty modes appropriately. Delays embedded in the capabilities \fBcr\fR, @@ -1752,7 +1735,6 @@ appropriate delay bits to be set in the tty driver. If \fBpb\fR (padding baud rate) is given, these values can be ignored at baud rates below the value of \fBpb\fR. .SS "Section 1-11: Status Lines" -.LP If the terminal has an extra ``status line'' that is not normally used by software, this fact can be indicated. If the status line is viewed as an extra line below the bottom line, into which one can cursor address normally (such as @@ -1776,7 +1758,6 @@ line is a different width (possibly because the terminal does not allow an entire line to be loaded) the width, in columns, can be indicated with the numeric parameter \fBwsl\fR. .SS "Section 1-12: Line Graphics" -.LP If the device has a line drawing alternate character set, the mapping of glyph to character would be given in \fBacsc\fR. The definition of this string is based on the alternate character set used in the DEC VT100 terminal, extended @@ -1847,7 +1828,6 @@ Now write down the characters left to right, as in In addition, \fBterminfo\fR allows you to define multiple character sets. See Section 2-5 for details. .SS "Section 1-13: Color Manipulation" -.LP Let us define two methods of color manipulation: the Tektronix method and the HP method. The Tektronix method uses a set of N predefined colors (usually 8) from which a user can select "current" foreground and background colors. Thus a @@ -1938,7 +1918,6 @@ cannot coexist with colors. For example, if the terminal uses colors to simulate reverse video (bit number 2 and decimal value 4) and bold (bit number 5 and decimal value 32), the resulting value for \fBncv\fR will be 36 (4 + 32). .SS "Section 1-14: Miscellaneous" -.LP If the terminal requires other than a null (zero) character as a pad, then this can be given as \fBpad\fR. Only the first character of the \fBpad\fR string is used. If the terminal does not have a pad character, specify \fBnpc\fR. @@ -2009,7 +1988,6 @@ screen when the printer is on, specify \fBmc5i\fR (silent printer). All text, including \fBmc4\fR, is transparently passed to the printer while an \fBmc5p\fR is in effect. .SS "Section 1-15: Special Cases" -.LP The working model used by \fBterminfo\fR fits most terminals reasonably well. However, some terminals do not completely match that model, requiring special support by \fBterminfo\fR. These are not meant to be construed as deficiencies @@ -2044,7 +2022,6 @@ Those Beehive Superbee terminals which do not transmit the escape or control\(miC characters, should specify \fBxsb\fR, indicating that the f1 key is to be used for escape and the f2 key for control C. .SS "Section 1-16: Similar Terminals" -.LP If there are two very similar terminals, one can be defined as being just like the other with certain exceptions. The string capability \fBuse\fR can be given with the name of the similar terminal. The capabilities given before \fBuse\fR @@ -2067,20 +2044,17 @@ defines an AT&T4424 terminal that does not have the \fBrev\fR, \fBsgr\fR, and different modes for a terminal, or for different user preferences. More than one \fBuse\fR capability may be given. .SS "PART 2: PRINTER CAPABILITIES" -.LP The \fBterminfo\fR database allows you to define capabilities of printers as well as terminals. To find out what capabilities are available for printers as well as for terminals, see the two lists under "DEVICE CAPABILITIES" that list capabilities by variable and by capability name. .SS "Section 2-1: Rounding Values" -.LP Because parameterized string capabilities work only with integer values, we recommend that \fBterminfo\fR designers create strings that expect numeric values that have been rounded. Application designers should note this and should always round values to the nearest integer before using them with a parameterized string capability. .SS "Section 2-2: Printer Resolution" -.LP A printer's resolution is defined to be the smallest spacing of characters it can achieve. In general printers have independent resolution horizontally and vertically. Thus the vertical resolution of a printer can be determined by @@ -2122,7 +2096,6 @@ capability would give the width of a page in columns. In ``micro mode,'' many printers the micro mode may be concomitant with normal mode, so that all the capabilities work at the same time. .SS "Section 2-3: Specifying Printer Resolution" -.LP The printing resolution of a printer is given in several ways. Each specifies the resolution as the number of smallest steps per distance: .sp @@ -2289,7 +2262,6 @@ $V sub italic cpi$, $V sub italic lpi$, $V sub italic chr$, and $V sub italic cvr$ are the arguments used with \fBcpi\fR, \fBlpi\fR, \fBchr\fR, and \fBcvr\fR, respectively. The prime marks (\|'\|) indicate the old values. .SS "Section 2-4: Capabilities that Cause Movement" -.LP In the following descriptions, ``movement'' refers to the motion of the ``current position.'' With video terminals this would be the cursor; with some printers this is the carriage position. Other printers have different @@ -2453,7 +2425,6 @@ Miscellaneous Motion Strings .sp .SS "Margins" -.LP \fBterminfo\fR provides two strings for setting margins on terminals: one for the left and one for the right margin. Printers, however, have two additional margins, for the top and bottom margins of each page. Furthermore, some @@ -2516,7 +2487,6 @@ the bottom line of the page. .LP All margins can be cleared with \fBmgc\fR. .SS "Shadows, Italics, Wide Characters" -.LP Five new sets of strings describe the capabilities printers have of enhancing printed text. .sp @@ -2594,7 +2564,6 @@ affecting shadow, italicized, widened, superscript, or subscript printing. Conversely, if \fBmsgr\fR is not set, a program should end these modes before attempting any motion. .SS "Section 2-5: Alternate Character Sets" -.LP In addition to allowing you to define line graphics (described in Section 1-12), \fBterminfo\fR lets you define alternate character sets. The following capabilities cover printers and terminals with multiple selectable or definable @@ -2680,7 +2649,6 @@ are not available, the strings should not be defined. For printers that have manually changed print-wheels or font cartridges, the boolean \fBdaisy\fR is set. .SS "Section 2-6: Dot-Matrix Graphics" -.LP Dot-matrix printers typically have the capability of reproducing ``raster-graphics'' images. Three new numeric capabilities and three new string capabilities can help a program draw raster-graphics images independent of the @@ -2703,7 +2671,7 @@ Dot-Matrix Graphics .sp .LP -The \fBsbim\fR sring is used with a single argument, \fIB\fR, the width of the +The \fBsbim\fR string is used with a single argument, \fIB\fR, the width of the image in dots. .sp .LP @@ -2769,7 +2737,6 @@ the decimal values are further offset by the value 63. The \fBporder\fR string for these printers would be \fB,,6,5,4,3,2,1;63\fR, or alternately \fBo,o,6,5,4,3,2,1;63\fR. .SS "Section 2-7: Effect of Changing Printing Resolution" -.LP If the control sequences to change the character pitch or the line pitch are used, the pin or dot spacing may change: .sp @@ -2829,7 +2796,6 @@ in steps per inch, before using \fBlpi\fR and after using \fBlpi\fR, respectively. Thus, the changes in the dots per inch for dot-matrix graphics follow the changes in steps per inch for printer resolution. .SS "Section 2-8: Print Quality" -.LP Many dot-matrix printers can alter the dot spacing of printed text to produce near ``letter quality'' printing or ``draft quality'' printing. Usually it is important to be able to choose one or the other because the rate of printing @@ -2853,7 +2819,6 @@ The capabilities are listed in decreasing levels of quality. If a printer doesn't have all three levels, one or two of the strings should be left blank as appropriate. .SS "Section 2-9: Printing Rate and Buffer Size" -.LP Because there is no standard protocol that can be used to keep a program synchronized with a printer, and because modern printers can buffer data before printing it, a program generally cannot determine at any time what has been @@ -2939,12 +2904,10 @@ terminal (escape sequences that set margins and tabs) .RE .SH SEE ALSO -.LP \fBls\fR(1), \fBpg\fR(1), \fBstty\fR(1), \fBtput\fR(1), \fBtty\fR(1), \fBvi\fR(1), \fBinfocmp\fR(1M), \fBtic\fR(1M), \fBprintf\fR(3C), \fBcurses\fR(3CURSES), \fBcurses\fR(3XCURSES) .SH NOTES -.LP The most effective way to prepare a terminal description is by imitating the description of a similar terminal in \fBterminfo\fR and to build up a description gradually, using partial descriptions with a screen oriented diff --git a/usr/src/man/man7d/cpqary3.7d b/usr/src/man/man7d/cpqary3.7d index 5f52d849a6..1ed77081ee 100644 --- a/usr/src/man/man7d/cpqary3.7d +++ b/usr/src/man/man7d/cpqary3.7d @@ -11,11 +11,10 @@ .\" .\" Copyright (C) 2013 Hewlett-Packard Development Company, L.P. .\" -.TH CPQARY3 7D Aug 26, 2013" +.TH CPQARY3 7D "December 28, 2020" .SH NAME cpqary3 - provides disk and SCSI tape support for HP Smart Array controllers .SH DESCRIPTION -.LP The cpqary3 module provides low-level interface routines between the common disk I/O subsystem and the HP SMART Array controllers. The cpqary3 driver provides disk and SCSI tape support for the HP Smart Array controllers. @@ -32,7 +31,7 @@ controller can support up to 32 logical volumes. In addition, each controller supports up to a maximum of 28 connected SCSI tape drives. With 1.90 and later versions of cpqary3 driver, HP Smart Array SAS controllers, having Firmware Revision 5.10 or later, will support 64 logical drives. This -firmware also supports Dual Domian Multipath configurations. +firmware also supports Dual Domain Multipath configurations. .LP The driver attempts to initialize itself in accordance with the information found in the configuration file, /kernel/drv/cpqary3.conf. @@ -77,7 +76,6 @@ then target ID entries for tape drives from 65 to 65+N must be added in .BR sd (7D), .BR st (7D) .SH NOTES -.LP The Smart Array controllers supported by the current version of the cpqary3 driver do not support 'format unit' SCSI command. Hence, selecting \&'format' option under 'format' utility main menu is not supported. In addition, diff --git a/usr/src/man/man7i/vt.7i b/usr/src/man/man7i/vt.7i index c81860b4f2..67659e830b 100644 --- a/usr/src/man/man7i/vt.7i +++ b/usr/src/man/man7i/vt.7i @@ -14,7 +14,7 @@ .\" If applicable, add the following below this CDDL HEADER, with the .\" fields enclosed by brackets "[]" replaced with your own identifying .\" information: Portions Copyright [yyyy] [name of copyright owner] -.Dd October 29, 2017 +.Dd December 28, 2020 .Dt VT 7I .Os .Sh NAME @@ -277,7 +277,7 @@ to .Dv KD_TEXT or a VT of .Dv KD_TEXT -mode is actived from a previous active VT of +mode is activated from a previous active VT of .Dv KD_GRAPHICS mode, the virtual console manager initiates a .Dv KDSETMODE diff --git a/usr/src/man/man7p/ip6.7p b/usr/src/man/man7p/ip6.7p index c196466c81..c88233ed39 100644 --- a/usr/src/man/man7p/ip6.7p +++ b/usr/src/man/man7p/ip6.7p @@ -3,11 +3,10 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH IP6 7P "Dec 2, 2008" +.TH IP6 7P "December 28, 2020" .SH NAME ip6 \- Internet Protocol Version 6 .SH SYNOPSIS -.LP .nf #include <sys/socket.h> #include <netinet/in.h> @@ -25,8 +24,6 @@ t = t_open ("/dev/rawip6", O_RDWR); .fi .SH DESCRIPTION -.sp -.LP The \fBIPv6\fR protocol is the next generation of the internetwork datagram delivery protocol of the Internet protocol family. Programs may use \fBIPv6\fR through higher-level protocols such as the Transmission Control Protocol @@ -37,8 +34,6 @@ Transport Level Interface (\fBTLI\fR). The protocol options and \fBIPv6\fR extension headers defined in the \fBIPv6\fR specification may be set in outgoing datagrams. .SH APPLICATION PROGRAMMING INTERFACE -.sp -.LP The \fBSTREAMS\fR driver \fB/dev/rawip6\fR is the \fBTLI\fR transport provider that provides raw access to \fBIPv6\fR. .sp @@ -82,7 +77,7 @@ The socket options supported at the \fBIPv6\fR level are: .ad .RS 24n Limit reception and transmission of packets to this interface. Takes an integer -as an argument; the integer is the selected interace index. +as an argument; the integer is the selected interface index. .RE .sp @@ -578,8 +573,6 @@ reconstructed within a short time period. Errors in sending discovered at the network interface driver layer are passed by IPv6 back up to the user process. .SH SEE ALSO -.sp -.LP \fBsvcs\fR(1), \fBndd\fR(1M), \fBrouteadm\fR(1M), \fBsvcadm\fR(1M), \fBread\fR(2), \fBwrite\fR(2), \fBbind\fR(3SOCKET), \fBconnect\fR(3SOCKET), \fBgetsockopt\fR(3SOCKET), \fBrecv\fR(3SOCKET), \fBrecvmsg\fR(3SOCKET), @@ -596,8 +589,6 @@ Specification\fR. The Internet Society. December, 1998. Stevens, W., and Thomas, M. \fIRFC 2292, Advanced Sockets API for IPv6\fR. Network Working Group. February 1998. .SH DIAGNOSTICS -.sp -.LP A socket operation may fail with one of the following errors returned: .sp .ne 2 @@ -766,8 +757,6 @@ Invalid socket type for the option. .RE .SH NOTES -.sp -.LP Applications using the sockets \fBAPI\fR must use the Advanced Sockets \fBAPI\fR for \fBIPv6\fR (\fIRFC 2292\fR) to see elements of the inbound packet's \fBIPv6\fR header or extension headers. diff --git a/usr/src/man/man7p/pf_key.7p b/usr/src/man/man7p/pf_key.7p index 453dc81aa0..1c904048f4 100644 --- a/usr/src/man/man7p/pf_key.7p +++ b/usr/src/man/man7p/pf_key.7p @@ -4,11 +4,10 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH PF_KEY 7P "Jan 12, 2018" +.TH PF_KEY 7P "December 28, 2020" .SH NAME pf_key \- Security association database interface .SH SYNOPSIS -.LP .nf #include <sys/types.h> #include <sys/socket.h> @@ -20,7 +19,6 @@ pf_key \- Security association database interface .fi .SH DESCRIPTION -.LP Keying information for IPsec security services is maintained in security association databases (\fBSADB\fRs). The security associations (\fBSA\fRs) are used to protect both inbound and outbound packets. @@ -52,7 +50,6 @@ message and all extensions must be eight-byte aligned. An example message is the \fBGET\fR message, which requires the base header, the \fBSA \fRextension, and the \fBADDRESS_DST\fR extension. .SS "Messages" -.LP Messages include: .sp .in +2 @@ -229,7 +226,7 @@ struct sadb_key { .fi .in -2 -.SS "Indentity Extension" +.SS "Identity Extension" .in +2 .nf struct sadb_ident { @@ -411,7 +408,6 @@ struct sadb_x_pair { .in -2 .SS "Message Use and Behavior" -.LP Each message has a behavior. A behavior is defined as where the initial message travels, for example, user to kernel, and what subsequent actions are expected to take place. Contents of messages are illustrated as: @@ -512,7 +508,6 @@ Message exceeds the maximum length allowed. .LP The following are examples of message use and behavior: .SS "\fBSADB_GETSPI\fR" -.LP Send a \fBSADB_GETSPI\fR message from a user process to the kernel. .sp .in +2 @@ -532,7 +527,6 @@ The kernel returns the \fBSADB_GETSPI\fR message to all listening processes. .in -2 .SS "\fBSADB_UPDATE\fR" -.LP Send a \fBSADB_UPDATE\fR message from a user process to the kernel. .sp .in +2 @@ -560,7 +554,6 @@ security association contained in that extension. The resulting security association "pair" can be updated or as a single entity using the \fBSADB_X_UPDATEPAIR\fR or \fBSADB_X_DELPAIR\fR message types. .SS "\fBSADB_ADD\fR" -.LP Send a \fBSADB_ADD\fR message from a user process to the kernel. .sp .in +2 @@ -582,7 +575,6 @@ The kernel returns the \fBSADB_ADD\fR message to all listening processes. .in -2 .SS "\fBSADB_X_UPDATEPAIR\fR" -.LP Send a \fBSADB_X_UPDATEPAIR\fR message from a user process to the kernel. This message type is used to update the lifetime values of a security association and the lifetime values of the security association it is paired @@ -595,7 +587,6 @@ with. .in -2 .SS "\fBSADB_DELETE | SADB_X_DELPAIR\fR" -.LP Send a \fBSADB_DELETE\fR message from a user process to the kernel. The \fBSADB_X_DELPAIR\fR message type will request deletion of the security association and the security association it is paired with. @@ -617,7 +608,6 @@ The kernel returns the \fBSADB_DELETE\fR message to all listening processes. .in -2 .SS "\fBSADB_GET\fR" -.LP Send a \fBSADB_GET\fR message from a user process to the kernel. .sp .in +2 @@ -639,7 +629,6 @@ The kernel returns the \fBSADB_GET\fR message to the socket that sent the .in -2 .SS "\fBSADB_ACQUIRE\fR" -.LP The kernel sends a \fBSADB_ACQUIRE\fR message to registered sockets. Note that any \fBGETSPI\fR, \fBADD\fR, or \fBUPDATE\fR calls in reaction to an \fBACQUIRE\fR must fill in the \fBsadb_msg_seq\fR of those messages with the @@ -678,7 +667,6 @@ If key management fails, send an \fBSADB_ACQUIRE\fR to indicate failure. .in -2 .SS "\fBSADB_X_INVERSE_ACQUIRE\fR" -.LP For inbound Key Management processing, a Key Management application may wish to consult the kernel for its policy. The application should send to the kernel: .sp @@ -700,7 +688,6 @@ The kernel returns a message similar to a kernel-generated extended ACQUIRE: .in -2 .SS "\fBSADB_REGISTER\fR" -.LP Send a \fBSADB_REGISTER\fR message from a user process to the kernel. .sp .in +2 @@ -738,7 +725,6 @@ extended ACQUIREs. Which returns a series of SADB_REGISTER replies (one for each security protocol registered) from the kernel. .SS "\fBSADB_EXPIRE\fR" -.LP The kernel sends a \fBSADB_EXPIRE\fR message to all listeners when the soft limit of a security association has been expired. .sp @@ -749,7 +735,6 @@ limit of a security association has been expired. .in -2 .SS "\fBSADB_FLUSH\fR" -.LP Send a \fBSADB_FLUSH\fR message from a user process to the kernel. .sp .in +2 @@ -769,7 +754,6 @@ The kernel returns the \fBSADB_FLUSH\fR message to all listening sockets. .in -2 .SS "\fBSADB_DUMP\fR" -.LP Send a \fBSADB_DUMP\fR message from a user process to the kernel. .sp .in +2 @@ -802,7 +786,6 @@ To mark the end of a dump a single base header arrives with its .in -2 .SS "\fBSADB_X_PROMISC\fR" -.LP Send a \fBSADB_X_PROMISC\fR message from a user process to the kernel. .sp .in +2 @@ -822,7 +805,6 @@ The kernel returns the \fBSADB_X_PROMISC\fR message to all listening processes. .in -2 .SH DIAGNOSTICS -.LP The message returning from the kernel will contain a diagnostic value in the base message header, the diagnostic value will indicate if action requested by the original message was a success. @@ -939,7 +921,6 @@ Diagnostic Values: .in -2 .SH ATTRIBUTES -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp @@ -953,7 +934,6 @@ Interface Stability Evolving .TE .SH SEE ALSO -.LP \fBin.iked\fR(1M), \fBipseckey\fR(1M), \fBsockaddr\fR(3SOCKET), \fBipsec\fR(7P), \fBipsecah\fR(7P), \fBipsecesp\fR(7P), \fBroute\fR(7P), \fBudp\fR(7P) @@ -962,6 +942,5 @@ Interface Stability Evolving McDonald, D.L., Metz, C.W., and Phan, B.G., \fIRFC 2367, PF_KEY Key Management API, Version 2\fR, The Internet Society, July 1998. .SH NOTES -.LP Time-based lifetimes may not expire with exact precision in seconds because kernel load may affect the aging of \fBSA\fR's. diff --git a/usr/src/man/man9f/usb_pipe_close.9f b/usr/src/man/man9f/usb_pipe_close.9f index 571ca577ca..65de310245 100644 --- a/usr/src/man/man9f/usb_pipe_close.9f +++ b/usr/src/man/man9f/usb_pipe_close.9f @@ -4,11 +4,10 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH USB_PIPE_CLOSE 9F "Sep 16, 2016" +.TH USB_PIPE_CLOSE 9F "December 28, 2020" .SH NAME usb_pipe_close \- Close and cleanup a USB device pipe .SH SYNOPSIS -.LP .nf #include <sys/usb/usba.h> @@ -22,7 +21,6 @@ usb_pipe_close \- Close and cleanup a USB device pipe .fi .SH INTERFACE LEVEL -.LP Solaris DDI specific (Solaris DDI) .SH PARAMETERS .ne 2 @@ -72,7 +70,6 @@ Second argument to callback function. .RE .SH DESCRIPTION -.LP The \fBusb_pipe_close()\fR function closes the pipe pointed to by \fIpipe_handle\fR, releases all related resources and then frees the pipe handle. This function stops polling if the pipe to be closed is an interrupt-IN @@ -155,9 +152,8 @@ Error starting asynchronous request. .RE .SH RETURN VALUES -.LP Status is returned to the caller via the callback handler's rval argument. -Possible callback hander rval argument values are: +Possible callback handler rval argument values are: .sp .ne 2 .na @@ -201,7 +197,7 @@ Pipe handle specifies the default control pipe. .ad .RS 23n Asynchronous resources are unavailable. In this case, USB_CB_ASYNC_REQ_FAILED -is passed in as the \fIcallback_flags\fR arg to the callback hander. +is passed in as the \fIcallback_flags\fR arg to the callback handler. .RE .sp @@ -215,7 +211,6 @@ Note that messages mirroring the above errors are logged to the console logfile on error. (This provides status for calls which otherwise could provide status). .SH CONTEXT -.LP May be called from user or kernel context regardless of arguments. May not be called from a callback executing in interrupt context. Please see \fBusb_callback_flags\fR(9S) for more information on callbacks. @@ -243,7 +238,6 @@ usb_pipe_close(dip, pipe, 0, close_callback, callback_arg); .in -2 .SH ATTRIBUTES -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp @@ -260,7 +254,6 @@ Interface stability Committed .TE .SH SEE ALSO -.LP \fBattributes\fR(5), \fBusb_get_status\fR(9F), \fBusb_pipe_drain_reqs\fR(9F), \fBusb_pipe_get_state\fR(9F), \fBusb_pipe_xopen\fR(9F), \fBusb_pipe_reset\fR(9F), \fBusb_callback_flags\fR(9S) diff --git a/usr/src/man/man9f/usb_pipe_reset.9f b/usr/src/man/man9f/usb_pipe_reset.9f index 5f7a516613..6bba298b4b 100644 --- a/usr/src/man/man9f/usb_pipe_reset.9f +++ b/usr/src/man/man9f/usb_pipe_reset.9f @@ -3,11 +3,10 @@ .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH USB_PIPE_RESET 9F "Sep 16, 2016" +.TH USB_PIPE_RESET 9F "December 28, 2020" .SH NAME usb_pipe_reset \- Abort queued requests from a USB pipe and reset the pipe .SH SYNOPSIS -.LP .nf #include <sys/usb/usba.h> @@ -19,7 +18,6 @@ usb_pipe_reset \- Abort queued requests from a USB pipe and reset the pipe .fi .SH INTERFACE LEVEL -.LP Solaris DDI specific (Solaris DDI) .SH PARAMETERS .ne 2 @@ -68,7 +66,6 @@ Second argument to callback function. .RE .SH DESCRIPTION -.LP Call \fBusb_pipe_reset()\fR to reset a pipe which is in an error state, or to abort a current request and clear the pipe. The \fBusb_pipe_reset()\fR function can be called on any pipe other than the default control pipe. @@ -158,9 +155,8 @@ USB_CB_ASYNC_REQ_FAILED \(em Error starting asynchronous request. .RE .SH RETURN VALUES -.LP Status is returned to the caller via the callback handler's rval argument. -Possible callback hander rval argument values are: +Possible callback handler rval argument values are: .sp .ne 2 .na @@ -214,7 +210,7 @@ Called from interrupt context with the USB_FLAGS_SLEEP flag set. .ad .RS 23n Asynchronous resources are unavailable. In this case, USB_CB_ASYNC_REQ_FAILED -is passed in as the \fIcallback_flags\fR arg to the callback hander. +is passed in as the \fIcallback_flags\fR arg to the callback handler. .RE .sp @@ -235,7 +231,6 @@ Note that messages mirroring the above errors are logged to the console logfile on error. This provides status for calls which could not otherwise provide status. .SH CONTEXT -.LP May be called from user or kernel context regardless of arguments. May be called from any callback with the USB_FLAGS_SLEEP clear. May not be called from a callback executing in interrupt context if the USB_FLAGS_SLEEP flag is set. @@ -264,7 +259,6 @@ usb_pipe_reset(dip, bulk_pipe, USB_FLAGS_SLEEP, NULL, NULL); .in -2 .SH ATTRIBUTES -.LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp @@ -281,7 +275,6 @@ Interface stability Committed .TE .SH SEE ALSO -.LP \fBattributes\fR(5), \fBusb_get_cfg\fR(9F), \fBusb_pipe_bulk_xfer\fR(9F), \fBusb_pipe_close\fR(9F), \fBusb_get_status\fR(9F), \fBusb_pipe_ctrl_xfer\fR(9F), \fBusb_pipe_drain_reqs\fR(9F), |