From: Chris Felaco <cfelaco@openmarket.com>
To: cygwin@sourceware.cygnus.com
Subject: sh can't run any programs from script when PATH exceeds 2500 characters
Date: Wed, 24 Feb 1999 11:44:00 -0000 [thread overview]
Message-ID: <36D457C4.69A571D2@openmarket.com> (raw)
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....
WARNING: multiple messages have this Message-ID
From: Chris Felaco <cfelaco@openmarket.com>
To: cygwin@sourceware.cygnus.com
Subject: sh can't run any programs from script when PATH exceeds 2500 characters
Date: Sun, 28 Feb 1999 23:02:00 -0000 [thread overview]
Message-ID: <36D457C4.69A571D2@openmarket.com> (raw)
Message-ID: <19990228230200.95PcHFVWLWh7Gbd4d2gkxn2miNmWtwCpb560kbTOYis@z> (raw)
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....
next reply other threads:[~1999-02-24 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-24 11:44 Chris Felaco [this message]
1999-02-28 23:02 ` Chris Felaco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36D457C4.69A571D2@openmarket.com \
--to=cfelaco@openmarket.com \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).