connect.2, pidfd_send_signal.2, ptrace.2, socket.7: ffix

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2020-06-21 09:26:30 +02:00
parent 7f740303b2
commit 575bac0fdd
4 changed files with 4 additions and 4 deletions

View File

@ -130,7 +130,7 @@ may dissolve the association by connecting to an address with the
member of
.I sockaddr
set to
.BR AF_UNSPEC;
.BR AF_UNSPEC ;
thereafter, the socket can be connected to another address.
.RB ( AF_UNSPEC
is supported on Linux since kernel 2.2.)

View File

@ -69,7 +69,7 @@ is set to 0;
.IP *
.I si_code
is set to
.BR SI_USER;
.BR SI_USER ;
.IP *
.I si_pid
is set to the caller's PID; and

View File

@ -1719,7 +1719,7 @@ no syscall-exit-stop occurs.
Note that all mentions
.BR PTRACE_SYSEMU
apply equally to
.BR PTRACE_SYSEMU_SINGLESTEP.
.BR PTRACE_SYSEMU_SINGLESTEP .
.PP
However, even if the tracee was continued using
.BR PTRACE_SYSCALL ,

View File

@ -978,7 +978,7 @@ for details on control messages.
A socket cannot mix
.B SO_TIMESTAMP
and
.BR SO_TIMESTAMPNS:
.BR SO_TIMESTAMPNS :
the two modes are mutually exclusive.
.TP
.B SO_TYPE