This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
sh can't run any programs from script when PATH exceeds 2500 characters
- To: cygwin@sourceware.cygnus.com
- Subject: sh can't run any programs from script when PATH exceeds 2500 characters
- From: Chris Felaco <cfelaco@openmarket.com>
- Date: Wed, 24 Feb 1999 14:49:24 -0500
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- Organization: PSW Technologies
- Sender: cygwin-owner@sourceware.cygnus.com
I have a sh script that basically sets up a bunch of environment variables, constructs a PATH based on some input files and then runs a program. If the path is over 2500 characters, the program (no matter what program it is) gives the following error:
foo: error 11
Even Win32 native apps such as cmd fail this way. Unfortunately, I can't easily reproduce the problem. I've tried writing a simple bare script to test it, but it won't fail. It only fails in my rather involved script that makes use of several input files from various locations.
Is there a hard limit on the PATH size? Is there perhaps a fixed buffer size used for the PATH conversion in the cygwin DLL? Any help or suggestions are appreciated....
begin:vcard
n:Felaco;Chris
tel;work:(781)359-7367
x-mozilla-html:FALSE
url:http://www.psw.com/
org:PSW Technologies
adr:;;One Innovation Drive;Natick;MA;01760;
version:2.1
email;internet:cfelaco@openmarket.com
title:Software Engineer
fn:Chris Felaco
end:vcard
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com