This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: long command lines
- To: Daniel Barclay <Daniel dot Barclay at digitalfocus dot com>
- Subject: Re: long command lines
- From: Mumit Khan <khan at NanoTech dot Wisc dot EDU>
- Date: Mon, 29 Jan 2001 11:08:38 -0600 (CST)
- cc: cygwin at cygwin dot com
On Mon, 29 Jan 2001, Daniel Barclay wrote:
> I thought GNU software tried to avoid arbitrary limit like that. Shouldn't
> the only limit be virtual memory?
The maximum length of the argument vector is typically determined by the
underlying OS kernel interface; even if your user-level software such
as the shell supports say 100 KB long argument vector, it's still limited
by what the kernel limit is. In Cygwin's case, Windows limits the length,
not Cygwin.
However, note that most (all?) exisiting OSs have these predefined limits
mostly for efficiency. The limits could be very large of course, or settable
at boot time, but it's there. The max number of open file descriptors is
one of the typical examples.
> That is, shouldn't bash keep reallocating (enlarging) its buffer until the
> pattern has been expanding, or until it runs out of memory?
Bash handles long command lines just fine.
Regards,
Mumit
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple