clone.2: Fix errors in argument names in text (ptid, ctd)

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2009-06-21 15:02:21 +02:00
parent bd16963cbe
commit d3dbc9b11a
1 changed files with 8 additions and 8 deletions

View File

@ -42,7 +42,7 @@
.\" FIXME . 2.6.25 marks the unused CLONE_STOPPED as obsolete, and it will
.\" probably be removed in the future.
.\"
.TH CLONE 2 2008-11-25 "Linux" "Linux Programmer's Manual"
.TH CLONE 2 2009-06-21 "Linux" "Linux Programmer's Manual"
.SH NAME
clone, __clone2 \- create a child process
.SH SYNOPSIS
@ -54,7 +54,7 @@ clone, __clone2 \- create a child process
.BI "int clone(int (*" "fn" ")(void *), void *" child_stack ,
.BI " int " flags ", void *" "arg" ", ... "
.BI " /* pid_t *" pid ", struct user_desc *" tls \
.BI " /* pid_t *" ptid ", struct user_desc *" tls \
", pid_t *" ctid " */ );"
.fi
.SH DESCRIPTION
@ -156,7 +156,7 @@ and the child process:
.TP
.BR CLONE_CHILD_CLEARTID " (since Linux 2.5.49)"
Erase child thread ID at location
.I child_tidptr
.I ctid
in child memory when the child exits, and do a wakeup on the futex
at that address.
The address involved may be changed by the
@ -166,7 +166,7 @@ This is used by threading libraries.
.TP
.BR CLONE_CHILD_SETTID " (since Linux 2.5.49)"
Store child thread ID at location
.I child_tidptr
.I ctid
in child memory.
.TP
.B CLONE_FILES
@ -499,7 +499,7 @@ calling process itself, will be signaled.
.TP
.BR CLONE_PARENT_SETTID " (since Linux 2.5.49)"
Store child thread ID at location
.I parent_tidptr
.I ptid
in parent and child memory.
(In Linux 2.5.32-2.5.48 there was a flag
.B CLONE_SETTID
@ -782,12 +782,12 @@ option should not be specified.
Since Linux 2.5.49 the system call has five arguments.
The two new arguments are
.I parent_tidptr
.I ptid
which points to the location (in parent and child memory) where
the child thread ID will be written in case
.B CLONE_PARENT_SETTID
was specified, and
.I child_tidptr
.I ctid
which points to the location (in child memory) where the child thread ID
will be written in case
.B CLONE_CHILD_SETTID
@ -955,7 +955,7 @@ On ia64, a different system call is used:
.BI "int __clone2(int (*" "fn" ")(void *), "
.BI " void *" child_stack_base ", size_t " stack_size ,
.BI " int " flags ", void *" "arg" ", ... "
.BI " /* pid_t *" pid ", struct user_desc *" tls \
.BI " /* pid_t *" ptid ", struct user_desc *" tls \
", pid_t *" ctid " */ );"
.fi
.PP