summaryrefslogtreecommitdiff
path: root/usr/src/man/man1m
diff options
context:
space:
mode:
Diffstat (limited to 'usr/src/man/man1m')
-rw-r--r--usr/src/man/man1m/etrn.1m35
-rw-r--r--usr/src/man/man1m/idmap.1m44
-rw-r--r--usr/src/man/man1m/ipseckey.1m40
-rw-r--r--usr/src/man/man1m/kadmin.1m97
-rw-r--r--usr/src/man/man1m/kclient.1m47
-rw-r--r--usr/src/man/man1m/kdb5_util.1m13
-rw-r--r--usr/src/man/man1m/ksslcfg.1m24
-rw-r--r--usr/src/man/man1m/ldapclient.1m45
-rw-r--r--usr/src/man/man1m/lpset.1m15
-rw-r--r--usr/src/man/man1m/mount_smbfs.1m31
-rw-r--r--usr/src/man/man1m/pppd.1m45
-rw-r--r--usr/src/man/man1m/share_nfs.1m8
-rw-r--r--usr/src/man/man1m/sharectl.1m20
-rw-r--r--usr/src/man/man1m/sharemgr.1m15
14 files changed, 140 insertions, 339 deletions
diff --git a/usr/src/man/man1m/etrn.1m b/usr/src/man/man1m/etrn.1m
index ddb147e465..76665411eb 100644
--- a/usr/src/man/man1m/etrn.1m
+++ b/usr/src/man/man1m/etrn.1m
@@ -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 ETRN 1M "Aug 10, 2004"
+.TH ETRN 1M "November 22, 2021"
.SH NAME
etrn \- start mail queue run
.SH SYNOPSIS
-.LP
.nf
\fBetrn\fR [\fB-b\fR] [\fB-v\fR] \fIserver-host\fR [\fIclient-hosts\fR]
.fi
.SH DESCRIPTION
-.sp
-.LP
SMTP's \fBETRN\fR command allows an SMTP client and server to interact, giving
the server an opportunity to start the processing of its queues for messages to
go to a given host. This is meant to be used in start-up conditions, as well as
@@ -29,8 +26,6 @@ command with that name as the argument. If any \fIclient-hosts\fR are
specified, \fBetrn\fR uses each of these as arguments for successive \fBETRN\fR
commands.
.SH OPTIONS
-.sp
-.LP
The following options are supported:
.sp
.ne 2
@@ -59,8 +54,6 @@ conversations with the remote SMTP server.
.RE
.SH ENVIRONMENT VARIABLES
-.sp
-.LP
No environment variables are used. However, at system start-up,
\fBsvc:/network/smtp:sendmail\fR reads \fB/etc/default/sendmail\fR. In this
file, if the variable \fBETRN_HOSTS\fR is set, \fBsvc:/network/smtp:sendmail\fR
@@ -92,7 +85,6 @@ for each \fIclient\fR name. This is comparable to running:
.LP
on the host \fIserver\fR.
.SH EXAMPLES
-.LP
\fBExample 1 \fRUsing \fBetrn\fR
.sp
.LP
@@ -101,7 +93,7 @@ Inserting the line:
.sp
.in +2
.nf
-ETRN_HOSTS="s1.domain.com:clnt.domain.com s2.domain.com:clnt.domain.com"
+ETRN_HOSTS="s1.example.com:clnt.example.com s2.example.com:clnt.example.com"
.fi
.in -2
.sp
@@ -110,8 +102,8 @@ ETRN_HOSTS="s1.domain.com:clnt.domain.com s2.domain.com:clnt.domain.com"
.LP
in \fB/etc/default/sendmail\fR results in \fBsvc:/network/smtp:sendmail\fR
invoking \fBetrn\fR such that \fBETRN\fR commands are sent to both
-\fBs1.domain.com\fR and \fBs2.domain.com\fR, with both having
-\fBclnt.domain.com\fR as the \fBETRN\fR argument.
+\fBs1.example.com\fR and \fBs2.example.com\fR, with both having
+\fBclnt.example.com\fR as the \fBETRN\fR argument.
.sp
.LP
@@ -120,16 +112,16 @@ The line:
.sp
.in +2
.nf
-ETRN_HOSTS="server.domain.com:client1.domain.com,client2.domain.com"
+ETRN_HOSTS="server.example.com:client1.example.com,client2.example.com"
.fi
.in -2
.sp
.sp
.LP
-results in two \fBETRN\fR commands being sent to \fBserver.domain.com\fR, one
-with the argument \fBclient1.domain.com\fR, the other with the argument
-\fBclient2.domain.com\fR.
+results in two \fBETRN\fR commands being sent to \fBserver.example.com\fR, one
+with the argument \fBclient1.example.com\fR, the other with the argument
+\fBclient2.example.com\fR.
.sp
.LP
@@ -138,7 +130,7 @@ The line:
.sp
.in +2
.nf
-ETRN_HOSTS="server1.domain.com server2.domain.com"
+ETRN_HOSTS="server1.example.com server2.example.com"
.fi
.in -2
.sp
@@ -146,12 +138,11 @@ ETRN_HOSTS="server1.domain.com server2.domain.com"
.sp
.LP
results in set of a \fBETRN\fR commands being sent to both
-\fBserver1.domain.com\fR and \fBserver2.domain.com\fR; each set contains one
+\fBserver1.example.com\fR and \fBserver2.example.com\fR; each set contains one
\fBETRN\fR command for each host name for which \fBsendmail\fR(1M) accepts
email, with that host name as the argument.
.SH FILES
-.sp
.ne 2
.na
\fB\fB/etc/mail/sendmail.cf\fR\fR
@@ -170,8 +161,6 @@ Variables used by \fBsvc:/network/smtp:sendmail\fR
.RE
.SH ATTRIBUTES
-.sp
-.LP
See \fBattributes\fR(5) for descriptions of the following attributes:
.sp
@@ -186,13 +175,9 @@ Interface Stability Stable
.TE
.SH SEE ALSO
-.sp
-.LP
\fBsendmail\fR(1M), \fBattributes\fR(5)
.sp
.LP
RFC 1985
.SH NOTES
-.sp
-.LP
Not all SMTP servers support \fBETRN\fR.
diff --git a/usr/src/man/man1m/idmap.1m b/usr/src/man/man1m/idmap.1m
index 7854c02708..585760e0fd 100644
--- a/usr/src/man/man1m/idmap.1m
+++ b/usr/src/man/man1m/idmap.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 IDMAP 1M "Aug 3, 2009"
+.TH IDMAP 1M "November 22, 2021"
.SH NAME
idmap \- configure and manage the Native Identity Mapping service
.SH SYNOPSIS
-.LP
.nf
\fBidmap\fR
.fi
@@ -85,8 +84,6 @@ idmap \- configure and manage the Native Identity Mapping service
.fi
.SH DESCRIPTION
-.sp
-.LP
The \fBidmap\fR utility is used to configure and manage the Native Identity
Mapping service.
.sp
@@ -125,8 +122,6 @@ If the \fBidmap\fR utility is invoked without a subcommand or option, it reads
the subcommands from standard input. When standard input is a TTY, the
\fBidmap\fR command prints the usage message and exits.
.SS "Mapping Mechanisms"
-.sp
-.LP
The \fBidmapd\fR(1M) daemon maps Windows user and group SIDs to UNIX UIDs and
GIDs as follows:
.RS +4
@@ -160,8 +155,6 @@ Windows groups and Solaris users and between Solaris groups and Windows users.
They are needed when Windows uses a group identity as a file owner or vice
versa.
.SS "Name-based Mappings"
-.sp
-.LP
Name-based mappings establish name equivalence between Windows users and groups
and their counterparts in the UNIX name service. These mappings persist across
reboots. For example, the following command maps Windows users to UNIX users
@@ -169,7 +162,7 @@ with the same name:
.sp
.in +2
.nf
-# \fBidmap add "winuser:*@mywindomain.com" "unixuser:*"\fR
+# \fBidmap add "winuser:*@example.com" "unixuser:*"\fR
.fi
.in -2
.sp
@@ -250,8 +243,6 @@ add winname:fred@example.com unixuser:fredf
.sp
.SS "Ephemeral Mappings"
-.sp
-.LP
The \fBidmapd\fR daemon attempts to preserve ephemeral ID mappings across
daemon restarts. However, when IDs cannot be preserved, the daemon maps each
previously mapped SID to a new ephemeral UID or GID value. The daemon will
@@ -264,8 +255,6 @@ The dynamic ID mappings are not retained across reboots. So, any SIDs that are
dynamically mapped to UNIX UIDs or GIDs are most likely mapped to different IDs
after rebooting the system.
.SS "Local SID Mappings"
-.sp
-.LP
If no name-based mapping is found, a non-ephemeral UID or GID is mapped to an
algorithmically generated local SID. The mapping is generated as follows:
.sp
@@ -282,8 +271,6 @@ local SID for GID = \fI<machine SID>\fR - \fI<2^31 + GID>\fR
\fI<machine SID>\fR is a unique SID generated by the \fBidmap\fR service for
the host on which it runs.
.SS "Rule Lookup Order"
-.sp
-.LP
When mapping a Windows name to a UNIX name, lookup for name-based mapping rules
is performed in the following order:
.RS +4
@@ -366,8 +353,6 @@ is performed in the following order:
\fB*\fR to \fIwindows-name\fR\fB@\fR\fIdomain\fR
.RE
.SS "Service Properties"
-.sp
-.LP
The service properties determine the behavior of the \fBidmapd\fR(1M) daemon.
These properties are stored in the SMF repository (see \fBsmf\fR(5)) under
property group \fBconfig\fR. They can be accessed and modified using
@@ -432,8 +417,6 @@ Changes to service properties do not affect a running \fBidmap\fR service. The
service must be refreshed (with \fBsvcadm\fR(1M)) for the changes to take
effect.
.SH OPERANDS
-.sp
-.LP
The \fBidmap\fR command uses the following operands:
.sp
.ne 2
@@ -697,12 +680,9 @@ attribute within the object specified by the \fIname\fR operand.
.RE
.SH OPTIONS
-.sp
-.LP
The \fBidmap\fR command supports one option and a set of subcommands. The
subcommands also have options.
.SS "Command-Line Option"
-.sp
.ne 2
.na
\fB\fB-f\fR \fIcommand-file\fR\fR
@@ -715,8 +695,6 @@ not used by any subcommands.
.RE
.SS "Subcommands"
-.sp
-.LP
The following subcommands are supported:
.sp
.ne 2
@@ -947,11 +925,10 @@ See the \fBset-namemap\fR subcommand for options.
.RE
.SH EXAMPLES
-.LP
\fBExample 1 \fRUsing a Wildcard on Both Sides of a Name-Based Mapping Rule
.sp
.LP
-The following command maps all Windows user names in the \fBxyz.com\fR domain
+The following command maps all Windows user names in the \fBexample.com\fR domain
to the UNIX users with the same names provided that one exists and is not
otherwise mapped. If such a rule is matched but the UNIX user name does not
exist, an ephemeral ID mapping is used.
@@ -959,7 +936,7 @@ exist, an ephemeral ID mapping is used.
.sp
.in +2
.nf
-# \fBidmap add "winuser:*@xyz.com" "unixuser:*"\fR
+# \fBidmap add "winuser:*@example.com" "unixuser:*"\fR
.fi
.in -2
.sp
@@ -968,14 +945,14 @@ exist, an ephemeral ID mapping is used.
\fBExample 2 \fRUsing a Wildcard on One Side of a Name-Based Mapping Rule
.sp
.LP
-The following command maps all unmapped Windows users in the \fBxyz.com\fR
+The following command maps all unmapped Windows users in the \fBexample.com\fR
domain to the \fBguest\fR UNIX user. The \fB-d\fR option specifies a
-unidirectional mapping from \fB*@xyz.com\fR users to the \fBguest\fR user.
+unidirectional mapping from \fB*@example.com\fR users to the \fBguest\fR user.
.sp
.in +2
.nf
-# \fBidmap add -d "winuser:*@xyz.com" unixuser:guest\fR
+# \fBidmap add -d "winuser:*@example.com" unixuser:guest\fR
.fi
.in -2
.sp
@@ -1249,7 +1226,6 @@ object representing \fBjoe@example.com\fR.
.sp
.SH EXIT STATUS
-.sp
.ne 2
.na
\fB\fB0\fR\fR
@@ -1268,8 +1244,6 @@ An error occurred. A diagnostic message is written to standard error.
.RE
.SH ATTRIBUTES
-.sp
-.LP
See \fBattributes\fR(5) for descriptions of the following attributes:
.sp
@@ -1284,13 +1258,9 @@ Interface Stability Uncommitted
.TE
.SH SEE ALSO
-.sp
-.LP
\fBsvcs\fR(1), \fBidmapd\fR(1M), \fBldapaddent\fR(1M), \fBsvcadm\fR(1M),
\fBsvccfg\fR(1M), \fBattributes\fR(5), \fBsmf\fR(5)
.SH NOTES
-.sp
-.LP
The \fBidmapd\fR service is managed by the service management facility,
\fBsmf\fR(5). The service identifier for the \fBidmapd\fR service is
\fBsvc:/system/idmap\fR.
diff --git a/usr/src/man/man1m/ipseckey.1m b/usr/src/man/man1m/ipseckey.1m
index a76e99d9ab..180635151b 100644
--- a/usr/src/man/man1m/ipseckey.1m
+++ b/usr/src/man/man1m/ipseckey.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 IPSECKEY 1M "Sep 25, 2008"
+.TH IPSECKEY 1M "November 22, 2021"
.SH NAME
ipseckey \- manually manipulate an IPsec Security Association Database (SADB)
.SH SYNOPSIS
-.LP
.nf
\fBipseckey\fR [\fB-nvp\fR]
.fi
@@ -53,8 +52,6 @@ ipseckey \- manually manipulate an IPsec Security Association Database (SADB)
.fi
.SH DESCRIPTION
-.sp
-.LP
The \fBipseckey\fR command is used to manually manipulate the security
association databases of the network security services, \fBipsecah\fR(7P) and
\fBipsecesp\fR(7P). You can use the \fBipseckey\fR command to set up security
@@ -81,7 +78,6 @@ types.
\fBipseckey\fR handles sensitive cryptographic keying information. Please read
the \fBSecurity\fR section for details on how to use this command securely.
.SH OPTIONS
-.sp
.ne 2
.na
\fB\fB-c\fR [\fIfilename\fR]\fR
@@ -158,7 +154,6 @@ raw seconds values for lifetimes.
.RE
.SH COMMANDS
-.sp
.ne 2
.na
\fB\fBadd\fR\fR
@@ -313,7 +308,6 @@ Prints a brief summary of commands.
.RE
.SS "\fBSA_TYPE\fR"
-.sp
.ne 2
.na
\fB\fBall\fR\fR
@@ -346,8 +340,6 @@ Specifies the IPsec Encapsulating Security Payload ("\fBESP\fR") \fBSA\fR.
.RE
.SH EXTENSION VALUE TYPES
-.sp
-.LP
Commands like \fBadd\fR, \fBdelete\fR, \fBget\fR, and \fBupdate\fR require that
certain extensions and associated values be specified. The extensions will be
listed here, followed by the commands that use them, and the commands that
@@ -1015,14 +1007,10 @@ is used by the \fBadd\fR and \fBupdate\fR commands
.RE
.SS "Tunnel Mode versus Transport Mode SAs"
-.sp
-.LP
An IPsec SA is a Tunnel Mode SA if the "proto" value is either 4 (\fBipip\fR)
or 41 (\fBipv6\fR) \fBand\fR there is an inner-address or inner-port value
specified. Otherwise, the SA is a Transport Mode SA.
.SH SECURITY
-.sp
-.LP
Keying material is very sensitive and should be generated as randomly as
possible. Some algorithms have known weak keys. IPsec algorithms have built-in
weak key checks, so that if a weak key is in a newly added \fBSA\fR, the
@@ -1103,8 +1091,6 @@ For further thoughts on this subject, see the afterward by Matt Blaze in Bruce
Schneier's \fIApplied Cryptography: Protocols, Algorithms, and Source Code in
C\fR.
.SS "Service Management Facility"
-.sp
-.LP
IPsec manual keys are managed by the service management facility, \fBsmf\fR(5).
The services listed below manage the components of IPsec. These services are
delivered as follows:
@@ -1244,7 +1230,6 @@ discouraged. If the \fBipseckey\fR command is to be run from the command line,
the \fBmanual-key\fR \fBsmf\fR(5) service should be disabled first. See
\fBsvcadm\fR(1M).
.SH EXAMPLES
-.LP
\fBExample 1 \fREmptying Out All \fBSA\fRs
.sp
.LP
@@ -1352,9 +1337,9 @@ Adding or updating \fBSA\fRs requires entering interactive mode:
.in +2
.nf
example# \fBipseckey\fR
-ipseckey> \fBadd ah spi 0x90125 src me.domain.com dst you.domain.com \e
+ipseckey> \fBadd ah spi 0x90125 src me.example.com dst you.example.com \e
authalg md5 authkey 1234567890abcdef1234567890abcdef\fR
-ipseckey> \fBupdate ah spi 0x90125 dst you.domain.com hard_bytes \e
+ipseckey> \fBupdate ah spi 0x90125 dst you.example.com hard_bytes \e
16000000\fR
ipseckey> \fBexit\fR
.fi
@@ -1369,10 +1354,10 @@ Adding two SAs that are linked together as a pair:
.in +2
.nf
example# \fBipseckey\fR
-ipseckey> \fBadd esp spi 0x2345 src me.domain.com dst you.domain.com \e
+ipseckey> \fBadd esp spi 0x2345 src me.example.com dst you.example.com \e
authalg md5 authkey bde359723576fdea08e56cbe876e24ad \e
encralg des encrkey be02938e7def2839\fR
-ipseckey> \fBadd esp spi 0x5432 src me.domain.com dst you.domain.com \e
+ipseckey> \fBadd esp spi 0x5432 src me.example.com dst you.example.com \e
authalg md5 authkey bde359723576fdea08e56cbe876e24ad \e
encralg des encrkey be02938e7def2839 pair-spi 0x2345\fR
ipseckey> \fBexit\fR
@@ -1392,7 +1377,7 @@ also needs to add both \fBSA\fRs.
.in +2
.nf
example# \fBipseckey\fR
-ipseckey> \fBadd ah spi 0x2112 src you.domain.com dst me.domain.com \e
+ipseckey> \fBadd ah spi 0x2112 src you.example.com dst me.example.com \e
authalg md5 authkey bde359723576fdea08e56cbe876e24ad \e
hard_bytes 16000000\fR
ipseckey> \fBexit\fR
@@ -1434,10 +1419,10 @@ flush esp
### SECURITY section in this manual page for why this can be
### dangerous .
-add esp spi 0x2112 src me.domain.com dst you.domain.com \e
+add esp spi 0x2112 src me.example.com dst you.example.com \e
authalg md5 authkey bde359723576fdea08e56cbe876e24ad \e
encralg des encrkey be02938e7def2839 hard_usetime 28800
-add esp spi 0x5150 src you.domain.com dst me.domain.com \e
+add esp spi 0x5150 src you.example.com dst me.example.com \e
authalg md5 authkey 930987dbe09743ade09d92b4097d9e93 \e
encralg des encrkey 8bd4a52e10127deb hard_usetime 28800
@@ -1480,7 +1465,6 @@ pair-spi 0x654321\fR
.sp
.SH FILES
-.sp
.ne 2
.na
\fB\fB/etc/inet/secret/ipseckeys\fR\fR
@@ -1492,8 +1476,6 @@ and \fBSECURITY\fR for more information.
.RE
.SH ATTRIBUTES
-.sp
-.LP
See \fBattributes\fR(5) for descriptions of the following attributes:
.sp
@@ -1507,8 +1489,6 @@ Interface Stability Committed
.TE
.SH SEE ALSO
-.sp
-.LP
\fBps\fR(1), \fBsvcprop\fR(1), \fBsvcs\fR(1), \fBipsecconf\fR(1M),
\fBipsecalgs\fR(1M), \fBroute\fR(1M), \fBsvcadm\fR(1M), \fBsvccfg\fR(1M),
\fBike.config\fR(4), \fBattributes\fR(5), \fBsmf\fR(5), \fBipsec\fR(7P),
@@ -1518,8 +1498,6 @@ Interface Stability Committed
Schneier, B., \fIApplied Cryptography: Protocols, Algorithms, and Source Code
in C\fR. Second ed. New York, New York: John Wiley & Sons, 1996.
.SH DIAGNOSTICS
-.sp
-.LP
The \fBipseckey\fR command parses the configuration file and reports any
errors. In the case of multiple errors, \fBipseckey\fR reports as many of these
as possible.
@@ -1629,8 +1607,6 @@ provides more detail about what precise value was incorrect and why.
.RE
.SH NOTES
-.sp
-.LP
In spite of its IPsec-specific name, \fBipseckey\fR is analogous to
\fBroute\fR(1M), in that it is a command-line interface to a socket-based
administration engine, in this case, \fBPF_KEY\fR. \fBPF_KEY\fR was originally
diff --git a/usr/src/man/man1m/kadmin.1m b/usr/src/man/man1m/kadmin.1m
index d906fc4f0a..0a9106ee2d 100644
--- a/usr/src/man/man1m/kadmin.1m
+++ b/usr/src/man/man1m/kadmin.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 KADMIN 1M "Oct 29, 2015"
+.TH KADMIN 1M "November 22, 2021"
.SH NAME
kadmin, kadmin.local \- Kerberos database administration program
.SH SYNOPSIS
-.LP
.nf
\fB/usr/sbin/kadmin\fR [\fB-r\fR \fIrealm\fR] [\fB-p\fR \fIprincipal\fR] [\fB-q\fR \fIquery\fR]
[\fB-s\fR \fIadmin_server\fR [\fI:port\fR]] [ [\fB-c\fR \fIcredential_cache\fR]
@@ -21,8 +20,6 @@ kadmin, kadmin.local \- Kerberos database administration program
.fi
.SH DESCRIPTION
-.sp
-.LP
\fBkadmin\fR and \fBkadmin.local\fR are interactive command-line interfaces to
the Kerberos V5 administration system. They provide for the maintenance of
Kerberos principals, policies, and service key tables (keytabs). \fBkadmin\fR
@@ -62,8 +59,6 @@ file (see \fBkdb5_util\fR(1M)) to decrypt information from the database rather
than prompting for a password. The \fB-m\fR option will bypass the
\fB\&.k5.\fR\fIrealm\fR stash file and prompt for the master password.
.SH OPTIONS
-.sp
-.LP
The following options are supported:
.sp
.ne 2
@@ -254,7 +249,6 @@ Directory server connection port.
.RE
.SH COMMANDS
-.sp
.ne 2
.na
\fB\fBlist_requests\fR\fR
@@ -573,11 +567,11 @@ des-cbc-crc:normal.
.in +2
.nf
kadmin: \fBaddprinc tlyu/admin\fR
-WARNING: no policy specified for "tlyu/admin@ACME.COM";
+WARNING: no policy specified for "tlyu/admin@EXAMPLE.COM";
defaulting to no policy.
-Enter password for principal tlyu/admin@ACME.COM:
-Re-enter password for principal tlyu/admin@ACME.COM:
-Principal "tlyu/admin@ACME.COM" created.
+Enter password for principal tlyu/admin@EXAMPLE.COM:
+Re-enter password for principal tlyu/admin@EXAMPLE.COM:
+Principal "tlyu/admin@EXAMPLE.COM" created.
kadmin:
.fi
.in -2
@@ -627,8 +621,8 @@ deletion, unless the \fB-force\fR option is given. This command requires the
.nf
kadmin: \fBdelprinc mwm_user\fR
Are you sure you want to delete the principal
-"mwm_user@ACME.COM"? (yes/no): \fByes\fR
-Principal "mwm_user@ACME.COM" deleted.
+"mwm_user@EXAMPLE.COM"? (yes/no): \fByes\fR
+Principal "mwm_user@EXAMPLE.COM" deleted.
Make sure that you have removed this principal from
all kadmind ACLs before reusing.
kadmin:
@@ -749,9 +743,9 @@ will allow existing valid TGTs to continue to work.
.in +2
.nf
kadmin: \fBcpw systest\fR
-Enter password for principal systest@ACME.COM:
-Re-enter password for principal systest@ACME.COM:
-Password for systest@ACME.COM changed.
+Enter password for principal systest@EXAMPLE.COM:
+Re-enter password for principal systest@EXAMPLE.COM:
+Password for systest@EXAMPLE.COM changed.
kadmin:
.fi
.in -2
@@ -801,13 +795,13 @@ tab-separated strings. Aliased by \fBgetprinc\fR.
.in +2
.nf
kadmin: \fBgetprinc tlyu/admin\fR
-Principal: tlyu/admin@ACME.COM
+Principal: tlyu/admin@EXAMPLE.COM
Expiration date: [never]
Last password change: Thu Jan 03 12:17:46 CET 2008
Password expiration date: [none]
Maximum ticket life: 24855 days 03:14:07
Maximum renewable life: 24855 days 03:14:07
-Last modified: Thu Jan 03 12:17:46 CET 2008 (root/admin@ACME.COM)
+Last modified: Thu Jan 03 12:17:46 CET 2008 (root/admin@EXAMPLE.COM)
Last successful authentication: [never]
Last failed authentication: [never]
Failed password attempts: 0
@@ -820,8 +814,8 @@ Key: vno 2, DES cbc mode with RSA-MD5, no salt
Attributes: REQUIRES_PRE_AUTH
Policy: [none]
kadmin: \fBgetprinc -terse tlyu/admin\fR
-"tlyu/admin@ACME.COM" 0 1199359066 0 2147483647
-"root/admin@ACME.COM" 1199359066 128 2 0 "[none]" 21474836
+"tlyu/admin@EXAMPLE.COM" 0 1199359066 0 2147483647
+"root/admin@EXAMPLE.COM" 1199359066 128 2 0 "[none]" 21474836
47 0 0 0 5 1 2 18 0 1 2
17 0 1 2 16 0 1 2 23 0 12
3 0
@@ -871,10 +865,10 @@ the expression. Requires the \fBlist\fR privilege. Aliased by \fBlistprincs\fR,
.in +2
.nf
kadmin: \fBlistprincs test*\fR
-test3@ACME.COM
-test2@ACME.COM
-test1@ACME.COM
-testuser@ACME.COM
+test3@EXAMPLE.COM
+test2@EXAMPLE.COM
+test1@EXAMPLE.COM
+testuser@EXAMPLE.COM
kadmin:
.fi
.in -2
@@ -1266,8 +1260,6 @@ Quits \fBkadmin\fR. Aliased by \fBexit\fR and \fBq\fR.
.RE
.SS "Time Formats"
-.sp
-.LP
Various commands in \fBkadmin\fR can take a variety of time formats, specifying
time durations or absolute times. The \fBkadmin\fR option variables
\fImaxrenewlife\fR, \fImaxlife\fR, and \fIminlife\fR are time durations,
@@ -1350,7 +1342,7 @@ l l .
.TS
l l
l l .
-\fBVariable Description\fR
+\fBVariable\fR \fBDescription\fR
\fBdd\fR day
\fImm\fR month
\fIyy\fR T{
@@ -1370,29 +1362,29 @@ l l .
\fBTime Units\fR \fBExamples\fR
[+|- \fI#\fR] year "-2 year"
[+|- \fI#\fR] month "2 months"
-[+|- \fI#\fR] fortnight
-[+|- \fI#\fR] week
-[+|- \fI#\fR] day
-[+|- \fI#\fR] hour
-[+|- \fI#\fR] minute
-[+|- \fI#\fR] min
-[+|- \fI#\fR] second
-[+|- \fI#\fR] sec
-tomorrow
-yesterday
-today
-now
+[+|- \fI#\fR] fortnight
+[+|- \fI#\fR] week
+[+|- \fI#\fR] day
+[+|- \fI#\fR] hour
+[+|- \fI#\fR] minute
+[+|- \fI#\fR] min
+[+|- \fI#\fR] second
+[+|- \fI#\fR] sec
+tomorrow
+yesterday
+today
+now
this "this year"
last "last saturday"
next "next month"
-sunday
-monday
-tuesday
-wednesday
-thursday
-friday
-saturday
-never
+sunday
+monday
+tuesday
+wednesday
+thursday
+friday
+saturday
+never
.TE
.sp
@@ -1402,8 +1394,6 @@ You can also use the following time modifiers: \fBfirst\fR, \fBsecond\fR,
\fBeighth\fR, \fBninth\fR, \fBtenth\fR, \fBeleventh\fR, \fBtwelfth\fR, and
\fBago\fR.
.SH ENVIRONMENT VARIABLES
-.sp
-.LP
See \fBenviron\fR(5) for descriptions of the following environment variables
that affect the execution of \fBkadmin\fR:
.sp
@@ -1418,7 +1408,6 @@ specify options. The default is \fBmore\fR(1).
.RE
.SH FILES
-.sp
.ne 2
.na
\fB\fB/var/krb5/principal\fR\fR
@@ -1492,8 +1481,6 @@ Keytab for \fBkadmind\fR principals: \fBkadmin\fR/\fIfqdn\fR,
.RE
.SH ATTRIBUTES
-.sp
-.LP
See \fBattributes\fR(5) for descriptions of the following attributes:
.sp
@@ -1508,20 +1495,14 @@ Interface Stability Committed
.TE
.SH SEE ALSO
-.sp
-.LP
\fBkpasswd\fR(1), \fBmore\fR(1), \fBkadmind\fR(1M),
\fBkdb5_util\fR(1M), \fBkdb5_ldap_util\fR(1M), \fBkproplog\fR(1M),
\fBkadm5.acl\fR(4), \fBkdc.conf\fR(4), \fBkrb5.conf\fR(4), \fBattributes\fR(5),
\fBenviron\fR(5), \fBkerberos\fR(5), \fBkrb5envvar\fR(5)
.SH HISTORY
-.sp
-.LP
The \fBkadmin\fR program was originally written by Tom Yu at MIT, as an
interface to the OpenVision Kerberos administration program.
.SH DIAGNOSTICS
-.sp
-.LP
The \fBkadmin\fR command is currently incompatible with the MIT \fBkadmind\fR
daemon interface, so you cannot use this command to administer an MIT-based
Kerberos database. However, clients running the Solaris implementation of
diff --git a/usr/src/man/man1m/kclient.1m b/usr/src/man/man1m/kclient.1m
index 276c0055cf..caca84423a 100644
--- a/usr/src/man/man1m/kclient.1m
+++ b/usr/src/man/man1m/kclient.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 KCLIENT 1M "May 27, 2009"
+.TH KCLIENT 1M "November 22, 2021"
.SH NAME
kclient \- set up a machine as a Kerberos client
.SH SYNOPSIS
-.LP
.nf
\fB/usr/sbin/kclient\fR [\fB-n\fR] [\fB-R\fR \fIrealm\fR] [\fB-k\fR \fIkdc\fR] [\fB-a\fR \fIadminuser\fR]
[\fB-c\fR \fIfilepath\fR] [\fB-d\fR \fIdnsarg\fR] [\fB-f\fR \fIfqdn_list\fR] [\fB-h\fR \fIlogical_host_name\fR]
@@ -16,8 +15,6 @@ kclient \- set up a machine as a Kerberos client
.fi
.SH DESCRIPTION
-.sp
-.LP
By specifying the various command options, you can use the \fBkclient\fR
utility to:
.RS +4
@@ -137,8 +134,6 @@ the KDC. It is advised that both systems run some form of time synchronization
protocol, such as the Network Time Protocol (NTP). See the \fBntpd\fR man page,
delivered in the \fBSUNWntpu\fR package (not a SunOS man page).
.SH OPTIONS
-.sp
-.LP
The non-interactive mode supports the following options:
.sp
.ne 2
@@ -417,18 +412,17 @@ example of a possible \fIpam_service\fR value is: \fBdtlogin,sshd-kbdint\fR.
.RE
.SH EXAMPLES
-.LP
\fBExample 1 \fRSetting Up a Kerberos Client Using Command-Line Options
.sp
.LP
To setup a Kerberos client using the \fBclntconfig/admin\fR administrative
-principal for realm \fB\&'ABC.COM', kdc `example1.com'\fR and that also does
-kerberized NFS, enter:
+principal for realm \fB\&'EXAMPLE.COM', kdc `example1.example.com'\fR and
+that also does kerberized NFS, enter:
.sp
.in +2
.nf
-# /usr/sbin/kclient -n -R ABC.COM -k example1.com -a clntconfig
+# /usr/sbin/kclient -n -R EXAMPLE.COM -k example1.example.com -a clntconfig
.fi
.in -2
.sp
@@ -436,15 +430,15 @@ kerberized NFS, enter:
.sp
.LP
Alternatively, to set up a Kerberos client using the \fBclntconfig/admin\fR
-administrative principal for the realm \fB`EAST.ABC.COM', kdc
-`example2.east.abc.com'\fR and that also needs service principal(s) created
+administrative principal for the realm \fB`EAST.EXAMPLE.COM', kdc
+`example2.east.example.com'\fR and that also needs service principal(s) created
and/or added to the local \fBkeytab\fR for multiple DNS domains, enter:
.sp
.in +2
.nf
-# /usr/sbin/kclient -n -R EAST.ABC.COM -k example2.east.abc.com \e
--f west.abc.com,central.abc.com -a clntconfig
+# /usr/sbin/kclient -n -R EAST.EXAMPLE.COM -k example2.east.example.com \e
+-f west.example.com,central.example.com -a clntconfig
.fi
.in -2
@@ -458,7 +452,7 @@ privileges (for the principals in the KDC database) in order for the
.sp
.in +2
.nf
-clntconfig/admin@ABC.COM acmi
+clntconfig/admin@EXAMPLE.COM acmi
.fi
.in -2
.sp
@@ -468,13 +462,13 @@ clntconfig/admin@ABC.COM acmi
.sp
.LP
To setup a Kerberos client using the \fBclntconfig/admin\fR administrative
-principal for realm \fB`ABC.COM', kdc `example1.com'\fR and that also copies
-over the master \fBkrb5.conf\fR from a specified location, enter:
+principal for realm \fB`EXAMPLE.COM', kdc `example1.example.com'\fR and that
+also copies over the master \fBkrb5.conf\fR from a specified location, enter:
.sp
.in +2
.nf
-# /usr/sbin/kclient -p /net/example1.com/export/profile.krb5
+# /usr/sbin/kclient -p /net/example1.example.com/export/profile.krb5
.fi
.in -2
.sp
@@ -486,10 +480,10 @@ The contents of \fBprofile.krb5\fR:
.sp
.in +2
.nf
-REALM ABC.COM
-KDC example1
+REALM EXAMPLE.COM
+KDC example1.example.com
ADMIN clntconfig
-FILEPATH /net/example1.com/export/krb5.conf
+FILEPATH /net/example1.example.com/export/krb5.conf
NFS 0
DNSLOOKUP none
.fi
@@ -507,8 +501,8 @@ therefore does not require a \fBkeytab\fR (\fB/etc/krb5/krb5.keytab\fR) file.
.sp
.LP
For this type of client the administrator would issue the following command to
-configure this machine to be a Kerberos client of the \fBABC.COM\fR realm with
-the KDC server \fBkdc1.example.com\fR:
+configure this machine to be a Kerberos client of the \fBEXAMPLE.COM\fR realm
+with the KDC server \fBkdc1.example.com\fR:
.sp
.in +2
@@ -519,7 +513,6 @@ the KDC server \fBkdc1.example.com\fR:
.sp
.SH FILES
-.sp
.ne 2
.na
\fB\fB/etc/krb5/kadm5.acl\fR\fR
@@ -570,8 +563,6 @@ DNS resolver configuration file.
.RE
.SH ATTRIBUTES
-.sp
-.LP
See \fBattributes\fR(5) for descriptions of the following attributes:
.sp
@@ -586,15 +577,11 @@ Interface Stability Committed
.TE
.SH SEE ALSO
-.sp
-.LP
\fBencrypt\fR(1), \fBksh93\fR(1), \fBldapdelete\fR(1), \fBldapmodify\fR(1),
\fBldapsearch\fR(1), \fBdd\fR(1M), \fBsmbadm\fR(1M), \fBkadm5.acl\fR(4),
\fBkrb5.conf\fR(4), \fBnfssec.conf\fR(4), \fBpam.conf\fR(4),
\fBresolv.conf\fR(4), \fBattributes\fR(5), \fBpam_krb5\fR(5)
.SH NOTES
-.sp
-.LP
\fBfqdn\fR stands for the Fully Qualified Domain Name of the local host. The
\fBkclient\fR utility saves copies of both the \fBkrb5.conf\fR(4) and
\fBnfssec.conf\fR(4) files to files with corresponding names and \fB\&.sav\fR
diff --git a/usr/src/man/man1m/kdb5_util.1m b/usr/src/man/man1m/kdb5_util.1m
index 6e7a54ffb5..0ec8d80a48 100644
--- a/usr/src/man/man1m/kdb5_util.1m
+++ b/usr/src/man/man1m/kdb5_util.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 KDB5_UTIL 1M "April 9, 2016"
+.TH KDB5_UTIL 1M "November 22, 2021"
.SH NAME
kdb5_util \- Kerberos Database maintenance utility
.SH SYNOPSIS
-.LP
.nf
\fB/usr/sbin/kdb5_util\fR [\fB-d\fR \fIdbname\fR] [\fB-f\fR \fIstashfile_name\fR]
[\fB-k\fR \fImkeytype\fR] [\fB-m\fR ] [\fB-M\fR \fImkeyname\fR] [\fB-P\fR \fIpassword\fR] [\fB-r\fR \fIrealm\fR]
@@ -15,12 +14,10 @@ kdb5_util \- Kerberos Database maintenance utility
.fi
.SH DESCRIPTION
-.LP
The \fBkdb5_util\fR utility enables you to create, dump, load, and destroy the
Kerberos V5 database. You can also use \fBkdb5_util\fR to create a stash file
containing the Kerberos database master key.
.SH OPTIONS
-.LP
The following options are supported:
.sp
.ne 2
@@ -160,7 +157,6 @@ Directory server connection port.
.RE
.SH OPERANDS
-.LP
The following operands are supported:
.sp
.ne 2
@@ -446,18 +442,17 @@ Optional argument that is derived from \fIdbname\fR if not specified.
.RE
.SH EXAMPLES
-.LP
\fBExample 1 \fRCreating File that Contains Information about Two Principals
.sp
.LP
The following example creates a file named \fBslavedata\fR that contains the
-information about two principals, \fBjdb@ACME.COM\fR and \fBpak@ACME.COM\fR.
+information about two principals, \fBjdb@EXAMPLE.COM\fR and \fBpak@EXAMPLE.COM\fR.
.sp
.in +2
.nf
# /usr/krb5/bin/kdb5_util dump -verbose slavedata
-jdb@ACME.COM pak@ACME.COM
+jdb@EXAMPLE.COM pak@EXAMPLE.COM
.fi
.in -2
.sp
@@ -505,7 +500,6 @@ The update log file for incremental propagation.
.RE
.SH ATTRIBUTES
-.LP
See \fBattributes\fR(5) for descriptions of the following attributes:
.sp
@@ -520,7 +514,6 @@ Interface Stability Evolving
.TE
.SH SEE ALSO
-.LP
\fBkpasswd\fR(1), \fBkadmin\fR(1M), \fBkadmind\fR(1M),
\fBkadmin.local\fR(1M), \fBkdb5_ldap_util\fR(1M), \fBkproplog\fR(1M),
\fBkadm5.acl\fR(4), \fBkdc.conf\fR(4), \fBattributes\fR(5), \fBkerberos\fR(5)
diff --git a/usr/src/man/man1m/ksslcfg.1m b/usr/src/man/man1m/ksslcfg.1m
index d70ff33c94..efe6124d87 100644
--- a/usr/src/man/man1m/ksslcfg.1m
+++ b/usr/src/man/man1m/ksslcfg.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 KSSLCFG 1M "May 27, 2008"
+.TH KSSLCFG 1M "November 22, 2021"
.SH NAME
ksslcfg \- enable and configure SMF instance of Kernel SSL
.SH SYNOPSIS
-.LP
.nf
\fBksslcfg\fR create \fB-f\fR pkcs11 \fB-T\fR \fItoken_label\fR \fB-C\fR \fIcertificate_label\fR
[\fB-d\fR \fIsofttoken_directory\fR]
@@ -49,8 +48,6 @@ ksslcfg \- enable and configure SMF instance of Kernel SSL
.fi
.SH DESCRIPTION
-.sp
-.LP
\fBksslcfg\fR manages \fBsmf\fR(5) instances for the Kernel SSL proxy module.
An SSL-enabled web server can use the services of its Kernel SSL proxy to
improve the performance of the HTTPS packets processing. It does so by creating
@@ -85,8 +82,6 @@ service unique to the combination of host and SSL port. Instance FMRIs for
particular proxy entries can be found with \fBsvcs\fR(1) and used for
dependencies of other services.
.SH OPTIONS
-.sp
-.LP
The following options are supported:
.sp
.ne 2
@@ -281,7 +276,6 @@ Displays the usage of the command.
.RE
.SH OPERANDS
-.sp
.ne 2
.na
\fB\fB[\fIhost\fR] [\fIssl_port\fR]\fR\fR
@@ -295,7 +289,6 @@ is required. Typically, this has a value of 443.
.RE
.SH EXAMPLES
-.LP
\fBExample 1 \fRCreate and Enable a Kernel SSL Instance
.sp
.LP
@@ -307,11 +300,11 @@ certificate and a key in PKCS#11 format.
.nf
# \fBksslcfg create -f pkcs11 -T "Sun Software PKCS#11 softtoken" \e
-C "Server-Cert" -p /some/directory/password -u webservd \e
--x 8080 www.mysite.com 443\fR
+-x 8080 www.example.com 443\fR
% \fBsvcs svc:/network/ssl/proxy\fR
STATE STIME FMRI
-online Sep_27 svc:/network/ssl/proxy:kssl-www-mysite-com-443
+online Sep_27 svc:/network/ssl/proxy:kssl-www-example-com-443
.fi
.in -2
.sp
@@ -321,7 +314,7 @@ online Sep_27 svc:/network/ssl/proxy:kssl-www-mysite-com-443
.sp
.LP
The following command creates and enables a default instance for all addresses
-from a certicate and key in a \fBpkcs#12\fR file.
+from a certificate and key in a \fBpkcs#12\fR file.
.sp
.in +2
@@ -359,13 +352,12 @@ The following command disables and deletes an instance.
.sp
.in +2
.nf
-# \fBksslcfg delete www.mysite.com 443\fR
+# \fBksslcfg delete www.example.com 443\fR
.fi
.in -2
.sp
.SH EXIT STATUS
-.sp
.ne 2
.na
\fB\fB0\fR\fR
@@ -384,8 +376,6 @@ An error occurred.
.RE
.SH ATTRIBUTES
-.sp
-.LP
See \fBattributes\fR(5) for descriptions of the following attributes:
.sp
@@ -405,14 +395,10 @@ Command line options are Evolving; command output is Unstable. The FMRI service
name (\fBsvc://network/ssl/proxy\fR) is Unstable, as is the FMRI instance's
name format. The utility name is Stable.
.SH SEE ALSO
-.sp
-.LP
\fBnca\fR(1), \fBsvcprop\fR(1), \fBsvcs\fR(1), \fBcryptoadm\fR(1M),
\fBsvcadm\fR(1M), \fBsvccfg\fR(1M), \fBuser_attr\fR(4), \fBattributes\fR(5),
\fBpkcs11_softtoken\fR(5), \fBrbac\fR(5), \fBsmf\fR(5)
.SH NOTES
-.sp
-.LP
\fBksslcfg\fR \fBcreate\fR without an host argument creates an \fBINADDR_ANY\fR
\fBsmf\fR instance. \fBksslcfg\fR \fBdelete\fR without an host argument deletes
only the \fBINADDR_ANY\fR instance. \fBksslcfg\fR \fBdelete\fR needs a host
diff --git a/usr/src/man/man1m/ldapclient.1m b/usr/src/man/man1m/ldapclient.1m
index d56e09fed5..bb8162458d 100644
--- a/usr/src/man/man1m/ldapclient.1m
+++ b/usr/src/man/man1m/ldapclient.1m
@@ -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 LDAPCLIENT 1M "Feb 25, 2017"
+.TH LDAPCLIENT 1M "November 22, 2021"
.SH NAME
ldapclient \- initialize LDAP client machine or output an LDAP client profile
in LDIF format
.SH SYNOPSIS
-.LP
.nf
\fB/usr/sbin/ldapclient\fR [\fB-v\fR | \fB-q\fR] init [\fB-a\fR profileName=\fIprofileName\fR]
[\fB-a\fR domainName=\fIdomain\fR] [\fB-a\fR proxyDN=\fIproxyDN\fR]
@@ -49,7 +48,6 @@ in LDIF format
.fi
.SH DESCRIPTION
-.LP
The \fBldapclient\fR utility can be used to:
.RS +4
.TP
@@ -108,7 +106,7 @@ self \fBcredentialLevel\fR is configured, \fBauthenticationMethod\fR must be
\fBsasl/GSSAPI\fR.
.sp
.LP
-Similarily, if a client is to be configured to enable shadow information update
+Similarly, if a client is to be configured to enable shadow information update
and use a proxy credentialLevel, administrator credentials must be provided
using \fB-a\fR \fBadminDN=\fR\fIadminDN\fR and \fB-a\fR
\fBadminPassword=\fR\fIadminPassword\fR. However, the shadow information update
@@ -252,7 +250,6 @@ appropriate certificate databases to use TLS. Note that the \fBtls:none\fR
authentication method requires a \fBcredentialLevel\fR of \fBproxy\fR to
take effect.
.SS "Commands"
-.LP
The following commands are supported:
.sp
.ne 2
@@ -319,7 +316,6 @@ directory for clients to use, with the \fBinit\fR form of this command.
.RE
.SS "Attributes"
-.LP
The following attributes are supported:
.sp
.ne 2
@@ -765,18 +761,17 @@ This is a multivalued attribute. In the example,
.sp
.in +2
.nf
-serviceSearchDescriptor=passwd:ou=people,dc=a1,dc=acme,dc=com?one
+serviceSearchDescriptor=passwd:ou=people,dc=a1,dc=example,dc=com?one
.fi
.in -2
.sp
the LDAP client would do a one level search in
-\fBou=people,dc=a1,dc=acme,dc=com\fR rather than
+\fBou=people,dc=a1,dc=example,dc=com\fR rather than
\fBou=people,\fIdefaultSearchBase\fR\fR for the \fBpasswd\fR service.
.RE
.SH OPTIONS
-.LP
The following options are supported:
.sp
.ne 2
@@ -876,7 +871,6 @@ This option is mutually exclusive of the \fB-a\fR \fIadminPassword\fR option.
.RE
.SH OPERANDS
-.LP
The following operand is supported:
.sp
.ne 2
@@ -892,7 +886,6 @@ Once the profile is loaded, the \fBpreferredServerList\fR and
.RE
.SH EXAMPLES
-.LP
\fBExample 1 \fRSetting Up a Client By Using the Default Profile Stored on a
Specified LDAP Server
.sp
@@ -917,14 +910,14 @@ a Specified LDAP Server
.LP
The following example shows how to set up a client using the \fBsimple\fR
profile stored on the specified LDAP server. The domainname is set to
-\fBxyz.mycompany.com\fR and the proxyPassword is \fBsecret\fR.
+\fBxyz.example.com\fR and the proxyPassword is \fBsecret\fR.
.sp
.in +2
.nf
example# \fBldapclient init -a profileName=simple \e
--a domainName=xyz.mycompany.com \e
--a proxyDN=cn=proxyagent,ou=profile,dc=xyz,dc=mycompany,dc=com \e
+-a domainName=xyz.example.com \e
+-a proxyDN=cn=proxyagent,ou=profile,dc=xyz,dc=example,dc=com \e
-a proxyPassword=secret '['fe80::a00:20ff:fea3:388']':386\fR
.fi
.in -2
@@ -936,13 +929,13 @@ example# \fBldapclient init -a profileName=simple \e
.LP
The following example shows how to set up a client using only one server. The
authentication method is set to \fBnone\fR, and the search base is
-\fBdc=mycompany,dc=com\fR.
+\fBdc=example,dc=com\fR.
.sp
.in +2
.nf
example# \fBldapclient manual -a authenticationMethod=none \e
--a defaultSearchBase=dc=mycompany,dc=com \e
+-a defaultSearchBase=dc=example,dc=com \e
-a defaultServerList=172.16.100.1\fR
.fi
.in -2
@@ -956,7 +949,7 @@ Referrals
The following example shows how to set up a client using only one server. The
credential level is set to \fBproxy\fR. The authentication method of is
\fBsasl/CRAM-MD5\fR, with the option not to follow referrals. The domain name
-is \fBxyz.mycompany.com\fR, and the LDAP server is running on port number 386
+is \fBxyz.example.com\fR, and the LDAP server is running on port number 386
at IP address \fB172.16.100.1\fR.
.sp
@@ -966,9 +959,9 @@ example# \fBldapclient manual \e
-a credentialLevel=proxy \e
-a authenticationMethod=sasl/CRAM-MD5 \e
-a proxyPassword=secret \e
--a proxyDN=cn=proxyagent,ou=profile,dc=xyz,dc=mycompany,dc=com \e
--a defaultSearchBase=dc=xyz,dc=mycompany,dc=com \e
--a domainName=xyz.mycompany.com \e
+-a proxyDN=cn=proxyagent,ou=profile,dc=xyz,dc=example,dc=com \e
+-a defaultSearchBase=dc=xyz,dc=example,dc=com \e
+-a domainName=xyz.example.com \e
-a followReferrals=false \e
-a defaultServerList=172.16.100.1:386\fR
.fi
@@ -1006,8 +999,8 @@ The following example creates a profile on IPv6 servers
example# \fBldapclient genprofile -a profileName=eng \e
-a credentialLevel=proxy \e
-a authenticationMethod=sasl/DIGEST-MD5 \e
--a defaultSearchBase=dc=eng,dc=acme,dc=com \e
--a "serviceSearchDescriptor=passwd:ou=people,dc=a1,dc=acme,dc=com?one"\e
+-a defaultSearchBase=dc=eng,dc=example,dc=com \e
+-a "serviceSearchDescriptor=passwd:ou=people,dc=a1,dc=example,dc=com?one"\e
-a preferredServerList= '['fe80::a00:20ff:fea3:388']' \e
-a "defaultServerList='['fec0::111:a00:20ff:fea3:edcf']' \e
'['fec0::111:a00:20ff:feb5:e41']'" > eng.ldif\fR
@@ -1027,8 +1020,8 @@ The following example shows a profile that overrides every default value.
example# \fBldapclient genprofile -a profileName=eng \e
-a credentialLevel=proxy -a authenticationMethod=sasl/DIGEST-MD5 \e
-a bindTimeLimit=20 \e
--a defaultSearchBase=dc=eng,dc=acme,dc=com \e
--a "serviceSearchDescriptor=passwd:ou=people,dc=a1,dc=acme,dc=com?one"\e
+-a defaultSearchBase=dc=eng,dc=example,dc=com \e
+-a "serviceSearchDescriptor=passwd:ou=people,dc=a1,dc=example,dc=com?one"\e
-a serviceAuthenticationMethod=pam_ldap:tls:simple \e
-a defaultSearchScope=sub \e
-a attributeMap=passwd:uid=employeeNumber \e
@@ -1041,7 +1034,6 @@ example# \fBldapclient genprofile -a profileName=eng \e
.sp
.SH EXIT STATUS
-.LP
The following exit values are returned:
.sp
.ne 2
@@ -1120,7 +1112,6 @@ files.
.RE
.SH ATTRIBUTES
-.LP
See \fBattributes\fR(5) for descriptions of the following attributes:
.sp
@@ -1135,14 +1126,12 @@ Interface Stability Evolving
.TE
.SH SEE ALSO
-.LP
\fBchkey\fR(1), \fBldap\fR(1), \fBldapadd\fR(1), \fBldapdelete\fR(1),
\fBldaplist\fR(1), \fBldapmodify\fR(1), \fBldapmodrdn\fR(1),
\fBldapsearch\fR(1), \fBidsconfig\fR(1M), \fBldapaddent\fR(1M),
\fBldap_cachemgr\fR(1M), \fBdefaultdomain\fR(4),
\fBnsswitch.conf\fR(4), \fBresolv.conf\fR(4), \fBattributes\fR(5)
.SH CAUTION
-.LP
Currently \fBStartTLS\fR is not supported by \fBlibldap.so.5\fR, therefore the
port number provided refers to the port used during a TLS open, rather than the
port used as part of a \fBStartTLS\fR sequence. To avoid timeout delays, mixed
diff --git a/usr/src/man/man1m/lpset.1m b/usr/src/man/man1m/lpset.1m
index 4556d8d27b..a25eed3fc5 100644
--- a/usr/src/man/man1m/lpset.1m
+++ b/usr/src/man/man1m/lpset.1m
@@ -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 LPSET 1M "Feb 25, 2017"
+.TH LPSET 1M "November 22, 2021"
.SH NAME
lpset \- set printing configuration in /etc/printers.conf or other supported
databases
.SH SYNOPSIS
-.LP
.nf
\fBlpset\fR [\fB-n\fR system | fnsldap] [\fB-x\fR]
[ [\fB-D\fR binddn] [\fB-w\fR passwd] [\fB-h\fR ldaphost]]
@@ -16,7 +15,6 @@ databases
.fi
.SH DESCRIPTION
-.LP
The \fBlpset\fR utility sets printing configuration information in the system
configuration databases. Use \fBlpset\fR to create and update printing
configuration in \fB/etc/printers.conf\fR.
@@ -25,7 +23,6 @@ See \fBnsswitch.conf\fR(4) and \fBprinters.conf\fR(4).
.LP
Only a superuser or a member of Group 14 may execute \fBlpset\fR.
.SH OPTIONS
-.LP
The following options are supported:
.sp
.ne 2
@@ -105,7 +102,6 @@ not specified, the default is the current host system.
.RE
.SH OPERANDS
-.LP
The following operand is supported:
.sp
.ne 2
@@ -123,7 +119,6 @@ atomic names and \fBstandards\fR(5) for information regarding POSIX.
.RE
.SH EXAMPLES
-.LP
\fBExample 1 \fRRemoving All Existing Printing Configuration Information
.sp
.LP
@@ -143,14 +138,13 @@ example% \fBlpset -x dogs\fR
.sp
.in +2
.nf
-example% \fBlpset -n ldap -h ldapl.xyz.com -D "cn=Directory Manager" \e
+example% \fBlpset -n ldap -h ldapl.example.com -D "cn=Directory Manager" \e
-w passwd -a key1=value1 printer1\fR
.fi
.in -2
.sp
.SH EXIT STATUS
-.LP
The following exit values are returned:
.sp
.ne 2
@@ -180,7 +174,6 @@ System configuration database.
.RE
.SH ATTRIBUTES
-.LP
See \fBattributes\fR(5) for descriptions of the following attributes:
.sp
@@ -195,7 +188,6 @@ Stability Level Stable
.TE
.SH SEE ALSO
-.LP
\fBldap\fR(1), \fBlp\fR(1), \fBlpc\fR(1B), \fBlpq\fR(1B), \fBlpr\fR(1B),
\fBlpstat\fR(1), \fBldapclient\fR(1M), \fBlpadmin\fR(1M), \fBlpget\fR(1M),
\fBnsswitch.conf\fR(4), \fBprinters\fR(4), \fBprinters.conf\fR(4),
@@ -204,7 +196,6 @@ Stability Level Stable
.LP
\fI\fR
.SH NOTES
-.LP
If the \fBldap\fR database is used, the printer administrator should be mindful
of the following when updating printer information.
.RS +4
@@ -219,7 +210,7 @@ host the same domain that is used by the current \fBldapclient\fR(1M) server.
2.
If the LDAP server being updated is a replica LDAP server, the updates will
be referred to the master LDAP server and completed there. The updates might be
-out of sync and not appear immediatedly, as the replica server may not have
+out of sync and not appear immediately, as the replica server may not have
been updated by the master server. For example, a printer that you deleted by
using \fBlpset\fR may still appear in the printer list you display with
\fBlpget\fR until the replica is updated from the master. Replica servers vary
diff --git a/usr/src/man/man1m/mount_smbfs.1m b/usr/src/man/man1m/mount_smbfs.1m
index f47587ba67..74d38ba013 100644
--- a/usr/src/man/man1m/mount_smbfs.1m
+++ b/usr/src/man/man1m/mount_smbfs.1m
@@ -7,12 +7,11 @@
.\" SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
.\" OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\" Copyright 2012 Nexenta Systems, Inc. All rights reserved.
-.TH MOUNT_SMBFS 1M "Jan 2, 2012"
+.TH MOUNT_SMBFS 1M "November 22, 2021"
.SH NAME
mount_smbfs, umount_smbfs \- mount and unmount a shared resource from a CIFS
file server
.SH SYNOPSIS
-.LP
.nf
\fB/sbin/mount\fR [\fB-F smbfs\fR] [\fIgeneric-options\fR] [\fB-o\fR \fIname\fR\fB=\fR\fIvalue\fR] [\fB-O\fR] \fIresource\fR
.fi
@@ -34,8 +33,6 @@ file server
.fi
.SH DESCRIPTION
-.sp
-.LP
The \fBmount\fR utility attaches a named resource, \fIresource\fR, to the file
system hierarchy at the path name location, \fImount-point\fR, which must
already exist.
@@ -78,8 +75,6 @@ To enable the service, enter the following \fBsvcadm\fR(1M) command:
.sp
.SS "Operands"
-.sp
-.LP
The \fBmount\fR command supports the following operands:
.sp
.ne 2
@@ -148,8 +143,6 @@ The \fBmount\fR command maintains a table of mounted file systems in the
.RE
.SH OPTIONS
-.sp
-.LP
See the \fBmount\fR(1M) man page for the list of supported
\fIgeneric-options\fR.
.sp
@@ -323,7 +316,6 @@ producing the error "device busy."
.RE
.SH EXAMPLES
-.LP
\fBExample 1 \fRMounting an SMBFS Share
.sp
.LP
@@ -335,7 +327,7 @@ perform the mount operation.
.sp
.in +2
.nf
-# \fBmount -F smbfs "//SALES;root@nano.sfbay/tmp" /mnt\fR
+# \fBmount -F smbfs "//SALES;root@nano.example.org/tmp" /mnt\fR
Password:
.fi
.in -2
@@ -352,7 +344,7 @@ password for the \fBroot\fR user to successfully perform the mount operation.
.sp
.in +2
.nf
-# \fBmount -F smbfs //root@nano.sfbay/tmp /mnt\fR
+# \fBmount -F smbfs //root@nano.example.org/tmp /mnt\fR
Password:
.fi
.in -2
@@ -370,7 +362,7 @@ View the file system entry in the \fB/etc/mnttab\fR file.
.in +2
.nf
# \fBgrep root /etc/mnttab\fR
-//root@nano.sfbay/tmp /mnt smbfs dev=4900000 1177097833
+//root@nano.example.org/tmp /mnt smbfs dev=4900000 1177097833
.fi
.in -2
.sp
@@ -385,7 +377,7 @@ View the output of the \fBmount\fR command.
.in +2
.nf
# \fBmount | grep root\fR
-/mnt on //root@nano.sfbay/tmp read/write/setuid/devices/dev=4900000 on
+/mnt on //root@nano.example.org/tmp read/write/setuid/devices/dev=4900000 on
Fri Apr 20 13:37:13 2007
.fi
.in -2
@@ -401,7 +393,7 @@ View the output of the \fBdf /mnt\fR command.
.in +2
.nf
# \fBdf /mnt\fR
-/mnt (//root@nano.sfbay/tmp): 3635872 blocks -1 files
+/mnt (//root@nano.example.org/tmp): 3635872 blocks -1 files
.fi
.in -2
.sp
@@ -417,7 +409,7 @@ Obtain information about the mounted share by viewing the output of the \fBdf
.nf
# \fBdf -k /mnt\fR
Filesystem kbytes used avail capacity Mounted on
-//root@nano.sfbay/tmp
+//root@nano.example.org/tmp
1882384 64448 1817936 4% /mnt
.fi
.in -2
@@ -439,7 +431,6 @@ point. The following command line unmounts the share from the mount point.
.sp
.SH FILES
-.sp
.ne 2
.na
\fB\fB/etc/mnttab\fR\fR
@@ -481,8 +472,6 @@ connection.
.RE
.SH ATTRIBUTES
-.sp
-.LP
See the \fBattributes\fR(5) man page for descriptions of the following
attributes:
.sp
@@ -498,21 +487,15 @@ Interface Stability Committed
.TE
.SH SEE ALSO
-.sp
-.LP
\fBldap\fR(1), \fBsmbutil\fR(1),
\fBmount\fR(1M), \fBmountall\fR(1M), \fBsvcadm\fR(1M),
\fBacl\fR(2), \fBfcntl\fR(2), \fBlink\fR(2), \fBmknod\fR(2), \fBmount\fR(2),
\fBsymlink\fR(2), \fBumount\fR(2), \fBmnttab\fR(4), \fBnsmbrc\fR(4),
\fBvfstab\fR(4), \fBattributes\fR(5), \fBpcfs\fR(7FS), \fBsmbfs\fR(7FS)
.SH AUTHORS
-.sp
-.LP
This manual page contains material originally authored by Boris Popov,
\fBbpATbutya.kz\fR, \fBbpATFreeBSD.org\fR.
.SH NOTES
-.sp
-.LP
The Solaris CIFS client always attempts to use \fBgethostbyname()\fR to resolve
host names. If the host name cannot be resolved, the CIFS client uses NetBIOS
name resolution (NBNS). By default, the Solaris CIFS client permits the use of
diff --git a/usr/src/man/man1m/pppd.1m b/usr/src/man/man1m/pppd.1m
index 712976375a..8862ee9b94 100644
--- a/usr/src/man/man1m/pppd.1m
+++ b/usr/src/man/man1m/pppd.1m
@@ -3,18 +3,15 @@
.\" Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by Carnegie Mellon University. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
.\" WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
.\" Portions Copyright (c) 2008, Sun Microsystems, Inc. All Right Reserved.
-.TH PPPD 1M "Nov 21, 2001"
+.TH PPPD 1M "November 22, 2021"
.SH NAME
pppd \- point to point protocol daemon
.SH SYNOPSIS
-.LP
.nf
\fBpppd\fR [\fItty_name\fR] [\fIspeed\fR] [\fIoptions\fR]
.fi
.SH DESCRIPTION
-.sp
-.LP
The point-to-point protocol (PPP) provides a method for transmitting datagrams
over serial point-to-point links. PPP is composed of three components: a
facility for encapsulating datagrams over serial links, an extensible link
@@ -27,12 +24,8 @@ provides the basic LCP authentication support and several NCPs for establishing
and configuring the Internet Protocol (referred to as the IP Control Protocol
or "IPCP") and IPv6 (IPV6CP).
.SH OPTIONS
-.sp
-.LP
The following sections discuss the \fBpppd\fR options:
.SS "Options Files"
-.sp
-.LP
Options are taken from files and the command line. \fBpppd\fR reads options
from the files \fB/etc/ppp/options\fR, \fB$HOME/.ppprc\fR and
\fB/etc/ppp/options.\fR\fIttyname\fR (in that order) before processing the
@@ -51,7 +44,6 @@ starts a comment, which continues until the end of the line. There is no
restriction on using the \fBfile\fR or \fBcall\fR options within an options
file.
.SS "Frequently Used Options"
-.sp
.ne 2
.na
\fB\fB<tty_name>\fR \fR
@@ -269,7 +261,6 @@ this option.
.RE
.SS "Options"
-.sp
.ne 2
.na
\fB\fB<local_IP_address>:<remote_IP_address>\fR \fR
@@ -507,9 +498,9 @@ in conjunction with the \fBdemand\fR option.
.RS 4n
Append the domain name \fId\fR to the local host name for authentication
purposes. For example, if \fBgethostname()\fR returns the name \fBporsche\fR,
-but the fully qualified domain name is \fBporsche.Quotron.COM\fR, you could
-specify \fBdomain Quotron.COM\fR. With this configuration, \fBpppd\fR uses the
-name \fBporsche.Quotron.COM\fR for accessing secrets in the secrets file and as
+but the fully qualified domain name is \fBporsche.Example.COM\fR, you could
+specify \fBdomain Example.COM\fR. With this configuration, \fBpppd\fR uses the
+name \fBporsche.Example.COM\fR for accessing secrets in the secrets file and as
the default name when authenticating to the peer. This option is privileged.
.RE
@@ -1813,8 +1804,6 @@ the serial port.
.RE
.SS "Obsolete Options"
-.sp
-.LP
The following options are obsolete:
.sp
.ne 2
@@ -1855,12 +1844,8 @@ Show brief help message and exit.
.RE
.SH EXTENDED DESCRIPTION
-.sp
-.LP
The following sections discuss miscellaneous features of \fBpppd\fR:
.SS "Security"
-.sp
-.LP
\fBpppd\fR allows system administrators to provide legitimate users with PPP
access to a server machine without fear of compromising the security of the
server or the network it runs on. Access control is provided by restricting IP
@@ -1902,8 +1887,6 @@ administrator can allow users to establish a PPP connection via a device that
they would not normally have access to. Otherwise \fBpppd\fR uses the invoking
user's real UID when opening the device.
.SS "Authentication"
-.sp
-.LP
During the authentication process, one peer convinces the other of its identity
by sending its name and some secret information to the other. During
authentication, the first peer becomes the "client" and the second becomes the
@@ -2027,8 +2010,6 @@ peername servername secret ip-address -- novj
.in -2
.SS "Routing"
-.sp
-.LP
When IPCP negotiation is complete, \fBpppd\fR informs the kernel of the local
and remote IP addresses for the PPP interface and creates a host route to the
remote end of the link that enables peers to exchange IP packets. Communication
@@ -2060,8 +2041,6 @@ addresses to the negotiated addresses. This may disrupt existing connections.
Using demand dialing with peers that perform dynamic IP address assignment is
not recommended.
.SS "Scripts"
-.sp
-.LP
\fBpppd\fR invokes scripts at various stages during processing that are used to
perform site-specific ancillary processing. These scripts may be shell scripts
or executable programs. \fBpppd\fR does not wait for the scripts to finish. The
@@ -2262,7 +2241,6 @@ script.
.RE
.SH EXAMPLES
-.LP
\fBExample 1 \fRUsing the \fBauth\fR Option
.sp
.LP
@@ -2336,13 +2314,13 @@ To provide a user with access to the PPP facilities, allocate an IP address for
the user's machine, create an entry in \fB/etc/ppp/pap-secrets\fR or
\fB/etc/ppp/chap-secrets\fR. This enables the user's machine to authenticate
itself. For example, to enable user "Joe" using machine "joespc" to dial in to
-machine "server" and use the IP address "joespc.my.net," add the following
+machine "server" and use the IP address "joespc.example.net," add the following
entry to the \fB/etc/ppp/pap-secrets\fR or \fB/etc/ppp/chap-secrets\fR files:
.sp
.in +2
.nf
-\fBjoespc server "joe's secret" joespc.my.net\fR
+\fBjoespc server "joe's secret" joespc.example.net\fR
.fi
.in -2
.sp
@@ -2363,8 +2341,6 @@ includes a telnet, escape ^] (\fBasyncmap 200a0000\fR). If the path includes a
followed by any 8 bytes] from the stream.
.SH EXIT STATUS
-.sp
-.LP
The \fBpppd\fR exit status indicates errors or specifies why a link was
terminated. Exit status values are:
.sp
@@ -2554,7 +2530,6 @@ Authentication to the peer failed.
.RE
.SH FILES
-.sp
.ne 2
.na
\fB\fB/var/run/sppp\fIn\fR\fR\fB\&.pid\fR \fR
@@ -2641,8 +2616,6 @@ but only to certain trusted peers.
.RE
.SH ATTRIBUTES
-.sp
-.LP
See \fBattributes\fR(5) for descriptions of the following attributes:
.sp
@@ -2657,8 +2630,6 @@ Interface Stability Evolving
.TE
.SH SEE ALSO
-.sp
-.LP
\fBchat\fR(1M), \fBifconfig\fR(1M), \fBcrypt\fR(3C), \fBpam\fR(3PAM),
\fBattributes\fR(5)
.sp
@@ -2690,8 +2661,6 @@ Group. July 1994.
Simpson, W. \fIRFC 1662, HDLC-like Framing \fR. Network Working Group. July
1994.
.SH NOTES
-.sp
-.LP
These signals affect \fBpppd\fR behavior:
.sp
.ne 2
@@ -2738,8 +2707,6 @@ implementation.)
.RE
.SH DIAGNOSTICS
-.sp
-.LP
Messages are sent to the syslog daemon using facility \fBLOG_DAEMON\fR. To see
error and debug messages, edit the \fB/etc/syslog.conf\fR file to direct the
messages to the desired output device or file, or use the \fBupdetach\fR or
diff --git a/usr/src/man/man1m/share_nfs.1m b/usr/src/man/man1m/share_nfs.1m
index 8904de8ba1..ff360207e1 100644
--- a/usr/src/man/man1m/share_nfs.1m
+++ b/usr/src/man/man1m/share_nfs.1m
@@ -23,7 +23,7 @@
.\" Copyright 2014 Nexenta Systems, Inc. All rights reserved.
.\" Copyright 2016 Jason King.
.\"
-.Dd March 23, 2017
+.Dd November 22, 2021
.Dt SHARE_NFS 1M
.Os
.Sh NAME
@@ -440,14 +440,14 @@ NIS 172.16.45.9 --> "myhost"
.Pp
and
.Bd -literal -offset indent
-DNS or LDAP 172.16.45.9 --> "myhost.mydomain.mycompany.com"
+DNS or LDAP 172.16.45.9 --> "myhost.mydomain.example.com"
.Ed
.Pp
The domain name suffix is distinguished from hostnames and netgroups by a
prefixed dot.
For example,
.Bd -literal -offset indent
-rw=.mydomain.mycompany.com
+rw=.mydomain.example.com
.Ed
.Pp
A single dot can be used to match a hostname with no suffix.
@@ -459,7 +459,7 @@ rw=.
matches
.Qq mydomain
but not
-.Qq mydomain.mycompany.com .
+.Qq mydomain.example.com .
This feature can be used to match hosts resolved through NIS rather
than DNS and LDAP.
.It Sy network
diff --git a/usr/src/man/man1m/sharectl.1m b/usr/src/man/man1m/sharectl.1m
index 74d260d4e7..bd27bb4911 100644
--- a/usr/src/man/man1m/sharectl.1m
+++ b/usr/src/man/man1m/sharectl.1m
@@ -18,7 +18,7 @@
.\" Copyright (c) 2007, Sun Microsystems, Inc. All Rights Reserved
.\" Copyright 2016 Nexenta Systems, Inc.
.\"
-.Dd December 16, 2016
+.Dd November 22, 2021
.Dt SHARECTL 1M
.Os
.Sh NAME
@@ -148,7 +148,7 @@ lockd_listen_backlog=32
lockd_servers=256
lockd_retransmit_timeout=5
grace_period=90
-nfsmapid_domain=sun.com
+nfsmapid_domain=example.com
servers=1024
server_versmin=2
server_versmax=4
@@ -172,24 +172,24 @@ nfs enabled
The following command shows how an authorized user can use
.Nm
commands to configure global settings for the
-.Pa ex.com
+.Pa example.com
environment in the service management facility
.Pq SMF .
See
.Xr nsmbrc 4
for a description of the example environment,
-.Pa ex.com .
+.Pa example.com .
See
.Xr smf 5
for a description of the SMF.
.Bd -literal
# sharectl set -p section=default -p workgroup=SALES \e
-p timeout=5 smbfs
-# sharectl set -p section=FSERVER -p addr=fserv.ex.com smbfs
+# sharectl set -p section=FSERVER -p addr=fserv.example.com smbfs
# sharectl set -p section=RSERVER -p workgroup=REMGROUP \e
- -p addr=rserv.ex.com smbfs
+ -p addr=rserv.example.com smbfs
# sharectl set -p section=RSERVER:george -p timeout=30 smbfs
-# sharectl set -p section="SSERV:*:POKY" -p addr=sserv.ex.com \e
+# sharectl set -p section="SSERV:*:POKY" -p addr=sserv.example.com \e
-p timeout=25 smbfs
.Ed
.It Sy Example 5 No Displaying Current Settings
@@ -205,14 +205,14 @@ The values shown are those set by the previous example.
workgroup=SALES
timeout=5
[FSERVER]
-addr=fserv.ex.com
+addr=fserv.example.com
[RSERVER]
workgroup=REMGROUP
-addr=rserv.ex.com
+addr=rserv.example.com
[RSERVER:george]
timeout=30
[SSERV:*:POKY]
-addr=sserv.ex.com
+addr=sserv.example.com
timeout=25
.Ed
.El
diff --git a/usr/src/man/man1m/sharemgr.1m b/usr/src/man/man1m/sharemgr.1m
index e7e86f4961..6bf52efd94 100644
--- a/usr/src/man/man1m/sharemgr.1m
+++ b/usr/src/man/man1m/sharemgr.1m
@@ -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 SHAREMGR 1M "Feb 25, 2017"
+.TH SHAREMGR 1M "November 22, 2021"
.SH NAME
sharemgr \- configure and manage file sharing
.SH SYNOPSIS
-.LP
.nf
\fBsharemgr\fR \fIsubcommand\fR [\fIoptions\fR]
.fi
@@ -89,7 +88,6 @@ sharemgr \- configure and manage file sharing
.fi
.SH DESCRIPTION
-.LP
The \fBsharemgr\fR command configures share groups and the shares contained
within them.
.sp
@@ -123,7 +121,6 @@ The options shown in the SYNOPSIS section are described in the context of each
subcommand. All subcommands except \fBlist\fR and \fBshow\fR require root
privileges or that you assume the Primary Administrator role.
.SS "Subcommands"
-.LP
With no subcommand entered, a \fBsharemgr\fR command with the \fB-h\fR option
displays a usage message for all subcommands.
.sp
@@ -629,7 +626,6 @@ across reboots.
.RE
.SS "Supported Properties"
-.LP
Properties are protocol-specific. Currently, only the NFS and SMB protocols are
supported. Properties have the following characteristics:
.RS +4
@@ -1130,7 +1126,6 @@ is when the access list is an asterisk (\fB*\fR), in which case \fBro\fR or
.RE
.SS "Access List Argument"
-.LP
The \fIaccess-list\fR argument is either the string \fB"*"\fR to represent all
hosts or a colon-separated list whose components can be any number of the
following:
@@ -1191,7 +1186,7 @@ Returns: \fBmyhost\fR
.ad
.sp .6
.RS 4n
-Returns: \fBmyhost.mydomain.mycompany.com\fR
+Returns: \fBmyhost.mydomain.example.com\fR
.RE
The domain name suffix is distinguished from hostnames and netgroups by a
@@ -1199,7 +1194,7 @@ prefixed dot. For example:
.sp
.in +2
.nf
-rw=.mydomain.mycompany.com
+rw=.mydomain.example.com
.fi
.in -2
@@ -1212,7 +1207,7 @@ rw=.
.fi
.in -2
-\&...matches \fBmydomain\fR but not \fBmydomain.mycompany.com\fR. This feature
+\&...matches \fBmydomain\fR but not \fBmydomain.example.com\fR. This feature
can be used to match hosts resolved through NIS rather than DNS and
LDAP.
.RE
@@ -1321,7 +1316,6 @@ Error codes used for exit status.
.RE
.SH ATTRIBUTES
-.LP
See \fBattributes\fR(5) for descriptions of the following attributes:
.sp
@@ -1336,6 +1330,5 @@ Interface Stability Committed
.TE
.SH SEE ALSO
-.LP
\fBidmap\fR(1M), \fBsharectl\fR(1M), \fBzfs\fR(1M), \fBattributes\fR(5),
\fBnfssec\fR(5), \fBsmf\fR(5), \fBstandards\fR(5)
generated by cgit v1.2.3 (git 2.46.0) at 2025-12-06 20:19:26 +0000