X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: =?ISO-8859-1?Q?Ren=E9_Berber?= <r DOT berber AT computer DOT org>
Subject:  Re: using external commands in vim causes fork error
Date:  Wed, 18 Jul 2007 23:25:28 -0500
Lines: 51
Message-ID: <f7mp3u$ivt$1@sea.gmane.org>
References:  <11681959 DOT post AT talk DOT nabble DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1
Content-Transfer-Encoding:  quoted-printable
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
In-Reply-To: <11681959.post@talk.nabble.com>
OpenPGP: url=hkp://wwwkeys.pgp.net
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

nanothief wrote:

> When attempting to use an external command in vim (mainly make), I receive
> the following error:
> :make
> sh: fork: Resource temporarily unavailable

Works fine with the distributed vim binary.

> shell returned 128
> Press ENTER or type command to continue
> E40: Can't open errorfile /tmp/v817919/0
>=20
> However if i use make from outside vim, it works perfectly. Also, if use
> :shell from within vim, almost all commands (ie ls, make, fortune, etc) f=
ail
> from the same fork error, while only the builtin commands (echo, pwd, cd,
> etc) succeed. There is no problem running multiple bash prompts, vim wind=
ows
> or make commands simultaneously. The problem only occurs when inside vim.

Also works fine.

> I have found many references to a fork error in past discussions, but in =
the
> ones I found there was no solution relevant to me.
>=20
> I built vim from the sources supplied from the cygwin installer, using
> almost all the features and most of the interfaces (python, tcl, mzscheme,
> perl). The cygwin directory is on a NTFS partition. My cygwin variable is
> set to nontsec tty binmode. Finally, I have 2gb of ram, and a dual core
> intel core 2 6600 processor.
>=20
> Any help would be greatly appreciated

The CYGWIN env. var. only has nontsec different, the other 2 are the defaul=
ts
(no need to even put them)... those are the 2 differences: your build of vi=
m,
and the nontsec, experiment with changing the later and find if your binary=
 is
the problem.
--=20
Ren=E9 Berber


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/