Spelling corrections.
PR: 6868 Submitted by: Josh Gilliam <josh@quick.net>
This commit is contained in:
jkoshy
parent
b3603fedd6
commit
93bb25d88b
@ -79,7 +79,7 @@ This storage is owned by the caller.
|
||||
.AP int objc in
|
||||
Count of additional object arguments to pass to the alias object command.
|
||||
.AP Tcl_Object **objv in
|
||||
Vector of Tcl_Obj structures, the additional object argumenst to pass to
|
||||
Vector of Tcl_Obj structures, the additional object arguments to pass to
|
||||
the alias object command.
|
||||
This storage is owned by the caller.
|
||||
.AP Tcl_Interp **targetInterpPtr in
|
||||
|
||||
@ -55,7 +55,7 @@ The argument \fItypePtr\fR points to a Tcl_ObjType structure that
|
||||
describes the new type by giving its name
|
||||
and by supplying pointers to four procedures
|
||||
that implement the type.
|
||||
If the type table already containes a type
|
||||
If the type table already contains a type
|
||||
with the same name as in \fItypePtr\fR,
|
||||
it is replaced with the new type.
|
||||
The Tcl_ObjType structure is described
|
||||
|
||||
@ -64,7 +64,7 @@ subcommand we would like to use the full subcommand name rather than
|
||||
the abbreviation. If the \fBTcl_WrongNumArgs\fR command finds any
|
||||
\fIindexObjects\fR in the \fIobjv\fR array it will use the full subcommand
|
||||
name in the error message instead of the abbreviated name that was
|
||||
origionally passed in. Using the above example, lets assume that
|
||||
originally passed in. Using the above example, let us assume that
|
||||
\fIbar\fR is actually an abbreviation for \fIbarfly\fR and the object
|
||||
is now an indexObject becasue it was passed to
|
||||
\fBTcl_GetIndexFromObj\fR. In this case the error message would be:
|
||||
|
||||
@ -11,7 +11,7 @@
|
||||
.\" nor does the author assume any responsibility for damages incurred with
|
||||
.\" its use.
|
||||
.\"
|
||||
.\" $Id: dialog.3,v 1.5 1997/02/22 15:42:35 peter Exp $
|
||||
.\" $Id: dialog.3,v 1.6 1997/04/13 12:36:42 bde Exp $
|
||||
.\"
|
||||
.Dd December 18, 1995
|
||||
.Dt dialog 3
|
||||
@ -148,7 +148,7 @@ Returns the width of string in \fBp\fR, counting newlines.
|
||||
.Ft "void"
|
||||
.Fn dialog_create_rc "unsigned char *filename"
|
||||
|
||||
Dump dialog library settings into \fBfilename\fR for later retreival
|
||||
Dump dialog library settings into \fBfilename\fR for later retrieval
|
||||
as defaults. Returns 0 on success, -1 on failure.
|
||||
|
||||
.Ft "int"
|
||||
|
||||
@ -76,7 +76,7 @@ different groups of private addresses
|
||||
can be linked to different public addresses,
|
||||
comprising several distinct many-to-one
|
||||
mappings. Also, a given public address
|
||||
and port can be staticly redirected to
|
||||
and port can be statically redirected to
|
||||
a private address/port.
|
||||
|
||||
The packet aliasing engine was designed
|
||||
@ -212,7 +212,7 @@ unknown host address or unknown port number
|
||||
(e.g. an FTP data connection), this mode bit
|
||||
specifies that a socket be allocated as a place
|
||||
holder to prevent port conflicts. Once a
|
||||
connection is extablished, usually within a
|
||||
connection is established, usually within a
|
||||
minute or so, the socket is closed.
|
||||
.It PKT_ALIAS_UNREGISTERED_ONLY.
|
||||
If this mode bit is set, traffic on the
|
||||
@ -299,7 +299,7 @@ Return codes:
|
||||
.Bl -hang -offset left
|
||||
.It PKT_ALIAS_ERROR.
|
||||
An internal error within the packet aliasing
|
||||
engine occured.
|
||||
engine occurred.
|
||||
.It PKT_ALIAS_OK.
|
||||
The packet aliasing process was successful.
|
||||
.It PKT_ALIAS_IGNORED.
|
||||
@ -333,9 +333,9 @@ The IP packet is pointed to by
|
||||
.Em buffer r,
|
||||
and
|
||||
.Em maxpacketsize
|
||||
indicates the maximum packet size permissable
|
||||
indicates the maximum packet size permissible
|
||||
should the packet length be changed. IP encoding
|
||||
protocols place addresss and port information in
|
||||
protocols place address and port information in
|
||||
the encapsulated data stream which have to be
|
||||
modified and can account for changes in packet
|
||||
length. Well known examples of such protocols
|
||||
@ -345,7 +345,7 @@ Return codes:
|
||||
.Bl -hang -offset left
|
||||
.It PKT_ALIAS_ERROR.
|
||||
An internal error within the packet aliasing
|
||||
engine occured.
|
||||
engine occurred.
|
||||
.It PKT_ALIAS_OK.
|
||||
The packet aliasing process was successful.
|
||||
.It PKT_ALIAS_IGNORED.
|
||||
@ -376,7 +376,7 @@ address translations can be designated.
|
||||
This function specifies that traffic from a
|
||||
given remote address/port to an alias address/port
|
||||
be redirected to a specified local address/port.
|
||||
The paramater
|
||||
The parameter
|
||||
.Em proto
|
||||
can be either IPPROTO_TCP or IPPROTO_UDP, as
|
||||
defined in <netinet/in.h>.
|
||||
@ -682,7 +682,7 @@ number for identifying how individual packets
|
||||
should be handled.)
|
||||
|
||||
Each aliasing link must have a unique
|
||||
combination of the following five quanties:
|
||||
combination of the following five quantities:
|
||||
alias address/port, remote address/port
|
||||
and protocol. This ensures that several
|
||||
machines on a local network can share the
|
||||
@ -699,7 +699,7 @@ sequence. For the case of TCP, the connection
|
||||
can be monitored to see when the associated
|
||||
aliasing link should be deleted. Aliasing links
|
||||
for UDP transactions (and ICMP echo and timestamp
|
||||
equests) work on a simple timeout rule. When
|
||||
requests) work on a simple timeout rule. When
|
||||
no activity is observed on a dynamic link for
|
||||
a certain amount of time it is automatically
|
||||
deleted. Timeout rules also apply to TCP
|
||||
@ -708,7 +708,7 @@ properly.
|
||||
.Ss A.3 Partially Specified Aliasing Links
|
||||
Aliasing links can be partially specified,
|
||||
meaning that the remote address and/or remote
|
||||
ports are unkown. In this case, when a packet
|
||||
ports are unknown. In this case, when a packet
|
||||
matching the incomplete specification is found,
|
||||
a fully specified dynamic link is created. If
|
||||
the original partially specified link is dynamic,
|
||||
@ -750,7 +750,7 @@ the alias address to be used. If no mapping
|
||||
exists, then a default address, usually the
|
||||
address of the packet aliasing host, is used.
|
||||
If necessary, this default address can be
|
||||
changed as often as each indvidual packet
|
||||
changed as often as each individual packet
|
||||
arrives.
|
||||
|
||||
The aliasing port number is determined
|
||||
|
||||
@ -186,7 +186,7 @@ was improperly formatted for address family
|
||||
.Xr inet 4
|
||||
.Sh HISTORY
|
||||
An interface close to this one was originally suggested by Craig
|
||||
Partridge. This particular interface originally apppeared in the
|
||||
Partridge. This particular interface originally appeared in the
|
||||
.Tn INRIA
|
||||
.Tn IPv6
|
||||
implementation.
|
||||
|
||||
@ -30,7 +30,7 @@
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" From: @(#)gethostbyname.3 8.4 (Berkeley) 5/25/95
|
||||
.\" $Id: gethostbyname.3,v 1.8 1997/06/18 06:26:13 charnier Exp $
|
||||
.\" $Id: gethostbyname.3,v 1.9 1998/03/23 13:05:07 bde Exp $
|
||||
.\"
|
||||
.Dd May 25, 1995
|
||||
.Dt GETHOSTBYNAME 3
|
||||
@ -137,7 +137,7 @@ Currently the
|
||||
.Fa af
|
||||
argument must be specified as
|
||||
.Dv AF_INET
|
||||
else the fuction will return
|
||||
else the function will return
|
||||
.Dv NULL
|
||||
after having set
|
||||
.Va h_errno
|
||||
|
||||
@ -625,7 +625,7 @@ The functions
|
||||
and
|
||||
.Fn vasprintf
|
||||
first appeared in the GNU C library. This implementation is thought
|
||||
to be compatable but is not derived from the GNU code. This implementation
|
||||
to be compatible but is not derived from the GNU code. This implementation
|
||||
was written by Peter Wemm <peter@FreeBSD.org> and first appeared in
|
||||
.Fx 2.2 .
|
||||
.Sh BUGS
|
||||
|
||||
@ -25,7 +25,7 @@
|
||||
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
||||
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: libdisk.3,v 1.5 1997/02/22 15:06:34 peter Exp $
|
||||
.\" $Id: libdisk.3,v 1.6 1998/03/19 07:34:03 charnier Exp $
|
||||
.\" "
|
||||
.Dd March 15, 1996
|
||||
.Dt LIBDISK 3
|
||||
@ -237,7 +237,7 @@ and
|
||||
are experimental, do not use.
|
||||
.Pp
|
||||
.Fn Create_Chunk
|
||||
creates a chunk with the specified paramters.
|
||||
creates a chunk with the specified parameters.
|
||||
.Pp
|
||||
.Fn All_FreeBSD
|
||||
makes one FreeBSD chunk covering the entire disk; if
|
||||
@ -328,7 +328,7 @@ returns the name strings associated with the specified
|
||||
.Ql subtype .
|
||||
If
|
||||
.Fn slice_type_name
|
||||
returns "unknown" for slices it isn't familar with.
|
||||
returns "unknown" for slices it isn't familiar with.
|
||||
.Ql / .
|
||||
.Sh AUTHORS
|
||||
.Nm Libdisk
|
||||
|
||||
@ -530,5 +530,5 @@ This documentation is probably incomplete.
|
||||
should not modify the supplied
|
||||
.Va argv[0] .
|
||||
.Pp
|
||||
The tokenization functions are not publically defined in
|
||||
The tokenization functions are not publicly defined in
|
||||
.Li <histedit.h> .
|
||||
|
||||
@ -17,7 +17,7 @@
|
||||
.\" 5. Modifications may be freely made to this file providing the above
|
||||
.\" conditions are met.
|
||||
.\"
|
||||
.\" $Id: _secure_path.3,v 1.1 1997/05/10 18:55:37 davidn Exp $
|
||||
.\" $Id: _secure_path.3,v 1.2 1997/05/15 06:06:32 davidn Exp $
|
||||
.\"
|
||||
.Dd May 2, 1997
|
||||
.Os FreeBSD
|
||||
@ -59,7 +59,7 @@ considered secure, -2 if the file does not exist, and
|
||||
is used to log any failure of this function, including the
|
||||
reason, at LOG_ERR priority.
|
||||
.Sh BUGS
|
||||
The checks carried out are rudamentary and no attempt is made
|
||||
The checks carried out are rudimentary and no attempt is made
|
||||
to eliminate race conditions between use of this function and
|
||||
access to the file referenced.
|
||||
.Sh SEE ALSO
|
||||
|
||||
@ -17,7 +17,7 @@
|
||||
.\" 5. Modifications may be freely made to this file providing the above
|
||||
.\" conditions are met.
|
||||
.\"
|
||||
.\" $Id: login_cap.3,v 1.7 1997/05/18 09:14:11 davidn Exp $
|
||||
.\" $Id: login_cap.3,v 1.8 1997/11/05 04:03:05 steve Exp $
|
||||
.\"
|
||||
.Dd December 27, 1996
|
||||
.Os FreeBSD
|
||||
@ -174,7 +174,7 @@ record to be retrieved, the second being an optional directory name.
|
||||
If the first
|
||||
.Ar name
|
||||
argument is NULL, an empty string, or a class that does not exist
|
||||
in the supplimental or system login class database, then the system
|
||||
in the supplemental or system login class database, then the system
|
||||
.Em default
|
||||
record is returned instead.
|
||||
If the second
|
||||
@ -190,7 +190,7 @@ In the context of a
|
||||
.Em login ,
|
||||
it should be noted that some options cannot by overridden by
|
||||
users for two reasons; many options, such as resource settings
|
||||
and deafult process priorities, require root privileges
|
||||
and default process priorities, require root privileges
|
||||
in order to take effect, and other fields in the user's file are
|
||||
not be consulted at all during the early phases of login for
|
||||
security or administrative reasons.
|
||||
@ -330,11 +330,11 @@ parameter is returned, and if an error occurs, the
|
||||
parameter is returned.
|
||||
.It Fn login_getcapsize
|
||||
.Fn login_getcapsize
|
||||
returns a value representing a size (typicially, file or memory)
|
||||
returns a value representing a size (typically, file or memory)
|
||||
which may be expressed as bytes (the default), 512 byte blocks,
|
||||
kilobytes, megabytes, gigabytes, and on systems that support the
|
||||
.Ar long long
|
||||
type, terrabytes.
|
||||
type, terabytes.
|
||||
The suffix used determines the units, and multiple values and
|
||||
units may be used in combination (e.g. 1m500k = 1.5 megabytes).
|
||||
A value with no suffix is interpreted as bytes, B as 512-byte
|
||||
|
||||
@ -17,7 +17,7 @@
|
||||
.\" 5. Modifications may be freely made to this file providing the above
|
||||
.\" conditions are met.
|
||||
.\"
|
||||
.\" $Id: login_class.3,v 1.4 1997/02/22 15:08:20 peter Exp $
|
||||
.\" $Id: login_class.3,v 1.5 1997/04/13 14:12:48 bde Exp $
|
||||
.\"
|
||||
.Dd December 28, 1996
|
||||
.Os FreeBSD
|
||||
@ -49,7 +49,7 @@ accounting settings for users on logging into the system and when
|
||||
selecting an appropriate set of environment and resource settings
|
||||
for system daemons based on login classes.
|
||||
These functions may only be called if the current process is
|
||||
running with root priviledges.
|
||||
running with root privileges.
|
||||
If the LOGIN_SETLOGIN flag is used this function calls
|
||||
.Xr setlogin 2 ,
|
||||
and due care must be taken as detailed in the manpage for that
|
||||
@ -171,7 +171,7 @@ be useful in isolation.
|
||||
.Fn setclasscontext
|
||||
and
|
||||
.Fn setusercontext
|
||||
return -1 if an error occured, or 0 on success.
|
||||
return -1 if an error occurred, or 0 on success.
|
||||
If an error occurs when attempting to set the user, login, group
|
||||
or resources, a message is reported to
|
||||
.Xr syslog 3 ,
|
||||
|
||||
@ -30,7 +30,7 @@
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" @(#)intro.3 8.1 (Berkeley) 6/5/93
|
||||
.\" $Id$
|
||||
.\" $Id: intro.3,v 1.5 1997/02/22 13:24:16 peter Exp $
|
||||
.\"
|
||||
.Dd June 5, 1993
|
||||
.Dt INTRO 3
|
||||
@ -100,7 +100,7 @@ Use of these routines should, for the most part, be avoided.
|
||||
The manual page entry for each compatibility routine
|
||||
indicates the proper interface to use.
|
||||
.It Xr libkvm Pq Fl l Ns Ar kvm
|
||||
Fuctions used to access kernel memory are in this library. They can be used
|
||||
Functions used to access kernel memory are in this library. They can be used
|
||||
against both a running system and a crash dump.
|
||||
.Pq See Xr kvm 3 . )
|
||||
.It Xr libl Pq Fl l Ns Ar l
|
||||
|
||||
@ -30,7 +30,7 @@
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" @(#)queue.3 8.2 (Berkeley) 1/24/94
|
||||
.\" $Id: queue.3,v 1.11 1997/03/09 00:49:00 mpp Exp $
|
||||
.\" $Id: queue.3,v 1.12 1997/03/19 02:57:50 bde Exp $
|
||||
.\"
|
||||
.Dd January 24, 1994
|
||||
.Dt QUEUE 3
|
||||
@ -598,7 +598,7 @@ while (head.lh_first != NULL) { /* List Deletion. */
|
||||
|
||||
n1 = head.lh_first; /* Faster List Delete. */
|
||||
while (n1 != NULL) {
|
||||
n2 = n1->entires.le_next;
|
||||
n2 = n1->entries.le_next;
|
||||
free(n1);
|
||||
n1 = n2;
|
||||
}
|
||||
|
||||
@ -76,7 +76,7 @@ different groups of private addresses
|
||||
can be linked to different public addresses,
|
||||
comprising several distinct many-to-one
|
||||
mappings. Also, a given public address
|
||||
and port can be staticly redirected to
|
||||
and port can be statically redirected to
|
||||
a private address/port.
|
||||
|
||||
The packet aliasing engine was designed
|
||||
@ -212,7 +212,7 @@ unknown host address or unknown port number
|
||||
(e.g. an FTP data connection), this mode bit
|
||||
specifies that a socket be allocated as a place
|
||||
holder to prevent port conflicts. Once a
|
||||
connection is extablished, usually within a
|
||||
connection is established, usually within a
|
||||
minute or so, the socket is closed.
|
||||
.It PKT_ALIAS_UNREGISTERED_ONLY.
|
||||
If this mode bit is set, traffic on the
|
||||
@ -299,7 +299,7 @@ Return codes:
|
||||
.Bl -hang -offset left
|
||||
.It PKT_ALIAS_ERROR.
|
||||
An internal error within the packet aliasing
|
||||
engine occured.
|
||||
engine occurred.
|
||||
.It PKT_ALIAS_OK.
|
||||
The packet aliasing process was successful.
|
||||
.It PKT_ALIAS_IGNORED.
|
||||
@ -333,9 +333,9 @@ The IP packet is pointed to by
|
||||
.Em buffer r,
|
||||
and
|
||||
.Em maxpacketsize
|
||||
indicates the maximum packet size permissable
|
||||
indicates the maximum packet size permissible
|
||||
should the packet length be changed. IP encoding
|
||||
protocols place addresss and port information in
|
||||
protocols place address and port information in
|
||||
the encapsulated data stream which have to be
|
||||
modified and can account for changes in packet
|
||||
length. Well known examples of such protocols
|
||||
@ -345,7 +345,7 @@ Return codes:
|
||||
.Bl -hang -offset left
|
||||
.It PKT_ALIAS_ERROR.
|
||||
An internal error within the packet aliasing
|
||||
engine occured.
|
||||
engine occurred.
|
||||
.It PKT_ALIAS_OK.
|
||||
The packet aliasing process was successful.
|
||||
.It PKT_ALIAS_IGNORED.
|
||||
@ -376,7 +376,7 @@ address translations can be designated.
|
||||
This function specifies that traffic from a
|
||||
given remote address/port to an alias address/port
|
||||
be redirected to a specified local address/port.
|
||||
The paramater
|
||||
The parameter
|
||||
.Em proto
|
||||
can be either IPPROTO_TCP or IPPROTO_UDP, as
|
||||
defined in <netinet/in.h>.
|
||||
@ -682,7 +682,7 @@ number for identifying how individual packets
|
||||
should be handled.)
|
||||
|
||||
Each aliasing link must have a unique
|
||||
combination of the following five quanties:
|
||||
combination of the following five quantities:
|
||||
alias address/port, remote address/port
|
||||
and protocol. This ensures that several
|
||||
machines on a local network can share the
|
||||
@ -699,7 +699,7 @@ sequence. For the case of TCP, the connection
|
||||
can be monitored to see when the associated
|
||||
aliasing link should be deleted. Aliasing links
|
||||
for UDP transactions (and ICMP echo and timestamp
|
||||
equests) work on a simple timeout rule. When
|
||||
requests) work on a simple timeout rule. When
|
||||
no activity is observed on a dynamic link for
|
||||
a certain amount of time it is automatically
|
||||
deleted. Timeout rules also apply to TCP
|
||||
@ -708,7 +708,7 @@ properly.
|
||||
.Ss A.3 Partially Specified Aliasing Links
|
||||
Aliasing links can be partially specified,
|
||||
meaning that the remote address and/or remote
|
||||
ports are unkown. In this case, when a packet
|
||||
ports are unknown. In this case, when a packet
|
||||
matching the incomplete specification is found,
|
||||
a fully specified dynamic link is created. If
|
||||
the original partially specified link is dynamic,
|
||||
@ -750,7 +750,7 @@ the alias address to be used. If no mapping
|
||||
exists, then a default address, usually the
|
||||
address of the packet aliasing host, is used.
|
||||
If necessary, this default address can be
|
||||
changed as often as each indvidual packet
|
||||
changed as often as each individual packet
|
||||
arrives.
|
||||
|
||||
The aliasing port number is determined
|
||||
|
||||
Loading…
Reference in New Issue
Block a user