Messages in this thread | | | Date | Sun, 27 Aug 2000 06:05:19 -0700 | From | Mitchell Blank Jr <> | Subject | Re: SCO: "thread creation is about a thousand times faster than on |
| |
Mark Kettenis wrote: > The current draft for IEEE Std. 1003.1-200x says: > > "A call to any exec function from a process with more than one thread > results in all threads being terminated and the new executable image > being loaded and executed. No destructor functions shall be called."
Grumble... and I suppose a failed execve() needs to return an error to that one thread, but a succesful one needs to atomically destroy all the other threads... And HOW is this supposed to be implemented?
The previous version of the standard had this right - just leave it undefined and let the OS try to do something sane. Hopefully this part will get nixed before the final revision.
-Mitch - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |