This is the mail archive of the
mailing list for the Cygwin project.
Re: Failure with fork()
- From: "Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>
- To: cygwin at cygwin dot com
- Date: Thu, 27 Jun 2013 16:58:02 -0500
- Subject: Re: Failure with fork()
- References: <alpine dot DEB dot 2 dot 02 dot 1306271112580 dot 27492 at enira dot zlyna dot ubzr> <alpine dot DEB dot 2 dot 02 dot 1306271148230 dot 27492 at enira dot zlyna dot ubzr> <51CC8EE9 dot 1080401 at gmail dot com> <alpine dot DEB dot 2 dot 02 dot 1306271225460 dot 27492 at enira dot zlyna dot ubzr> <51CCA6FB dot 5060804 at users dot sourceforge dot net> <alpine dot DEB dot 2 dot 02 dot 1306271429000 dot 27492 at enira dot zlyna dot ubzr>
On 2013-06-27 16:52, Alan W. Irwin wrote:
Once the relevant snapshot is released I will let you know how far I
The 20130627 snapshot is now available.
get with a variant of the above I have thought of which is replacing
cygwin1.dll on the fly when the individual step of the initial run of
setup.exe that installs cygwin1.dll is completed. That method takes
advantage of the fact that the fork issue only occurs during the final
step of the install and presumably nothing is using cygwin1.dll when
the prior step that installs cygwin1.dll is completed. So ideally
this method would be completely error free, but I will see about that,
and if not I will fall back to trying your method.
That might just work, if you get the timing right.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple