On 11/08/2013 10:41 AM, Peng Haitao wrote: > CLONE_PARENT_SETTID only stores child thread ID in parent memory. Applied. Thanks, Haitao. Cheers, Michael > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> > --- > man2/clone.2 | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/man2/clone.2 b/man2/clone.2 > index 4815fb1..6325397 100644 > --- a/man2/clone.2 > +++ b/man2/clone.2 > @@ -532,7 +532,7 @@ calling process itself, will be signaled. > .BR CLONE_PARENT_SETTID " (since Linux 2.5.49)" > Store child thread ID at location > .I ptid > -in parent and child memory. > +in parent memory. > (In Linux 2.5.32-2.5.48 there was a flag > .B CLONE_SETTID > that did this.) > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
