mirror of https://github.com/mkerrisk/man-pages
Spelling/typo fixes
This commit is contained in:
parent
9fdfa163e5
commit
b956004699
|
@ -124,7 +124,7 @@ function was not implemented, probably because of U.S.A. export restrictions.
|
|||
.\" It is suspected that this may contain a back door which could allow the
|
||||
.\" NSA to decrypt DES encrypted data.
|
||||
.\" .PP
|
||||
.\" Making encrypted data computed using crypt() publically available has
|
||||
.\" Making encrypted data computed using crypt() publicly available has
|
||||
.\" to be considered insecure for the given reasons.
|
||||
.SH "GNU EXTENSION"
|
||||
The glibc2 version of this function has the following additional features.
|
||||
|
|
|
@ -135,7 +135,7 @@ functions,
|
|||
.B GLOB_BRACE
|
||||
which means that
|
||||
.BR csh (1)
|
||||
style brace expresions \fB{a,b}\fR are expanded,
|
||||
style brace expressions \fB{a,b}\fR are expanded,
|
||||
.TP
|
||||
.B GLOB_NOMAGIC
|
||||
which means that the pattern is returned if it contains no metacharacters,
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
.\" Copyright 2002 walter harms (walter.harms@informatik.uni-oldenburg.de)
|
||||
.\" Distributed under GPL
|
||||
.\" I had no way the check the functions out
|
||||
.\" be carefull
|
||||
.\" be careful
|
||||
.TH KEY_SETSECRET 3 2002-07-18 "secure rpc"
|
||||
.SH NAME
|
||||
key_decryptsession, key_encryptsession, key_setsecret, key_gendes,
|
||||
|
|
|
@ -87,7 +87,7 @@ database, or 0 if an error occurred.
|
|||
.SH NOTE
|
||||
These functions are included in libutil, hence you'll need to add
|
||||
.B \-lutil
|
||||
to your compiler commandline.
|
||||
to your compiler command line.
|
||||
|
||||
Note that the
|
||||
member
|
||||
|
|
|
@ -141,7 +141,7 @@ fails.
|
|||
.SH NOTE
|
||||
These functions are included in libutil, hence you'll need to add
|
||||
.B \-lutil
|
||||
to your compiler commandline.
|
||||
to your compiler command line.
|
||||
.SH FILES
|
||||
.I /dev/[pt]ty[pqrstuwxyzabcdePQRST][0123456789abcdef]
|
||||
.SH "CONFORMING TO"
|
||||
|
|
|
@ -87,7 +87,7 @@ etc.) are made available when including
|
|||
As mentioned,
|
||||
.BR system ()
|
||||
ignores SIGINT and SIGQUIT. This may make programs that call it
|
||||
from a loop uninterruptable, unless they take care themselves
|
||||
from a loop uninterruptible, unless they take care themselves
|
||||
to check the exit status of the child. E.g.
|
||||
.br
|
||||
.nf
|
||||
|
|
|
@ -47,7 +47,7 @@ used to occur in the old libbsd. These days, the
|
|||
.B logwtmp
|
||||
function is included in libutil. (Hence you'll need to add
|
||||
.B \-lutil
|
||||
to your compiler commandline to get it.)
|
||||
to your compiler command line to get it.)
|
||||
.SH FILES
|
||||
.TP
|
||||
.I /var/log/wtmp
|
||||
|
|
|
@ -1230,5 +1230,5 @@ Linus Torvalds (and many others)
|
|||
Large parts of this man page have been derived from the
|
||||
Boot Parameter HOWTO (version 1.0.1) written by Paul Gortmaker.
|
||||
More information may be found in this (or a more recent) HOWTO.
|
||||
An uptodate source of information is
|
||||
An up-to-date source of information is
|
||||
.IR /usr/src/linux/Documentation/kernel-parameters.txt .
|
||||
|
|
|
@ -66,7 +66,7 @@ is specified and the IP header has a non-zero destination address then
|
|||
the destination address of the socket is used to route the packet. When
|
||||
.B MSG_DONTROUTE
|
||||
is specified the destination address should refer to a local interface,
|
||||
otherwise a routing table lookup is done anyways but gatewayed routes
|
||||
otherwise a routing table lookup is done anyway but gatewayed routes
|
||||
are ignored.
|
||||
|
||||
If
|
||||
|
|
|
@ -99,7 +99,7 @@ A path segment which contains a colon
|
|||
character can't be used as the first segment of a relative URI path
|
||||
(e.g., "this:that"), because it would be mistaken for a scheme name;
|
||||
precede such segments with ./ (e.g., "./this:that").
|
||||
Note that descendents of MS-DOS (e.g., Microsoft Windows) replace
|
||||
Note that descendants of MS-DOS (e.g., Microsoft Windows) replace
|
||||
devicename colons with the vertical bar ("|") in URIs, so "C:" becomes "C|".
|
||||
.PP
|
||||
A fragment identifier, if included, refers to a particular named portion
|
||||
|
@ -608,7 +608,7 @@ remote operation to be performed.
|
|||
.PP
|
||||
It is clearly unwise to use a URI that contains a password which is
|
||||
intended to be secret. In particular, the use of a password within
|
||||
the 'userinfo' component of a URI is strongly disrecommended except
|
||||
the 'userinfo' component of a URI is strongly recommended against except
|
||||
in those rare cases where the 'password' parameter is intended to be public.
|
||||
.SH "CONFORMING TO"
|
||||
.PP
|
||||
|
|
Loading…
Reference in New Issue