Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

documentation should mention issues of fork and multi-threading #2

Open
MartinNowak opened this Issue Feb 24, 2015 · 5 comments

Comments

Projects
None yet
4 participants

NCrashed added a commit that referenced this issue Feb 24, 2015

Update README.md
Warning about #2
@NCrashed

This comment has been minimized.

Copy link
Owner

NCrashed commented Feb 24, 2015

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

@MartinNowak

This comment has been minimized.

Copy link
Author

MartinNowak commented Feb 26, 2015

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

@etcimon

This comment has been minimized.

Copy link

etcimon commented Mar 20, 2015

GC deadlock issue on the forums was resolved here: etcimon/libasync#22

@MartinNowak

This comment has been minimized.

Copy link
Author

MartinNowak commented Apr 9, 2015

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

@andre2007

This comment has been minimized.

Copy link

andre2007 commented Feb 11, 2019

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.