Cleanup some of the Lite2 merge. Most of it is mdoc cleanup,
but in one case the Lite2 changes were flat out wrong and caused the man page to disagree with a header file. There are still some *roff macro calls that were added that I have yet to figure out what to do with in some of the man pages.
This commit is contained in:
parent
4fdffd9e94
commit
2602ef2be2
@ -66,11 +66,9 @@ An interpreter file begins with a line of the form:
|
||||
.Ed
|
||||
.Pp
|
||||
When an interpreter file is
|
||||
.\" was .Fn execve Ap d ,
|
||||
\fBexecve\fP'd,
|
||||
.Sy execve Ap d ,
|
||||
the system
|
||||
.\" was .Fn execve Ap s
|
||||
\fBexecve\fP's
|
||||
.Sy execve Ap s
|
||||
runs the specified
|
||||
.Em interpreter .
|
||||
If the optional
|
||||
@ -78,16 +76,13 @@ If the optional
|
||||
is specified, it becomes the first argument to the
|
||||
.Em interpreter ,
|
||||
and the name of the originally
|
||||
.\" was .Fn execve Ap d
|
||||
\fBexecve\fP'd
|
||||
.Sy execve Ap d
|
||||
file becomes the second argument;
|
||||
otherwise, the name of the originally
|
||||
.\" was .Fn execve Ap d
|
||||
\fBexecve\fP'd
|
||||
.Sy execve Ap d
|
||||
file becomes the first argument. The original arguments are shifted over to
|
||||
become the subsequent arguments. The zeroth argument, normally the name of the
|
||||
.\" was .Fn execve Ap d
|
||||
\fBexecve\fP'd
|
||||
.Sy execve Ap d
|
||||
file, is left unchanged.
|
||||
.Pp
|
||||
The argument
|
||||
|
@ -157,7 +157,7 @@ executable file.
|
||||
A file descriptor argument was out of range, referred to no open file,
|
||||
or a read (write) request was made to a file that was only open for
|
||||
writing (reading).
|
||||
.sp
|
||||
.Pp
|
||||
.It Er 10 ECHILD Em "\&No child processes" .
|
||||
A
|
||||
.Xr wait 2
|
||||
@ -325,7 +325,7 @@ addresses with
|
||||
Internet protocols.
|
||||
.It Er 48 EADDRINUSE Em "Address already in use" .
|
||||
Only one usage of each address is normally permitted.
|
||||
.sp
|
||||
.Pp
|
||||
.It Er 49 EADDRNOTAVAIL Em "Cannot assign requested address" .
|
||||
Normally results from an attempt to create a socket with an
|
||||
address not on this machine.
|
||||
|
@ -42,7 +42,7 @@
|
||||
.Fd #include <signal.h>
|
||||
.Bd -literal
|
||||
struct sigaltstack {
|
||||
caddr_t ss_base;
|
||||
caddr_t ss_sp;
|
||||
long ss_size;
|
||||
int ss_flags;
|
||||
};
|
||||
@ -74,7 +74,7 @@ If
|
||||
.Dv SS_DISABLE
|
||||
is set in
|
||||
.Fa ss_flags ,
|
||||
.Fa ss_base
|
||||
.Fa ss_sp
|
||||
and
|
||||
.Fa ss_size
|
||||
are ignored and the signal stack will be disabled.
|
||||
@ -106,7 +106,7 @@ is defined to be the number of bytes/chars that would be used to cover
|
||||
the usual case when allocating an alternate stack area.
|
||||
The following code fragment is typically used to allocate an alternate stack.
|
||||
.Bd -literal -offset indent
|
||||
if ((sigstk.ss_base = malloc(SIGSTKSZ)) == NULL)
|
||||
if ((sigstk.ss_sp = malloc(SIGSTKSZ)) == NULL)
|
||||
/* error return */
|
||||
sigstk.ss_size = SIGSTKSZ;
|
||||
sigstk.ss_flags = 0;
|
||||
|
Loading…
x
Reference in New Issue
Block a user