Index: stable/11/lib/libc/gen/signal.3
===================================================================
--- stable/11/lib/libc/gen/signal.3	(revision 331184)
+++ stable/11/lib/libc/gen/signal.3	(revision 331185)
@@ -1,272 +1,276 @@
 .\" Copyright (c) 1980, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\" 4. Neither the name of the University nor the names of its contributors
 .\"    may be used to endorse or promote products derived from this software
 .\"    without specific prior written permission.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, 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.
 .\"
 .\"     @(#)signal.3	8.3 (Berkeley) 4/19/94
 .\" $FreeBSD$
 .\"
-.Dd June 7, 2004
+.Dd December 1, 2017
 .Dt SIGNAL 3
 .Os
 .Sh NAME
 .Nm signal
 .Nd simplified software signal facilities
 .Sh LIBRARY
 .Lb libc
 .Sh SYNOPSIS
 .In signal.h
 .\" The following is Quite Ugly, but syntactically correct.
 .\" Don't try to fix it.
 .Ft void
 .Fn \*(lp*signal "int sig" "void \*(lp*func\*(rp\*(lpint\*(rp\*(rp\*(rp\*(lpint"
 .Pp
 or in
 .Fx Ap s
 equivalent but easier to read typedef'd version:
 .Ft typedef "void \*(lp*sig_t\*(rp \*(lpint\*(rp" ;
 .Pp
 .Ft sig_t
 .Fn signal "int sig" "sig_t func"
 .Sh DESCRIPTION
 This
 .Fn signal
 facility
 is a simplified interface to the more general
 .Xr sigaction 2
 facility.
 .Pp
 Signals allow the manipulation of a process from outside its
 domain as well as allowing the process to manipulate itself or
 copies of itself (children).
 There are two general types of signals:
 those that cause termination of a process and those that do not.
 Signals which cause termination of a program might result from
 an irrecoverable error or might be the result of a user at a terminal
 typing the `interrupt' character.
 Signals are used when a process is stopped because it wishes to access
 its control terminal while in the background (see
 .Xr tty 4 ) .
 Signals are optionally generated
 when a process resumes after being stopped,
 when the status of child processes changes,
 or when input is ready at the control terminal.
 Most signals result in the termination of the process receiving them
 if no action
 is taken; some signals instead cause the process receiving them
 to be stopped, or are simply discarded if the process has not
 requested otherwise.
 Except for the
 .Dv SIGKILL
 and
 .Dv SIGSTOP
 signals, the
 .Fn signal
 function allows for a signal to be caught, to be ignored, or to generate
 an interrupt.
 These signals are defined in the file
 .In signal.h :
 .Bl -column No ".Dv SIGVTALRM" "create core image"
 .It Sy "Num" Ta Sy "Name" Ta Sy "Default Action" Ta Sy "Description"
 .It 1 Ta Dv SIGHUP Ta "terminate process" Ta "terminal line hangup"
 .It 2 Ta Dv SIGINT Ta "terminate process" Ta "interrupt program"
 .It 3 Ta Dv SIGQUIT Ta "create core image" Ta "quit program"
 .It 4 Ta Dv SIGILL Ta "create core image" Ta "illegal instruction"
 .It 5 Ta Dv SIGTRAP Ta "create core image" Ta "trace trap"
 .It 6 Ta Dv SIGABRT Ta "create core image" Ta "abort program"
 (formerly
 .Dv SIGIOT )
 .It 7 Ta Dv SIGEMT Ta "create core image" Ta "emulate instruction executed"
 .It 8 Ta Dv SIGFPE Ta "create core image" Ta "floating-point exception"
 .It 9 Ta Dv SIGKILL Ta "terminate process" Ta "kill program"
 .It 10 Ta Dv SIGBUS Ta "create core image" Ta "bus error"
 .It 11 Ta Dv SIGSEGV Ta "create core image" Ta "segmentation violation"
 .It 12 Ta Dv SIGSYS Ta "create core image" Ta "non-existent system call invoked"
 .It 13 Ta Dv SIGPIPE Ta "terminate process" Ta "write on a pipe with no reader"
 .It 14 Ta Dv SIGALRM Ta "terminate process" Ta "real-time timer expired"
 .It 15 Ta Dv SIGTERM Ta "terminate process" Ta "software termination signal"
 .It 16 Ta Dv SIGURG Ta "discard signal" Ta "urgent condition present on socket"
 .It 17 Ta Dv SIGSTOP Ta "stop process" Ta "stop (cannot be caught or ignored)"
 .It 18 Ta Dv SIGTSTP Ta "stop process" Ta "stop signal generated from keyboard"
 .It 19 Ta Dv SIGCONT Ta "discard signal" Ta "continue after stop"
 .It 20 Ta Dv SIGCHLD Ta "discard signal" Ta "child status has changed"
 .It 21 Ta Dv SIGTTIN Ta "stop process" Ta "background read attempted from"
 control terminal
 .It 22 Ta Dv SIGTTOU Ta "stop process" Ta "background write attempted to"
 control terminal
 .It 23 Ta Dv SIGIO Ta "discard signal" Ta Tn "I/O"
 is possible on a descriptor (see
 .Xr fcntl 2 )
 .It 24 Ta Dv SIGXCPU Ta "terminate process" Ta "cpu time limit exceeded (see"
 .Xr setrlimit 2 )
 .It 25 Ta Dv SIGXFSZ Ta "terminate process" Ta "file size limit exceeded (see"
 .Xr setrlimit 2 )
 .It 26 Ta Dv SIGVTALRM Ta "terminate process" Ta "virtual time alarm (see"
 .Xr setitimer 2 )
 .It 27 Ta Dv SIGPROF Ta "terminate process" Ta "profiling timer alarm (see"
 .Xr setitimer 2 )
 .It 28 Ta Dv SIGWINCH Ta "discard signal" Ta "Window size change"
 .It 29 Ta Dv SIGINFO Ta "discard signal" Ta "status request from keyboard"
 .It 30 Ta Dv SIGUSR1 Ta "terminate process" Ta "User defined signal 1"
 .It 31 Ta Dv SIGUSR2 Ta "terminate process" Ta "User defined signal 2"
 .It 32 Ta Dv SIGTHR Ta "terminate process" Ta "thread interrupt"
 .It 33 Ta Dv SIGLIBRT Ta "terminate process" Ta "real-time library interrupt"
 .El
 .Pp
 The
 .Fa sig
 argument specifies which signal was received.
 The
 .Fa func
 procedure allows a user to choose the action upon receipt of a signal.
 To set the default action of the signal to occur as listed above,
 .Fa func
 should be
 .Dv SIG_DFL .
 A
 .Dv SIG_DFL
 resets the default action.
 To ignore the signal
 .Fa func
 should be
 .Dv SIG_IGN .
 This will cause subsequent instances of the signal to be ignored
 and pending instances to be discarded.
 If
 .Dv SIG_IGN
 is not used,
 further occurrences of the signal are
 automatically blocked and
 .Fa func
 is called.
 .Pp
 The handled signal is unblocked when the
 function returns and
 the process continues from where it left off when the signal occurred.
 .Bf -symbolic
 Unlike previous signal facilities, the handler
 func() remains installed after a signal has been delivered.
 .Ef
 .Pp
 For some system calls, if a signal is caught while the call is
 executing and the call is prematurely terminated,
 the call is automatically restarted.
 Any handler installed with
 .Xr signal 3
 will have the
 .Dv SA_RESTART
 flag set, meaning that any restartable system call will not return on
 receipt of a signal.
 The affected system calls include
 .Xr read 2 ,
 .Xr write 2 ,
 .Xr sendto 2 ,
 .Xr recvfrom 2 ,
 .Xr sendmsg 2
 and
 .Xr recvmsg 2
 on a communications channel or a low speed device
 and during a
 .Xr ioctl 2
 or
 .Xr wait 2 .
 However, calls that have already committed are not restarted,
 but instead return a partial success (for example, a short read count).
 These semantics could be changed with
 .Xr siginterrupt 3 .
 .Pp
 When a process which has installed signal handlers forks,
 the child process inherits the signals.
 All caught signals may be reset to their default action by a call
 to the
 .Xr execve 2
 function;
 ignored signals remain ignored.
 .Pp
 If a process explicitly specifies
 .Dv SIG_IGN
 as the action for the signal
 .Dv SIGCHLD ,
 the system will not create zombie processes when children
 of the calling process exit.
 As a consequence, the system will discard the exit status
 from the child processes.
 If the calling process subsequently issues a call to
 .Xr wait 2
 or equivalent, it will block until all of the calling process's
 children terminate, and then return a value of \-1 with
 .Va errno
 set to
 .Er ECHILD .
 .Pp
 See
 .Xr sigaction 2
 for a list of functions
 that are considered safe for use in signal handlers.
 .Sh RETURN VALUES
 The previous action is returned on a successful call.
 Otherwise, SIG_ERR is returned and the global variable
 .Va errno
 is set to indicate the error.
 .Sh ERRORS
 The
 .Fn signal
 function
 will fail and no action will take place if one of the
 following occur:
 .Bl -tag -width Er
 .It Bq Er EINVAL
 The
 .Fa sig
 argument
 is not a valid signal number.
 .It Bq Er EINVAL
 An attempt is made to ignore or supply a handler for
 .Dv SIGKILL
 or
 .Dv SIGSTOP .
 .El
 .Sh SEE ALSO
 .Xr kill 1 ,
 .Xr kill 2 ,
 .Xr ptrace 2 ,
 .Xr sigaction 2 ,
 .Xr sigaltstack 2 ,
 .Xr sigprocmask 2 ,
 .Xr sigsuspend 2 ,
 .Xr wait 2 ,
 .Xr fpsetmask 3 ,
 .Xr setjmp 3 ,
 .Xr siginterrupt 3 ,
 .Xr tty 4
 .Sh HISTORY
 The
+.Fn signal
+function appeared in
+.At v4 .
+The current
 .Nm
 facility appeared in
 .Bx 4.0 .
 The option to avoid the creation of child zombies through ignoring
 .Dv SIGCHLD
 appeared in
 .Fx 5.0 .
Index: stable/11/lib/libc/sys/dup.2
===================================================================
--- stable/11/lib/libc/sys/dup.2	(revision 331184)
+++ stable/11/lib/libc/sys/dup.2	(revision 331185)
@@ -1,169 +1,171 @@
 .\" Copyright (c) 1980, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\" 4. Neither the name of the University nor the names of its contributors
 .\"    may be used to endorse or promote products derived from this software
 .\"    without specific prior written permission.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, 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.
 .\"
 .\"     @(#)dup.2	8.1 (Berkeley) 6/4/93
 .\" $FreeBSD$
 .\"
-.Dd June 1, 2013
+.Dd December 1, 2017
 .Dt DUP 2
 .Os
 .Sh NAME
 .Nm dup ,
 .Nm dup2
 .Nd duplicate an existing file descriptor
 .Sh LIBRARY
 .Lb libc
 .Sh SYNOPSIS
 .In unistd.h
 .Ft int
 .Fn dup "int oldd"
 .Ft int
 .Fn dup2 "int oldd" "int newd"
 .Sh DESCRIPTION
 The
 .Fn dup
 system call
 duplicates an existing object descriptor and returns its value to
 the calling process
 .Fa ( newd
 =
 .Fn dup oldd ) .
 The argument
 .Fa oldd
 is a small non-negative integer index in
 the per-process descriptor table.
 The new descriptor returned by the call
 is the lowest numbered descriptor
 currently not in use by the process.
 .Pp
 The object referenced by the descriptor does not distinguish
 between
 .Fa oldd
 and
 .Fa newd
 in any way.
 Thus if
 .Fa newd
 and
 .Fa oldd
 are duplicate references to an open
 file,
 .Xr read 2 ,
 .Xr write 2
 and
 .Xr lseek 2
 calls all move a single pointer into the file,
 and append mode, non-blocking I/O and asynchronous I/O options
 are shared between the references.
 If a separate pointer into the file is desired, a different
 object reference to the file must be obtained by issuing an
 additional
 .Xr open 2
 system call.
 The close-on-exec flag on the new file descriptor is unset.
 .Pp
 In
 .Fn dup2 ,
 the value of the new descriptor
 .Fa newd
 is specified.
 If this descriptor is already in use and
 .Fa oldd
 \*(Ne
 .Fa newd ,
 the descriptor is first deallocated as if the
 .Xr close 2
 system call had been used.
 If
 .Fa oldd
 is not a valid descriptor, then
 .Fa newd
 is not closed.
 If
 .Fa oldd
 ==
 .Fa newd
 and
 .Fa oldd
 is a valid descriptor, then
 .Fn dup2
 is successful, and does nothing.
 .Sh RETURN VALUES
 These calls return the new file descriptor if successful;
 otherwise the value -1 is returned and
 the external variable
 .Va errno
 is set to indicate the cause of the error.
 .Sh ERRORS
 The
 .Fn dup
 system call fails if:
 .Bl -tag -width Er
 .It Bq Er EBADF
 The
 .Fa oldd
 argument
 is not a valid active descriptor
 .It Bq Er EMFILE
 Too many descriptors are active.
 .El
 .Pp
 The
 .Fn dup2
 system call fails if:
 .Bl -tag -width Er
 .It Bq Er EBADF
 The
 .Fa oldd
 argument is not a valid active descriptor or the
 .Fa newd
 argument is negative or exceeds the maximum allowable descriptor number
 .El
 .Sh SEE ALSO
 .Xr accept 2 ,
 .Xr close 2 ,
 .Xr fcntl 2 ,
 .Xr getdtablesize 2 ,
 .Xr open 2 ,
 .Xr pipe 2 ,
 .Xr socket 2 ,
 .Xr socketpair 2 ,
 .Xr dup3 3
 .Sh STANDARDS
 The
 .Fn dup
 and
 .Fn dup2
 system calls are expected to conform to
 .St -p1003.1-90 .
 .Sh HISTORY
 The
 .Fn dup
-and
+function appeared in
+.At v3 .
+The
 .Fn dup2
-functions appeared in
+function appeared in
 .At v7 .
Index: stable/11/lib/libc/sys/getuid.2
===================================================================
--- stable/11/lib/libc/sys/getuid.2	(revision 331184)
+++ stable/11/lib/libc/sys/getuid.2	(revision 331185)
@@ -1,89 +1,89 @@
 .\" Copyright (c) 1980, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\" 4. Neither the name of the University nor the names of its contributors
 .\"    may be used to endorse or promote products derived from this software
 .\"    without specific prior written permission.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, 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.
 .\"
 .\"     @(#)getuid.2	8.1 (Berkeley) 6/4/93
 .\" $FreeBSD$
 .\"
 .Dd December 15, 2015
 .Dt GETUID 2
 .Os
 .Sh NAME
 .Nm getuid ,
 .Nm geteuid
 .Nd get user identification
 .Sh LIBRARY
 .Lb libc
 .Sh SYNOPSIS
 .In unistd.h
 .Ft uid_t
 .Fn getuid void
 .Ft uid_t
 .Fn geteuid void
 .Sh DESCRIPTION
 The
 .Fn getuid
 system call returns the real user ID of the calling process.
 The
 .Fn geteuid
 system call
 returns the effective user ID of the calling process.
 .Pp
 The real user ID is that of the user who has invoked the program.
 As the effective user ID
 gives the process additional permissions during
 execution of
 .Dq Em set-user-ID
 mode processes,
 .Fn getuid
 is used to determine the real-user-id of the calling process.
 .Sh ERRORS
 The
 .Fn getuid
 and
 .Fn geteuid
 system calls are always successful, and no return value is reserved to
 indicate an error.
 .Sh SEE ALSO
 .Xr getgid 2 ,
 .Xr issetugid 2 ,
 .Xr setgid 2 ,
 .Xr setreuid 2 ,
 .Xr setuid 2
 .Sh STANDARDS
 The
 .Fn geteuid
 and
 .Fn getuid
 system calls are expected to conform to
 .St -p1003.1-90 .
 .Sh HISTORY
 The
 .Fn getuid
 and
 .Fn geteuid
 functions appeared in
-.At v7 .
+.At v4 .
Index: stable/11/lib/libc/sys/kill.2
===================================================================
--- stable/11/lib/libc/sys/kill.2	(revision 331184)
+++ stable/11/lib/libc/sys/kill.2	(revision 331185)
@@ -1,156 +1,160 @@
 .\" Copyright (c) 1980, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\" 4. Neither the name of the University nor the names of its contributors
 .\"    may be used to endorse or promote products derived from this software
 .\"    without specific prior written permission.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, 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.
 .\"
 .\"     @(#)kill.2	8.3 (Berkeley) 4/19/94
 .\" $FreeBSD$
 .\"
-.Dd March 15, 2012
+.Dd December 1, 2017
 .Dt KILL 2
 .Os
 .Sh NAME
 .Nm kill
 .Nd send signal to a process
 .Sh LIBRARY
 .Lb libc
 .Sh SYNOPSIS
 .In sys/types.h
 .In signal.h
 .Ft int
 .Fn kill "pid_t pid" "int sig"
 .Sh DESCRIPTION
 The
 .Fn kill
 system call sends the signal given by
 .Fa sig
 to
 .Fa pid ,
 a
 process or a group of processes.
 The
 .Fa sig
 argument
 may be one of the signals specified in
 .Xr sigaction 2
 or it may be 0, in which case
 error checking is performed but no
 signal is actually sent.
 This can be used to check the validity of
 .Fa pid .
 .Pp
 For a process to have permission to send a signal to a process designated
 by
 .Fa pid ,
 the user must be the super-user, or
 the real or saved user ID of the receiving process must match
 the real or effective user ID of the sending process.
 A single exception is the signal SIGCONT, which may always be sent
 to any process with the same session ID as the sender.
 In addition, if the
 .Va security.bsd.conservative_signals
 .Xr sysctl 9
 is set to 1, the user is not a super-user, and
 the receiver is set-uid, then
 only job control and terminal control signals may
 be sent (in particular, only SIGKILL, SIGINT, SIGTERM, SIGALRM,
 SIGSTOP, SIGTTIN, SIGTTOU, SIGTSTP, SIGHUP, SIGUSR1, SIGUSR2).
 .Bl -tag -width Ds
 .It \&If Fa pid No \&is greater than zero :
 The
 .Fa sig
 signal
 is sent to the process whose ID is equal to
 .Fa pid .
 .It \&If Fa pid No \&is zero :
 The
 .Fa sig
 signal
 is sent to all processes whose group ID is equal
 to the process group ID of the sender, and for which the
 process has permission;
 this is a variant of
 .Xr killpg 2 .
 .It \&If Fa pid No \&is -1 :
 If the user has super-user privileges,
 the signal is sent to all processes excluding
 system processes
 (with
 .Dv P_SYSTEM
 flag set),
 process with ID 1
 (usually
 .Xr init 8 ) ,
 and the process sending the signal.
 If the user is not the super user, the signal is sent to all processes
 with the same uid as the user excluding the process sending the signal.
 No error is returned if any process could be signaled.
 .El
 .Pp
 For compatibility with System V,
 if the process number is negative but not -1,
 the signal is sent to all processes whose process group ID
 is equal to the absolute value of the process number.
 This is a variant of
 .Xr killpg 2 .
 .Sh RETURN VALUES
 .Rv -std kill
 .Sh ERRORS
 The
 .Fn kill
 system call
 will fail and no signal will be sent if:
 .Bl -tag -width Er
 .It Bq Er EINVAL
 The
 .Fa sig
 argument
 is not a valid signal number.
 .It Bq Er ESRCH
 No process or process group can be found corresponding to that specified by
 .Fa pid .
 .It Bq Er EPERM
 The sending process does not have permission to send
 .Va sig
 to the receiving process.
 .El
 .Sh SEE ALSO
 .Xr getpgrp 2 ,
 .Xr getpid 2 ,
 .Xr killpg 2 ,
 .Xr sigaction 2 ,
 .Xr sigqueue 2 ,
 .Xr raise 3 ,
 .Xr init 8
 .Sh STANDARDS
 The
 .Fn kill
 system call is expected to conform to
 .St -p1003.1-90 .
 .Sh HISTORY
-The
+A version of the
 .Fn kill
 function appeared in
-.At v7 .
+.At v3 .
+The signal number was added to the
+.Fn kill
+function in
+.At v4 .
Index: stable/11/lib/libc/sys/mknod.2
===================================================================
--- stable/11/lib/libc/sys/mknod.2	(revision 331184)
+++ stable/11/lib/libc/sys/mknod.2	(revision 331185)
@@ -1,182 +1,182 @@
 .\" Copyright (c) 1980, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\" 4. Neither the name of the University nor the names of its contributors
 .\"    may be used to endorse or promote products derived from this software
 .\"    without specific prior written permission.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, 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.
 .\"
 .\"     @(#)mknod.2	8.1 (Berkeley) 6/4/93
 .\" $FreeBSD$
 .\"
 .Dd January 16, 2011
 .Dt MKNOD 2
 .Os
 .Sh NAME
 .Nm mknod ,
 .Nm mknodat
 .Nd make a special file node
 .Sh LIBRARY
 .Lb libc
 .Sh SYNOPSIS
 .In sys/stat.h
 .Ft int
 .Fn mknod "const char *path" "mode_t mode" "dev_t dev"
 .Ft int
 .Fn mknodat "int fd" "const char *path" "mode_t mode" "dev_t dev"
 .Sh DESCRIPTION
 The file system node
 .Fa path
 is created with the file type and access permissions specified in
 .Fa mode .
 The access permissions are modified by the process's umask value.
 .Pp
 If
 .Fa mode
 indicates a block or character special file,
 .Fa dev
 is a configuration dependent specification denoting a particular device
 on the system.
 Otherwise,
 .Fa dev
 is ignored.
 .Pp
 The
 .Fn mknod
 system call
 requires super-user privileges.
 .Pp
 The
 .Fn mknodat
 system call is equivalent to
 .Fn mknod
 except in the case where
 .Fa path
 specifies a relative path.
 In this case the newly created device node is created relative to the
 directory associated with the file descriptor
 .Fa fd
 instead of the current working directory.
 If
 .Fn mknodat
 is passed the special value
 .Dv AT_FDCWD
 in the
 .Fa fd
 parameter, the current working directory is used and the behavior is
 identical to a call to
 .Fn mknod .
 .Sh RETURN VALUES
 .Rv -std mknod
 .Sh ERRORS
 The
 .Fn mknod
 system call
 will fail and the file will be not created if:
 .Bl -tag -width Er
 .It Bq Er ENOTDIR
 A component of the path prefix is not a directory.
 .It Bq Er ENAMETOOLONG
 A component of a pathname exceeded 255 characters,
 or an entire path name exceeded 1023 characters.
 .It Bq Er ENOENT
 A component of the path prefix does not exist.
 .It Bq Er EACCES
 Search permission is denied for a component of the path prefix.
 .It Bq Er ELOOP
 Too many symbolic links were encountered in translating the pathname.
 .It Bq Er EPERM
 The process's effective user ID is not super-user.
 .It Bq Er EIO
 An I/O error occurred while making the directory entry or allocating the inode.
 .It Bq Er ENOSPC
 The directory in which the entry for the new node is being placed
 cannot be extended because there is no space left on the file
 system containing the directory.
 .It Bq Er ENOSPC
 There are no free inodes on the file system on which the
 node is being created.
 .It Bq Er EDQUOT
 The directory in which the entry for the new node
 is being placed cannot be extended because the
 user's quota of disk blocks on the file system
 containing the directory has been exhausted.
 .It Bq Er EDQUOT
 The user's quota of inodes on the file system on
 which the node is being created has been exhausted.
 .It Bq Er EROFS
 The named file resides on a read-only file system.
 .It Bq Er EEXIST
 The named file exists.
 .It Bq Er EFAULT
 The
 .Fa path
 argument
 points outside the process's allocated address space.
 .It Bq Er EINVAL
 Creating anything else than a block or character special
 file (or a
 .Em whiteout )
 is not supported.
 .El
 .Pp
 In addition to the errors returned by the
 .Fn mknod ,
 the
 .Fn mknodat
 may fail if:
 .Bl -tag -width Er
 .It Bq Er EBADF
 The
 .Fa path
 argument does not specify an absolute path and the
 .Fa fd
 argument is neither
 .Dv AT_FDCWD
 nor a valid file descriptor open for searching.
 .It Bq Er ENOTDIR
 The
 .Fa path
 argument is not an absolute path and
 .Fa fd
 is neither
 .Dv AT_FDCWD
 nor a file descriptor associated with a directory.
 .El
 .Sh SEE ALSO
 .Xr chmod 2 ,
 .Xr mkfifo 2 ,
 .Xr stat 2 ,
 .Xr umask 2
 .Sh STANDARDS
 The
 .Fn mknodat
 system call follows The Open Group Extended API Set 2 specification.
 .Sh HISTORY
 The
 .Fn mknod
 function appeared in
-.At v6 .
+.At v4 .
 The
 .Fn mknodat
 system call appeared in
 .Fx 8.0 .
Index: stable/11/lib/libc/sys/pipe.2
===================================================================
--- stable/11/lib/libc/sys/pipe.2	(revision 331184)
+++ stable/11/lib/libc/sys/pipe.2	(revision 331185)
@@ -1,178 +1,178 @@
 .\" Copyright (c) 1980, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\" 4. Neither the name of the University nor the names of its contributors
 .\"    may be used to endorse or promote products derived from this software
 .\"    without specific prior written permission.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, 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.
 .\"
 .\"     @(#)pipe.2	8.1 (Berkeley) 6/4/93
 .\" $FreeBSD$
 .\"
-.Dd July 20, 2016
+.Dd December 1, 2017
 .Dt PIPE 2
 .Os
 .Sh NAME
 .Nm pipe ,
 .Nm pipe2
 .Nd create descriptor pair for interprocess communication
 .Sh LIBRARY
 .Lb libc
 .Sh SYNOPSIS
 .In unistd.h
 .Ft int
 .Fn pipe "int fildes[2]"
 .Ft int
 .Fn pipe2 "int fildes[2]" "int flags"
 .Sh DESCRIPTION
 The
 .Fn pipe
 function
 creates a
 .Em pipe ,
 which is an object allowing
 bidirectional data flow,
 and allocates a pair of file descriptors.
 .Pp
 The
 .Fn pipe2
 system call allows control over the attributes of the file descriptors
 via the
 .Fa flags
 argument.
 Values for
 .Fa flags
 are constructed by a bitwise-inclusive OR of flags from the following
 list, defined in
 .In fcntl.h :
 .Bl -tag -width ".Dv O_NONBLOCK"
 .It Dv O_CLOEXEC
 Set the close-on-exec flag for the new file descriptors.
 .It Dv O_NONBLOCK
 Set the non-blocking flag for the ends of the pipe.
 .El
 .Pp
 If the
 .Fa flags
 argument is 0, the behavior is identical to a call to
 .Fn pipe .
 .Pp
 By convention, the first descriptor is normally used as the
 .Em read end
 of the pipe,
 and the second is normally the
 .Em write end ,
 so that data written to
 .Fa fildes[1]
 appears on (i.e., can be read from)
 .Fa fildes[0] .
 This allows the output of one program to be
 sent
 to another program:
 the source's standard output is set up to be
 the write end of the pipe,
 and the sink's standard input is set up to be
 the read end of the pipe.
 The pipe itself persists until all its associated descriptors are
 closed.
 .Pp
 A pipe that has had an end closed is considered
 .Em widowed .
 Writing on such a pipe causes the writing process to receive
 a
 .Dv SIGPIPE
 signal.
 Widowing a pipe is the only way to deliver end-of-file to a reader:
 after the reader consumes any buffered data, reading a widowed pipe
 returns a zero count.
 .Pp
 The bidirectional nature of this implementation of pipes is not
 portable to older systems, so it is recommended to use the convention
 for using the endpoints in the traditional manner when using a
 pipe in one direction.
 .Sh IMPLEMENTATION NOTES
 The
 .Fn pipe
 function calls the
 .Fn pipe2
 system call.
 As a result, system call traces such as those captured by
 .Xr dtrace 1
 or
 .Xr ktrace 1
 will show calls to
 .Fn pipe2 .
 .Sh RETURN VALUES
 .Rv -std pipe
 .Sh ERRORS
 The
 .Fn pipe
 and
 .Fn pipe2
 system calls will fail if:
 .Bl -tag -width Er
 .It Bq Er EFAULT
 .Ar fildes
 argument points to an invalid memory location.
 .It Bq Er EMFILE
 Too many descriptors are active.
 .It Bq Er ENFILE
 The system file table is full.
 .It Bq Er ENOMEM
 Not enough kernel memory to establish a pipe.
 .El
 .Pp
 The
 .Fn pipe2
 system call will also fail if:
 .Bl -tag -width Er
 .It Bq Er EINVAL
 The
 .Fa flags
 argument is invalid.
 .El
 .Sh SEE ALSO
 .Xr sh 1 ,
 .Xr fork 2 ,
 .Xr read 2 ,
 .Xr socketpair 2 ,
 .Xr write 2
 .Sh HISTORY
 The
 .Fn pipe
 function appeared in
 .At v3 .
 .Pp
 Bidirectional pipes were first used on
 .At V.4 .
 .Pp
 The
 .Fn pipe2
 function appeared in
 .Fx 10.0 .
 .Pp
 The
 .Fn pipe
 function became a wrapper around
 .Fn pipe2
 in
 .Fx 11.0 .
Index: stable/11/lib/libc/sys/profil.2
===================================================================
--- stable/11/lib/libc/sys/profil.2	(revision 331184)
+++ stable/11/lib/libc/sys/profil.2	(revision 331185)
@@ -1,122 +1,122 @@
 .\" Copyright (c) 1993
 .\"	The Regents of the University of California.  All rights reserved.
 .\"
 .\" This code is derived from software contributed to Berkeley by
 .\" Donn Seeley of BSDI.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\" 4. Neither the name of the University nor the names of its contributors
 .\"    may be used to endorse or promote products derived from this software
 .\"    without specific prior written permission.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, 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.
 .\"
 .\"	@(#)profil.2	8.1 (Berkeley) 6/4/93
 .\" $FreeBSD$
 .\"
-.Dd June 4, 1993
+.Dd December 1, 2017
 .Dt PROFIL 2
 .Os
 .Sh NAME
 .Nm profil
 .Nd control process profiling
 .Sh LIBRARY
 .Lb libc
 .Sh SYNOPSIS
 .In unistd.h
 .Ft int
 .Fn profil "char *samples" "size_t size" "vm_offset_t offset" "int scale"
 .Sh DESCRIPTION
 The
 .Fn profil
 system call enables or disables
 program counter profiling of the current process.
 If profiling is enabled,
 then at every profiling clock tick,
 the kernel updates an appropriate count in the
 .Fa samples
 buffer.
 The frequency of the profiling clock is recorded
 in the header in the profiling output file.
 .Pp
 The buffer
 .Fa samples
 contains
 .Fa size
 bytes and is divided into
 a series of 16-bit bins.
 Each bin counts the number of times the program counter
 was in a particular address range in the process
 when a profiling clock tick occurred while profiling was enabled.
 For a given program counter address,
 the number of the corresponding bin is given
 by the relation:
 .Bd -literal -offset indent
 [(pc - offset) / 2] * scale / 65536
 .Ed
 .Pp
 The
 .Fa offset
 argument is the lowest address at which
 the kernel takes program counter samples.
 The
 .Fa scale
 argument ranges from 1 to 65536 and
 can be used to change the span of the bins.
 A scale of 65536 maps each bin to 2 bytes of address range;
 a scale of 32768 gives 4 bytes, 16384 gives 8 bytes and so on.
 Intermediate values provide approximate intermediate ranges.
 A
 .Fa scale
 value of 0 disables profiling.
 .Sh RETURN VALUES
 .Rv -std profil
 .Sh FILES
 .Bl -tag -width /usr/lib/gcrt0.o -compact
 .It Pa /usr/lib/gcrt0.o
 profiling C run-time startup file
 .It Pa gmon.out
 conventional name for profiling output file
 .El
 .Sh ERRORS
 The following error may be reported:
 .Bl -tag -width Er
 .It Bq Er EFAULT
 The buffer
 .Fa samples
 contains an invalid address.
 .El
 .Sh SEE ALSO
 .Xr gprof 1
 .Sh HISTORY
 The
 .Fn profil
 function appeared in
-.At v7 .
+.At v6 .
 .Sh BUGS
 This routine should be named
 .Fn profile .
 .Pp
 The
 .Fa samples
 argument should really be a vector of type
 .Fa "unsigned short" .
 .Pp
 The format of the gmon.out file is undocumented.
Index: stable/11/lib/libc/sys/ptrace.2
===================================================================
--- stable/11/lib/libc/sys/ptrace.2	(revision 331184)
+++ stable/11/lib/libc/sys/ptrace.2	(revision 331185)
@@ -1,1108 +1,1108 @@
 .\" $FreeBSD$
 .\"	$NetBSD: ptrace.2,v 1.2 1995/02/27 12:35:37 cgd Exp $
 .\"
 .\" This file is in the public domain.
-.Dd September 14, 2017
+.Dd December 1, 2017
 .Dt PTRACE 2
 .Os
 .Sh NAME
 .Nm ptrace
 .Nd process tracing and debugging
 .Sh LIBRARY
 .Lb libc
 .Sh SYNOPSIS
 .In sys/types.h
 .In sys/ptrace.h
 .Ft int
 .Fn ptrace "int request" "pid_t pid" "caddr_t addr" "int data"
 .Sh DESCRIPTION
 The
 .Fn ptrace
 system call
 provides tracing and debugging facilities.
 It allows one process
 (the
 .Em tracing
 process)
 to control another
 (the
 .Em traced
 process).
 The tracing process must first attach to the traced process, and then
 issue a series of
 .Fn ptrace
 system calls to control the execution of the process, as well as access
 process memory and register state.
 For the duration of the tracing session, the traced process will be
 .Dq re-parented ,
 with its parent process ID (and resulting behavior)
 changed to the tracing process.
 It is permissible for a tracing process to attach to more than one
 other process at a time.
 When the tracing process has completed its work, it must detach the
 traced process; if a tracing process exits without first detaching all
 processes it has attached, those processes will be killed.
 .Pp
 Most of the time, the traced process runs normally, but when it
 receives a signal
 (see
 .Xr sigaction 2 ) ,
 it stops.
 The tracing process is expected to notice this via
 .Xr wait 2
 or the delivery of a
 .Dv SIGCHLD
 signal, examine the state of the stopped process, and cause it to
 terminate or continue as appropriate.
 The signal may be a normal process signal, generated as a result of
 traced process behavior, or use of the
 .Xr kill 2
 system call; alternatively, it may be generated by the tracing facility
 as a result of attaching, stepping by the tracing
 process,
 or an event in the traced process.
 The tracing process may choose to intercept the signal, using it to
 observe process behavior (such as
 .Dv SIGTRAP ) ,
 or forward the signal to the process if appropriate.
 The
 .Fn ptrace
 system call
 is the mechanism by which all this happens.
 .Pp
 A traced process may report additional signal stops corresponding to
 events in the traced process.
 These additional signal stops are reported as
 .Dv SIGTRAP
 or
 .Dv SIGSTOP
 signals.
 The tracing process can use the
 .Dv PT_LWPINFO
 request to determine which events are associated with a
 .Dv SIGTRAP
 or
 .Dv SIGSTOP
 signal.
 Note that multiple events may be associated with a single signal.
 For example, events indicated by the
 .Dv PL_FLAG_BORN ,
 .Dv PL_FLAG_FORKED ,
 and
 .Dv PL_FLAG_EXEC
 flags are also reported as a system call exit event
 .Pq Dv PL_FLAG_SCX .
 The signal stop for a new child process enabled via
 .Dv PTRACE_FORK
 will report a
 .Dv SIGSTOP
 signal.
 All other additional signal stops use
 .Dv SIGTRAP .
 .Pp
 Each traced process has a tracing event mask.
 An event in the traced process only reports a
 signal stop if the corresponding flag is set in the tracing event mask.
 The current set of tracing event flags include:
 .Bl -tag -width "Dv PTRACE_SYSCALL"
 .It Dv PTRACE_EXEC
 Report a stop for a successful invocation of
 .Xr execve 2 .
 This event is indicated by the
 .Dv PL_FLAG_EXEC
 flag in the
 .Va pl_flags
 member of
 .Vt "struct ptrace_lwpinfo" .
 .It Dv PTRACE_SCE
 Report a stop on each system call entry.
 This event is indicated by the
 .Dv PL_FLAG_SCE
 flag in the
 .Va pl_flags
 member of
 .Vt "struct ptrace_lwpinfo" .
 .It Dv PTRACE_SCX
 Report a stop on each system call exit.
 This event is indicated by the
 .Dv PL_FLAG_SCX
 flag in the
 .Va pl_flags
 member of
 .Vt "struct ptrace_lwpinfo" .
 .It Dv PTRACE_SYSCALL
 Report stops for both system call entry and exit.
 .It Dv PTRACE_FORK
 This event flag controls tracing for new child processes of a traced process.
 .Pp
 When this event flag is enabled,
 new child processes will enable tracing and stop before executing their
 first instruction.
 The new child process will include the
 .Dv PL_FLAG_CHILD
 flag in the
 .Va pl_flags
 member of
 .Vt "struct ptrace_lwpinfo" .
 The traced process will report a stop that includes the
 .Dv PL_FLAG_FORKED
 flag.
 The process ID of the new child process will also be present in the
 .Va pl_child_pid
 member of
 .Vt "struct ptrace_lwpinfo" .
 If the new child process was created via
 .Xr vfork 2 ,
 the traced process's stop will also include the
 .Dv PL_FLAG_VFORKED
 flag.
 Note that new child processes will be attached with the default
 tracing event mask;
 they do not inherit the event mask of the traced process.
 .Pp
 When this event flag is not enabled,
 new child processes will execute without tracing enabled.
 .It Dv PTRACE_LWP
 This event flag controls tracing of LWP
 .Pq kernel thread
 creation and destruction.
 When this event is enabled,
 new LWPs will stop and report an event with
 .Dv PL_FLAG_BORN
 set before executing their first instruction,
 and exiting LWPs will stop and report an event with
 .Dv PL_FLAG_EXITED
 set before completing their termination.
 .Pp
 Note that new processes do not report an event for the creation of their
 initial thread,
 and exiting processes do not report an event for the termination of the
 last thread.
 .It Dv PTRACE_VFORK
 Report a stop event when a parent process resumes after a
 .Xr vfork 2 .
 .Pp
 When a thread in the traced process creates a new child process via
 .Xr vfork 2 ,
 the stop that reports
 .Dv PL_FLAG_FORKED
 and
 .Dv PL_FLAG_SCX
 occurs just after the child process is created,
 but before the thread waits for the child process to stop sharing process
 memory.
 If a debugger is not tracing the new child process,
 it must ensure that no breakpoints are enabled in the shared process
 memory before detaching from the new child process.
 This means that no breakpoints are enabled in the parent process either.
 .Pp
 The
 .Dv PTRACE_VFORK
 flag enables a new stop that indicates when the new child process stops
 sharing the process memory of the parent process.
 A debugger can reinsert breakpoints in the parent process and resume it
 in response to this event.
 This event is indicated by setting the
 .Dv PL_FLAG_VFORK_DONE
 flag.
 .El
 .Pp
 The default tracing event mask when attaching to a process via
 .Dv PT_ATTACH ,
 .Dv PT_TRACE_ME ,
 or
 .Dv PTRACE_FORK
 includes only
 .Dv PTRACE_EXEC
 events.
 All other event flags are disabled.
 .Pp
 The
 .Fa request
 argument specifies what operation is being performed; the meaning of
 the rest of the arguments depends on the operation, but except for one
 special case noted below, all
 .Fn ptrace
 calls are made by the tracing process, and the
 .Fa pid
 argument specifies the process ID of the traced process
 or a corresponding thread ID.
 The
 .Fa request
 argument
 can be:
 .Bl -tag -width "Dv PT_GET_EVENT_MASK"
 .It Dv PT_TRACE_ME
 This request is the only one used by the traced process; it declares
 that the process expects to be traced by its parent.
 All the other arguments are ignored.
 (If the parent process does not expect to trace the child, it will
 probably be rather confused by the results; once the traced process
 stops, it cannot be made to continue except via
 .Fn ptrace . )
 When a process has used this request and calls
 .Xr execve 2
 or any of the routines built on it
 (such as
 .Xr execv 3 ) ,
 it will stop before executing the first instruction of the new image.
 Also, any setuid or setgid bits on the executable being executed will
 be ignored.
 If the child was created by
 .Xr vfork 2
 system call or
 .Xr rfork 2
 call with the
 .Dv RFMEM
 flag specified, the debugging events are reported to the parent
 only after the
 .Xr execve 2
 is executed.
 .It Dv PT_READ_I , Dv PT_READ_D
 These requests read a single
 .Vt int
 of data from the traced process's address space.
 Traditionally,
 .Fn ptrace
 has allowed for machines with distinct address spaces for instruction
 and data, which is why there are two requests: conceptually,
 .Dv PT_READ_I
 reads from the instruction space and
 .Dv PT_READ_D
 reads from the data space.
 In the current
 .Fx
 implementation, these two requests are completely identical.
 The
 .Fa addr
 argument specifies the address
 (in the traced process's virtual address space)
 at which the read is to be done.
 This address does not have to meet any alignment constraints.
 The value read is returned as the return value from
 .Fn ptrace .
 .It Dv PT_WRITE_I , Dv PT_WRITE_D
 These requests parallel
 .Dv PT_READ_I
 and
 .Dv PT_READ_D ,
 except that they write rather than read.
 The
 .Fa data
 argument supplies the value to be written.
 .It Dv PT_IO
 This request allows reading and writing arbitrary amounts of data in
 the traced process's address space.
 The
 .Fa addr
 argument specifies a pointer to a
 .Vt "struct ptrace_io_desc" ,
 which is defined as follows:
 .Bd -literal
 struct ptrace_io_desc {
 	int	piod_op;	/* I/O operation */
 	void	*piod_offs;	/* child offset */
 	void	*piod_addr;	/* parent offset */
 	size_t	piod_len;	/* request length */
 };
 
 /*
  * Operations in piod_op.
  */
 #define PIOD_READ_D	1	/* Read from D space */
 #define PIOD_WRITE_D	2	/* Write to D space */
 #define PIOD_READ_I	3	/* Read from I space */
 #define PIOD_WRITE_I	4	/* Write to I space */
 .Ed
 .Pp
 The
 .Fa data
 argument is ignored.
 The actual number of bytes read or written is stored in
 .Va piod_len
 upon return.
 .It Dv PT_CONTINUE
 The traced process continues execution.
 The
 .Fa addr
 argument
 is an address specifying the place where execution is to be resumed
 (a new value for the program counter),
 or
 .Po Vt caddr_t Pc Ns 1
 to indicate that execution is to pick up where it left off.
 The
 .Fa data
 argument
 provides a signal number to be delivered to the traced process as it
 resumes execution, or 0 if no signal is to be sent.
 .It Dv PT_STEP
 The traced process is single stepped one instruction.
 The
 .Fa addr
 argument
 should be passed
 .Po Vt caddr_t Pc Ns 1 .
 The
 .Fa data
 argument
 provides a signal number to be delivered to the traced process as it
 resumes execution, or 0 if no signal is to be sent.
 .It Dv PT_KILL
 The traced process terminates, as if
 .Dv PT_CONTINUE
 had been used with
 .Dv SIGKILL
 given as the signal to be delivered.
 .It Dv PT_ATTACH
 This request allows a process to gain control of an otherwise
 unrelated process and begin tracing it.
 It does not need any cooperation from the to-be-traced process.
 In
 this case,
 .Fa pid
 specifies the process ID of the to-be-traced process, and the other
 two arguments are ignored.
 This request requires that the target process must have the same real
 UID as the tracing process, and that it must not be executing a setuid
 or setgid executable.
 (If the tracing process is running as root, these restrictions do not
 apply.)
 The tracing process will see the newly-traced process stop and may
 then control it as if it had been traced all along.
 .It Dv PT_DETACH
 This request is like PT_CONTINUE, except that it does not allow
 specifying an alternate place to continue execution, and after it
 succeeds, the traced process is no longer traced and continues
 execution normally.
 .It Dv PT_GETREGS
 This request reads the traced process's machine registers into the
 .Do
 .Vt "struct reg"
 .Dc
 (defined in
 .In machine/reg.h )
 pointed to by
 .Fa addr .
 .It Dv PT_SETREGS
 This request is the converse of
 .Dv PT_GETREGS ;
 it loads the traced process's machine registers from the
 .Do
 .Vt "struct reg"
 .Dc
 (defined in
 .In machine/reg.h )
 pointed to by
 .Fa addr .
 .It Dv PT_GETFPREGS
 This request reads the traced process's floating-point registers into
 the
 .Do
 .Vt "struct fpreg"
 .Dc
 (defined in
 .In machine/reg.h )
 pointed to by
 .Fa addr .
 .It Dv PT_SETFPREGS
 This request is the converse of
 .Dv PT_GETFPREGS ;
 it loads the traced process's floating-point registers from the
 .Do
 .Vt "struct fpreg"
 .Dc
 (defined in
 .In machine/reg.h )
 pointed to by
 .Fa addr .
 .It Dv PT_GETDBREGS
 This request reads the traced process's debug registers into
 the
 .Do
 .Vt "struct dbreg"
 .Dc
 (defined in
 .In machine/reg.h )
 pointed to by
 .Fa addr .
 .It Dv PT_SETDBREGS
 This request is the converse of
 .Dv PT_GETDBREGS ;
 it loads the traced process's debug registers from the
 .Do
 .Vt "struct dbreg"
 .Dc
 (defined in
 .In machine/reg.h )
 pointed to by
 .Fa addr .
 .It Dv PT_LWPINFO
 This request can be used to obtain information about the kernel thread,
 also known as light-weight process, that caused the traced process to stop.
 The
 .Fa addr
 argument specifies a pointer to a
 .Vt "struct ptrace_lwpinfo" ,
 which is defined as follows:
 .Bd -literal
 struct ptrace_lwpinfo {
 	lwpid_t pl_lwpid;
 	int	pl_event;
 	int	pl_flags;
 	sigset_t pl_sigmask;
 	sigset_t pl_siglist;
 	siginfo_t pl_siginfo;
 	char	pl_tdname[MAXCOMLEN + 1];
 	pid_t	pl_child_pid;
 	u_int	pl_syscall_code;
 	u_int	pl_syscall_narg;
 };
 .Ed
 .Pp
 The
 .Fa data
 argument is to be set to the size of the structure known to the caller.
 This allows the structure to grow without affecting older programs.
 .Pp
 The fields in the
 .Vt "struct ptrace_lwpinfo"
 have the following meaning:
 .Bl -tag -width indent -compact
 .It Va pl_lwpid
 LWP id of the thread
 .It Va pl_event
 Event that caused the stop.
 Currently defined events are:
 .Bl -tag -width "Dv PL_EVENT_SIGNAL" -compact
 .It Dv PL_EVENT_NONE
 No reason given
 .It Dv PL_EVENT_SIGNAL
 Thread stopped due to the pending signal
 .El
 .It Va pl_flags
 Flags that specify additional details about observed stop.
 Currently defined flags are:
 .Bl -tag -width indent -compact
 .It Dv PL_FLAG_SCE
 The thread stopped due to system call entry, right after the kernel is entered.
 The debugger may examine syscall arguments that are stored in memory and
 registers according to the ABI of the current process, and modify them,
 if needed.
 .It Dv PL_FLAG_SCX
 The thread is stopped immediately before syscall is returning to the usermode.
 The debugger may examine system call return values in the ABI-defined registers
 and/or memory.
 .It Dv PL_FLAG_EXEC
 When
 .Dv PL_FLAG_SCX
 is set, this flag may be additionally specified to inform that the
 program being executed by debuggee process has been changed by successful
 execution of a system call from the
 .Fn execve 2
 family.
 .It Dv PL_FLAG_SI
 Indicates that
 .Va pl_siginfo
 member of
 .Vt "struct ptrace_lwpinfo"
 contains valid information.
 .It Dv PL_FLAG_FORKED
 Indicates that the process is returning from a call to
 .Fn fork 2
 that created a new child process.
 The process identifier of the new process is available in the
 .Va pl_child_pid
 member of
 .Vt "struct ptrace_lwpinfo" .
 .It Dv PL_FLAG_CHILD
 The flag is set for first event reported from a new child which is
 automatically attached when
 .Dv PTRACE_FORK
 is enabled.
 .It Dv PL_FLAG_BORN
 This flag is set for the first event reported from a new LWP when
 .Dv PTRACE_LWP
 is enabled.
 It is reported along with
 .Dv PL_FLAG_SCX .
 .It Dv PL_FLAG_EXITED
 This flag is set for the last event reported by an exiting LWP when
 .Dv PTRACE_LWP
 is enabled.
 Note that this event is not reported when the last LWP in a process exits.
 The termination of the last thread is reported via a normal process exit
 event.
 .It Dv PL_FLAG_VFORKED
 Indicates that the thread is returning from a call to
 .Xr vfork 2
 that created a new child process.
 This flag is set in addition to
 .Dv PL_FLAG_FORKED .
 .It Dv PL_FLAG_VFORK_DONE
 Indicates that the thread has resumed after a child process created via
 .Xr vfork 2
 has stopped sharing its address space with the traced process.
 .El
 .It Va pl_sigmask
 The current signal mask of the LWP
 .It Va pl_siglist
 The current pending set of signals for the LWP.
 Note that signals that are delivered to the process would not appear
 on an LWP siglist until the thread is selected for delivery.
 .It Va pl_siginfo
 The siginfo that accompanies the signal pending.
 Only valid for
 .Dv PL_EVENT_SIGNAL
 stop when
 .Dv PL_FLAG_SI
 is set in
 .Va pl_flags .
 .It Va pl_tdname
 The name of the thread.
 .It Va pl_child_pid
 The process identifier of the new child process.
 Only valid for a
 .Dv PL_EVENT_SIGNAL
 stop when
 .Dv PL_FLAG_FORKED
 is set in
 .Va pl_flags .
 .It Va pl_syscall_code
 The ABI-specific identifier of the current system call.
 Note that for indirect system calls this field reports the indirected
 system call.
 Only valid when
 .Dv PL_FLAG_SCE
 or
 .Dv PL_FLAG_SCX
 is set in
 .Va pl_flags.
 .It Va pl_syscall_narg
 The number of arguments passed to the current system call not counting
 the system call identifier.
 Note that for indirect system calls this field reports the arguments
 passed to the indirected system call.
 Only valid when
 .Dv PL_FLAG_SCE
 or
 .Dv PL_FLAG_SCX
 is set in
 .Va pl_flags.
 .El
 .It Dv PT_GETNUMLWPS
 This request returns the number of kernel threads associated with the
 traced process.
 .It Dv PT_GETLWPLIST
 This request can be used to get the current thread list.
 A pointer to an array of type
 .Vt lwpid_t
 should be passed in
 .Fa addr ,
 with the array size specified by
 .Fa data .
 The return value from
 .Fn ptrace
 is the count of array entries filled in.
 .It Dv PT_SETSTEP
 This request will turn on single stepping of the specified process.
 .It Dv PT_CLEARSTEP
 This request will turn off single stepping of the specified process.
 .It Dv PT_SUSPEND
 This request will suspend the specified thread.
 .It Dv PT_RESUME
 This request will resume the specified thread.
 .It Dv PT_TO_SCE
 This request will set the
 .Dv PTRACE_SCE
 event flag to trace all future system call entries and continue the process.
 The
 .Fa addr
 and
 .Fa data
 arguments are used the same as for
 .Dv PT_CONTINUE.
 .It Dv PT_TO_SCX
 This request will set the
 .Dv PTRACE_SCX
 event flag to trace all future system call exits and continue the process.
 The
 .Fa addr
 and
 .Fa data
 arguments are used the same as for
 .Dv PT_CONTINUE.
 .It Dv PT_SYSCALL
 This request will set the
 .Dv PTRACE_SYSCALL
 event flag to trace all future system call entries and exits and continue
 the process.
 The
 .Fa addr
 and
 .Fa data
 arguments are used the same as for
 .Dv PT_CONTINUE.
 .It Dv PT_GET_SC_ARGS
 For the thread which is stopped in either
 .Dv PL_FLAG_SCE
 or
 .Dv PL_FLAG_SCX
 state, that is, on entry or exit to a syscall,
 this request fetches the syscall arguments.
 .Pp
 The arguments are copied out into the buffer pointed to by the
 .Fa addr
 pointer, sequentially.
 Each syscall argument is stored as the machine word.
 Kernel copies out as many arguments as the syscall accepts,
 see the
 .Va pl_syscall_narg
 member of the
 .Vt struct ptrace_lwpinfo ,
 but not more than the
 .Fa data
 bytes in total are copied.
 .It Dv PT_FOLLOW_FORK
 This request controls tracing for new child processes of a traced process.
 If
 .Fa data
 is non-zero,
 .Dv PTRACE_FORK
 is set in the traced process's event tracing mask.
 If
 .Fa data
 is zero,
 .Dv PTRACE_FORK
 is cleared from the traced process's event tracing mask.
 .It Dv PT_LWP_EVENTS
 This request controls tracing of LWP creation and destruction.
 If
 .Fa data
 is non-zero,
 .Dv PTRACE_LWP
 is set in the traced process's event tracing mask.
 If
 .Fa data
 is zero,
 .Dv PTRACE_LWP
 is cleared from the traced process's event tracing mask.
 .It Dv PT_GET_EVENT_MASK
 This request reads the traced process's event tracing mask into the
 integer pointed to by
 .Fa addr .
 The size of the integer must be passed in
 .Fa data .
 .It Dv PT_SET_EVENT_MASK
 This request sets the traced process's event tracing mask from the
 integer pointed to by
 .Fa addr .
 The size of the integer must be passed in
 .Fa data .
 .It Dv PT_VM_TIMESTAMP
 This request returns the generation number or timestamp of the memory map of
 the traced process as the return value from
 .Fn ptrace .
 This provides a low-cost way for the tracing process to determine if the
 VM map changed since the last time this request was made.
 .It Dv PT_VM_ENTRY
 This request is used to iterate over the entries of the VM map of the traced
 process.
 The
 .Fa addr
 argument specifies a pointer to a
 .Vt "struct ptrace_vm_entry" ,
 which is defined as follows:
 .Bd -literal
 struct ptrace_vm_entry {
 	int		pve_entry;
 	int		pve_timestamp;
 	u_long		pve_start;
 	u_long		pve_end;
 	u_long		pve_offset;
 	u_int		pve_prot;
 	u_int		pve_pathlen;
 	long		pve_fileid;
 	uint32_t	pve_fsid;
 	char		*pve_path;
 };
 .Ed
 .Pp
 The first entry is returned by setting
 .Va pve_entry
 to zero.
 Subsequent entries are returned by leaving
 .Va pve_entry
 unmodified from the value returned by previous requests.
 The
 .Va pve_timestamp
 field can be used to detect changes to the VM map while iterating over the
 entries.
 The tracing process can then take appropriate action, such as restarting.
 By setting
 .Va pve_pathlen
 to a non-zero value on entry, the pathname of the backing object is returned
 in the buffer pointed to by
 .Va pve_path ,
 provided the entry is backed by a vnode.
 The
 .Va pve_pathlen
 field is updated with the actual length of the pathname (including the
 terminating null character).
 The
 .Va pve_offset
 field is the offset within the backing object at which the range starts.
 The range is located in the VM space at
 .Va pve_start
 and extends up to
 .Va pve_end
 (inclusive).
 .Pp
 The
 .Fa data
 argument is ignored.
 .El
 .Sh ARM MACHINE-SPECIFIC REQUESTS
 .Bl -tag -width "Dv PT_SETVFPREGS"
 .It Dv PT_GETVFPREGS
 Return the thread's
 .Dv VFP
 machine state in the buffer pointed to by
 .Fa addr .
 .Pp
 The
 .Fa data
 argument is ignored.
 .It Dv PT_SETVFPREGS
 Set the thread's
 .Dv VFP
 machine state from the buffer pointed to by
 .Fa addr .
 .Pp
 The
 .Fa data
 argument is ignored.
 .El
 .Pp
 .Sh x86 MACHINE-SPECIFIC REQUESTS
 .Bl -tag -width "Dv PT_GETXSTATE_INFO"
 .It Dv PT_GETXMMREGS
 Copy the XMM FPU state into the buffer pointed to by the
 argument
 .Fa addr .
 The buffer has the same layout as the 32-bit save buffer for the
 machine instruction
 .Dv FXSAVE .
 .Pp
 This request is only valid for i386 programs, both on native 32-bit
 systems and on amd64 kernels.
 For 64-bit amd64 programs, the XMM state is reported as part of
 the FPU state returned by the
 .Dv PT_GETFPREGS
 request.
 .Pp
 The
 .Fa data
 argument is ignored.
 .It Dv PT_SETXMMREGS
 Load the XMM FPU state for the thread from the buffer pointed to
 by the argument
 .Fa addr .
 The buffer has the same layout as the 32-bit load buffer for the
 machine instruction
 .Dv FXRSTOR .
 .Pp
 As with
 .Dv PT_GETXMMREGS,
 this request is only valid for i386 programs.
 .Pp
 The
 .Fa data
 argument is ignored.
 .It Dv PT_GETXSTATE_INFO
 Report which XSAVE FPU extensions are supported by the CPU
 and allowed in userspace programs.
 The
 .Fa addr
 argument must point to a variable of type
 .Vt struct ptrace_xstate_info ,
 which contains the information on the request return.
 .Vt struct ptrace_xstate_info
 is defined as follows:
 .Bd -literal
 struct ptrace_xstate_info {
 	uint64_t	xsave_mask;
 	uint32_t	xsave_len;
 };
 .Ed
 The
 .Dv xsave_mask
 field is a bitmask of the currently enabled extensions.
 The meaning of the bits is defined in the Intel and AMD
 processor documentation.
 The
 .Dv xsave_len
 field reports the length of the XSAVE area for storing the hardware
 state for currently enabled extensions in the format defined by the x86
 .Dv XSAVE
 machine instruction.
 .Pp
 The
 .Fa data
 argument value must be equal to the size of the
 .Vt struct ptrace_xstate_info .
 .It Dv PT_GETXSTATE
 Return the content of the XSAVE area for the thread.
 The
 .Fa addr
 argument points to the buffer where the content is copied, and the
 .Fa data
 argument specifies the size of the buffer.
 The kernel copies out as much content as allowed by the buffer size.
 The buffer layout is specified by the layout of the save area for the
 .Dv XSAVE
 machine instruction.
 .It Dv PT_SETXSTATE
 Load the XSAVE state for the thread from the buffer specified by the
 .Fa addr
 pointer.
 The buffer size is passed in the
 .Fa data
 argument.
 The buffer must be at least as large as the
 .Vt struct savefpu
 (defined in
 .Pa x86/fpu.h )
 to allow the complete x87 FPU and XMM state load.
 It must not be larger than the XSAVE state length, as reported by the
 .Dv xsave_len
 field from the
 .Vt struct ptrace_xstate_info
 of the
 .Dv PT_GETXSTATE_INFO
 request.
 Layout of the buffer is identical to the layout of the load area for the
 .Dv XRSTOR
 machine instruction.
 .It Dv PT_GETFSBASE
 Return the value of the base used when doing segmented
 memory addressing using the %fs segment register.
 The
 .Fa addr
 argument points to an
 .Vt unsigned long
 variable where the base value is stored.
 .Pp
 The
 .Fa data
 argument is ignored.
 .It Dv PT_GETGSBASE
 Like the
 .Dv PT_GETFSBASE
 request, but returns the base for the %gs segment register.
 .It Dv PT_SETFSBASE
 Set the base for the %fs segment register to the value pointed to
 by the
 .Fa addr
 argument.
 .Fa addr
 must point to the
 .Vt unsigned long
 variable containing the new base.
 .Pp
 The
 .Fa data
 argument is ignored.
 .It Dv PT_SETGSBASE
 Like the
 .Dv PT_SETFSBASE
 request, but sets the base for the %gs segment register.
 .El
 .Sh PowerPC MACHINE-SPECIFIC REQUESTS
 .Bl -tag -width "Dv PT_SETVRREGS"
 .It Dv PT_GETVRREGS
 Return the thread's
 .Dv ALTIVEC
 machine state in the buffer pointed to by
 .Fa addr .
 .Pp
 The
 .Fa data
 argument is ignored.
 .It Dv PT_SETVRREGS
 Set the thread's
 .Dv ALTIVEC
 machine state from the buffer pointed to by
 .Fa addr .
 .Pp
 The
 .Fa data
 argument is ignored.
 .El
 .Pp
 Additionally, other machine-specific requests can exist.
 .Sh RETURN VALUES
 Most requests return 0 on success and \-1 on error.
 Some requests can cause
 .Fn ptrace
 to return
 \-1
 as a non-error value, among them are
 .Dv PT_READ_I
 and
 .Dv PT_READ_D ,
 which return the value read from the process memory on success.
 To disambiguate,
 .Va errno
 can be set to 0 before the call and checked afterwards.
 .Pp
 The current
 .Fn ptrace
 implementation always sets
 .Va errno
 to 0 before calling into the kernel, both for historic reasons and for
 consistency with other operating systems.
 It is recommended to assign zero to
 .Va errno
 explicitly for forward compatibility.
 .Sh ERRORS
 The
 .Fn ptrace
 system call may fail if:
 .Bl -tag -width Er
 .It Bq Er ESRCH
 .Bl -bullet -compact
 .It
 No process having the specified process ID exists.
 .El
 .It Bq Er EINVAL
 .Bl -bullet -compact
 .It
 A process attempted to use
 .Dv PT_ATTACH
 on itself.
 .It
 The
 .Fa request
 argument
 was not one of the legal requests.
 .It
 The signal number
 (in
 .Fa data )
 to
 .Dv PT_CONTINUE
 was neither 0 nor a legal signal number.
 .It
 .Dv PT_GETREGS ,
 .Dv PT_SETREGS ,
 .Dv PT_GETFPREGS ,
 .Dv PT_SETFPREGS ,
 .Dv PT_GETDBREGS ,
 or
 .Dv PT_SETDBREGS
 was attempted on a process with no valid register set.
 (This is normally true only of system processes.)
 .It
 .Dv PT_VM_ENTRY
 was given an invalid value for
 .Fa pve_entry .
 This can also be caused by changes to the VM map of the process.
 .It
 The size (in
 .Fa data )
 provided to
 .Dv PT_LWPINFO
 was less than or equal to zero, or larger than the
 .Vt ptrace_lwpinfo
 structure known to the kernel.
 .It
 The size (in
 .Fa data )
 provided to the x86-specific
 .Dv PT_GETXSTATE_INFO
 request was not equal to the size of the
 .Vt struct ptrace_xstate_info .
 .It
 The size (in
 .Fa data )
 provided to the x86-specific
 .Dv PT_SETXSTATE
 request was less than the size of the x87 plus the XMM save area.
 .It
 The size (in
 .Fa data )
 provided to the x86-specific
 .Dv PT_SETXSTATE
 request was larger than returned in the
 .Dv xsave_len
 member of the
 .Vt struct ptrace_xstate_info
 from the
 .Dv PT_GETXSTATE_INFO
 request.
 .It
 The base value, provided to the amd64-specific requests
 .Dv PT_SETFSBASE
 or
 .Dv PT_SETGSBASE ,
 pointed outside of the valid user address space.
 This error will not occur in 32-bit programs.
 .El
 .It Bq Er EBUSY
 .Bl -bullet -compact
 .It
 .Dv PT_ATTACH
 was attempted on a process that was already being traced.
 .It
 A request attempted to manipulate a process that was being traced by
 some process other than the one making the request.
 .It
 A request
 (other than
 .Dv PT_ATTACH )
 specified a process that was not stopped.
 .El
 .It Bq Er EPERM
 .Bl -bullet -compact
 .It
 A request
 (other than
 .Dv PT_ATTACH )
 attempted to manipulate a process that was not being traced at all.
 .It
 An attempt was made to use
 .Dv PT_ATTACH
 on a process in violation of the requirements listed under
 .Dv PT_ATTACH
 above.
 .El
 .It Bq Er ENOENT
 .Bl -bullet -compact
 .It
 .Dv PT_VM_ENTRY
 previously returned the last entry of the memory map.
 No more entries exist.
 .El
 .It Bq Er ENAMETOOLONG
 .Bl -bullet -compact
 .It
 .Dv PT_VM_ENTRY
 cannot return the pathname of the backing object because the buffer is not big
 enough.
 .Fa pve_pathlen
 holds the minimum buffer size required on return.
 .El
 .El
 .Sh SEE ALSO
 .Xr execve 2 ,
 .Xr sigaction 2 ,
 .Xr wait 2 ,
 .Xr execv 3 ,
 .Xr i386_clr_watch 3 ,
 .Xr i386_set_watch 3
 .Sh HISTORY
 The
 .Fn ptrace
 function appeared in
-.At v7 .
+.At v6 .
Index: stable/11/lib/libc/sys/setuid.2
===================================================================
--- stable/11/lib/libc/sys/setuid.2	(revision 331184)
+++ stable/11/lib/libc/sys/setuid.2	(revision 331185)
@@ -1,187 +1,187 @@
 .\" Copyright (c) 1983, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\" 4. Neither the name of the University nor the names of its contributors
 .\"    may be used to endorse or promote products derived from this software
 .\"    without specific prior written permission.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, 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.
 .\"
 .\"     @(#)setuid.2	8.1 (Berkeley) 6/4/93
 .\" $FreeBSD$
 .\"
 .Dd December 15, 2015
 .Dt SETUID 2
 .Os
 .Sh NAME
 .Nm setuid ,
 .Nm seteuid ,
 .Nm setgid ,
 .Nm setegid
 .Nd set user and group ID
 .Sh LIBRARY
 .Lb libc
 .Sh SYNOPSIS
 .In unistd.h
 .Ft int
 .Fn setuid "uid_t uid"
 .Ft int
 .Fn seteuid "uid_t euid"
 .Ft int
 .Fn setgid "gid_t gid"
 .Ft int
 .Fn setegid "gid_t egid"
 .Sh DESCRIPTION
 The
 .Fn setuid
 system call
 sets the real and effective
 user IDs and the saved set-user-ID of the current process
 to the specified value.
 .\" Comment out next block for !_POSIX_SAVED_IDS
 .\" The real user ID and the saved set-user-ID are changed only if the
 .\" effective user ID is that of the super user.
 .\" I.e.
 .\" .Fn setuid
 .\" system call is equal to
 .\" .Fn seteuid
 .\" system call if the effective user ID is not that of the super user.
 .\" End of block
 The
 .Fn setuid
 system call is permitted if the specified ID is equal to the real user ID
 .\" Comment out next line for !_POSIX_SAVED_IDS
 .\" or the saved set-user-ID
 .\" Next line is for Appendix B.4.2.2 case.
 or the effective user ID
 of the process, or if the effective user ID is that of the super user.
 .Pp
 The
 .Fn setgid
 system call
 sets the real and effective
 group IDs and the saved set-group-ID of the current process
 to the specified value.
 .\" Comment out next block for !_POSIX_SAVED_IDS
 .\" The real group ID and the saved set-group-ID are changed only if the
 .\" effective user ID is that of the super user.
 .\" I.e.
 .\" .Fn setgid
 .\" system call is equal to
 .\" .Fn setegid
 .\" system call if the effective user ID is not that of the super user.
 .\" End of block
 The
 .Fn setgid
 system call is permitted if the specified ID is equal to the real group ID
 .\" Comment out next line for !_POSIX_SAVED_IDS
 .\" or the saved set-group-ID
 .\" Next line is for Appendix B.4.2.2 case.
 or the effective group ID
 of the process, or if the effective user ID is that of the super user.
 .Pp
 The
 .Fn seteuid
 system call
 .Pq Fn setegid
 sets the effective user ID (group ID) of the
 current process.
 The effective user ID may be set to the value
 of the real user ID or the saved set-user-ID (see
 .Xr intro 2
 and
 .Xr execve 2 ) ;
 in this way, the effective user ID of a set-user-ID executable
 may be toggled by switching to the real user ID, then re-enabled
 by reverting to the set-user-ID value.
 Similarly, the effective group ID may be set to the value
 of the real group ID or the saved set-group-ID.
 .Sh RETURN VALUES
 .Rv -std
 .Sh ERRORS
 The system calls will fail if:
 .Bl -tag -width Er
 .It Bq Er EPERM
 The user is not the super user and the ID
 specified is not the real, effective ID, or saved ID.
 .El
 .Sh SEE ALSO
 .Xr getgid 2 ,
 .Xr getuid 2 ,
 .Xr issetugid 2 ,
 .Xr setregid 2 ,
 .Xr setreuid 2
 .Sh STANDARDS
 The
 .Fn setuid
 and
 .Fn setgid
 system calls are compliant with the
 .St -p1003.1-90
 specification with
 .Li _POSIX_SAVED_IDS
 .\" Uncomment next line for !_POSIX_SAVED_IDS
 not
 defined with the permitted extensions from Appendix B.4.2.2.
 The
 .Fn seteuid
 and
 .Fn setegid
 system calls are extensions based on the
 .Tn POSIX
 concept of
 .Li _POSIX_SAVED_IDS ,
 and have been proposed for a future revision of the standard.
 .Sh HISTORY
 The
 .Fn setuid
 and
 .Fn setgid
 functions appeared in
-.At v7 .
+.At v4 .
 .Sh SECURITY CONSIDERATIONS
 Read and write permissions to files are determined upon a call to
 .Xr open 2 .
 Once a file descriptor is open, dropping privilege does not affect
 the process's read/write permissions, even if the user ID specified
 has no read or write permissions to the file.
 These files normally remain open in any new process executed,
 resulting in a user being able to read or modify
 potentially sensitive data.
 .Pp
 To prevent these files from remaining open after an
 .Xr exec 3
 call, be sure to set the close-on-exec flag:
 .Bd -literal
 void
 pseudocode(void)
 {
 	int fd;
 	/* ... */
 
 	fd = open("/path/to/sensitive/data", O_RDWR | O_CLOEXEC);
 	if (fd == -1)
 		err(1, "open");
 
 	/* ... */
 	execve(path, argv, environ);
 }
 .Ed
Index: stable/11/lib/libc/sys/sync.2
===================================================================
--- stable/11/lib/libc/sys/sync.2	(revision 331184)
+++ stable/11/lib/libc/sys/sync.2	(revision 331185)
@@ -1,77 +1,77 @@
 .\" Copyright (c) 1980, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\" 4. Neither the name of the University nor the names of its contributors
 .\"    may be used to endorse or promote products derived from this software
 .\"    without specific prior written permission.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, 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.
 .\"
 .\"     @(#)sync.2	8.1 (Berkeley) 6/4/93
 .\" $FreeBSD$
 .\"
-.Dd June 4, 1993
+.Dd December 1, 2017
 .Dt SYNC 2
 .Os
 .Sh NAME
 .Nm sync
 .Nd "schedule file system updates"
 .Sh LIBRARY
 .Lb libc
 .Sh SYNOPSIS
 .In unistd.h
 .Ft void
 .Fn sync void
 .Sh DESCRIPTION
 The
 .Fn sync
 system call forces a write of dirty (modified) buffers
 in the block buffer cache out
 to disk.
 The kernel keeps this information in core to reduce
 the number of disk I/O transfers required by the system.
 As information in the cache is lost after a system crash, a
 .Fn sync
 system call is issued
 frequently
 by the kernel process
 .Xr syncer 4
 (about every 30 seconds).
 .Pp
 The
 .Xr fsync 2
 system call
 may be used to synchronize individual file descriptor
 attributes.
 .Sh SEE ALSO
 .Xr fsync 2 ,
 .Xr syncer 4 ,
 .Xr sync 8
 .Sh HISTORY
 The
 .Fn sync
 function appeared in
-.At v6 .
+.At v3 .
 .Sh BUGS
 The
 .Fn sync
 system call
 may return before the buffers are completely flushed.
Index: stable/11
===================================================================
--- stable/11	(revision 331184)
+++ stable/11	(revision 331185)

Property changes on: stable/11
___________________________________________________________________
Modified: svn:mergeinfo
## -0,0 +0,1 ##
   Merged /head:r326437