This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: fork() and NT error 0xC0000135 (STATUS_DLL_NOT_FOUND)
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 29 Oct 2013 13:23:21 -0400
- Subject: Re: fork() and NT error 0xC0000135 (STATUS_DLL_NOT_FOUND)
- Authentication-results: sourceware.org; auth=none
- References: <5F8AAC04F9616747BC4CC0E803D5907D0C40B026 at MLBXv04 dot nih dot gov>
- Reply-to: cygwin at cygwin dot com
On Tue, Oct 29, 2013 at 04:13:14PM +0000, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>Hello All,
>
>I can't find a similar problem reported earlier, so please excuse the question
>if it looks familiar.
>
>We have a software package that installs like a miniature CYGWIN deployment
>(basically, only cygwin1.dll and just a few other libraries in /bin
>along with cygrunsrv.exe), and there are no shells.
>
>cygrunsrv.exe is used to register and launch a Windows service with a binary
>located under "/opt/..." (which is a ported UNIX server). The binary is started
>just fine, but when it tries to fork(), it gets the error 0xC0000135 (w/ errno=11,
>EAGAIN). I traced it down to the fact that before fork() there is chdir("/") in
>that server binary. Can it be the reason for the failed fork() that it can no longer
>find cygwin1.dll? Unfortunately, I can't extend Windows PATH to include the
>CYGWIN /bin directory (because the cygrunsrv runs under an unmanaged service
>account). Is there any other fix?
Cygwin doesn't rely on the PATH environment variable to find the binary
being forked. It would be disastrous if it did.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple