Stefan Behnel, 30.01.2010 07:36: > Pascal Chambon, 29.01.2010 22:58: >> I've just recently realized the huge problems surrounding the mix of >> multithreading and fork() - i.e that only the main thread actually >> survived the fork(), and that process data (in particular, >> synchronization primitives) could be left in a dangerously broken state >> because of such forks, if multithreaded programs. > > I would *never* have even tried that, but it doesn't surprise me that it > works basically as expected. I found this as a quick intro: > > http://unix.derkeiler.com/Newsgroups/comp.unix.programmer/2003-09/0672.html
... and another interesting link that also describes exec() usage in this context. http://www.linuxprogrammingblog.com/threads-and-fork-think-twice-before-using-them Stefan _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
