documentation should mention issues of fork and multi-threading

[MartinNowak]

http://forum.dlang.org/post/[email protected] http://www.linuxprogrammingblog.com/threads-and-fork-think-twice-before-using-them

[NCrashed]

Hmm, that a complex problem. Could it be avoided by using an exec function after forking?

[MartinNowak]

Yes, I'd think so. If you can restart the daemonized process using exec, then it should avoid the problem.

[etcimon]

GC deadlock issue on the forums was resolved here: https://github.com/etcimon/libasync/pull/22

[MartinNowak]

It should still be mentioned in the readme and/or the wiki.

[andre2007]

The information here are a little bit confusing for me:

• Is this still an issue on linux?
• Does the issue occur only when I do multi threading in general or only when using libasync?

MartinNowak mentioned the issue simply can be solved by using an exec function after forking. I am not an expert here, but if this is just a few lines, could you add these line if you have some time?