This is the mail archive of the
mailing list for the Cygwin project.
Problem forking from Zsh under 1.7 when installed under UNC path
- From: Nikolai Weibull <now at bitwi dot se>
- To: cygwin at sourceware dot org
- Date: Mon, 2 Jul 2012 15:24:04 +0200
- Subject: Problem forking from Zsh under 1.7 when installed under UNC path
I have come across a problem that occurs when Zsh (both 4.3.11 and
4.3.12) tries to fork when Cygwin (1.7) has been installed under a UNC
path. The problem occurs because Zsh has support for dynamically
loaded modules. When Zsh forks to run a process (like âlsâ), Cygwin
tries to map these modules (DLLs) into the new process, but somewhere
along the line gets confused as to what passed was used to load the
2 [main] zsh 8220 child_info_fork::abort: unable to map UNC\Filer\Programs
\Cygwin\lib\zsh\4.3.11\zsh\parameter.dll, Win32 error 126
compaudit:91: fork failed: resource temporarily unavailable
2 [main] zsh 4836 child_info_fork::abort: unable to map UNC\Filer\Programs
\Cygwin\lib\zsh\4.3.11\zsh\zle.dll, Win32 error 126
compinit:526: fork failed: resource temporarily unavailable
I have installed Cygwin under the path \\Filer\Programs\Cygwin.
MODULE_PATH in Zsh is /usr/lib/zsh/4.3.11.
The modules are loaded fine inside Zsh itself, but canât be mapped
over into the fork properly, it seems.
This occurred when I upgraded Cygwin from 1.5 to 1.7. Zsh was also
upgraded from 4.3.11 to 4.3.12 at the same time, but was since
downgraded to exclude any changes that may have occurred in Zsh
between 4.3.11 and 4.3.12.
Note that running âlsâ from Bash works fine, as it doesnât have
Mapping \\Filer\Programs\Cygwin to a drive and then running Zsh from
there works fine, so it seems that the issue is completely isolated to
that of the UNC path to the module not being saved/used correctly.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple