Linux-kernel mailing list archive 1999-36,: clone() and CLONE_PID

# clone() and CLONE_PID

Lorenzo Allegrucci (parsek@tin.it)
Tue, 7 Sep 1999 18:15:29 +0200

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Marek Zelem: "[PATCH] 2.2.x bugfix (signal handling)"
- Previous message: Chuck Mead: "Re: Adaptec 2920A & fdomain.o (again) (Bugzilla #4670)"
- Next in thread: David Wragg: "Re: clone() and CLONE_PID"
- Reply: David Wragg: "Re: clone() and CLONE_PID"
- Reply: David Wragg: "Re: clone() and CLONE_PID"

This is from the LinuxThreads README file:

KNOWN BUGS AND LIMITATIONS:

- Threads share pretty much everything they should share according
to the standard: memory space, file descriptors, signal handlers,
current working directory, etc. One thing that they do not share
is their pid's and parent pid's. According to the standard, they
should have the same, but that's one thing we cannot achieve
in this implementation (until the CLONE_PID flag to clone() becomes
usable).

When does the CLONE_PID flag to clone() becomes usable? 2.4.x? 2.5.x?

    --
    Lorenzo

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

- Next message: Marek Zelem: "[PATCH] 2.2.x bugfix (signal handling)"
- Previous message: Chuck Mead: "Re: Adaptec 2920A & fdomain.o (again) (Bugzilla #4670)"
- Next in thread: David Wragg: "Re: clone() and CLONE_PID"
- Reply: David Wragg: "Re: clone() and CLONE_PID"
- Reply: David Wragg: "Re: clone() and CLONE_PID"