public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: Eric Blake <eblake@redhat.com>
Cc: cygwin@cygwin.com
Subject: Re: Command line length in Ash or Dash Shells
Date: Tue, 27 Oct 2015 18:12:00 -0000	[thread overview]
Message-ID: <22063.37889.345000.595112@woitok.gmail.com> (raw)
In-Reply-To: Msg <562E514E.4000801@redhat.com> of 2015-10-26 10:14:06 -0600 from eblake@redhat.com

Eric,

On Monday, 2015-10-26 10:14:06 -0600, you wrote:

> ...
>                                                                  So once
> you start a dash shell, that dash shell can start any number of other
> dash shells with no command line length limit other than the memory
> available to your machine.

Assume I terminate  Cygserver and any  other Cygwin  services running, I
then start "ash.exe" by double clicking it in a Windows Explorer window,
from the  command line  in the  "ash.exe"  window  I start my  Ash Shell
script which in turn starts  "setup-x86*.exe"  with a  very long command
line.

Am I interpreting you correctly in assuming that under these circumstan-
ces the maximum length of this command line  is 2 * 10**9 ASCII charact-
ers on my box?

This would be just enough I think.

Sincerely,
  Rainer

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

  reply	other threads:[~2015-10-27 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 13:54 Dr Rainer Woitok
2015-10-26 17:45 ` Eric Blake
2015-10-27 18:12   ` Dr Rainer Woitok [this message]
2015-10-27 19:06     ` Corinna Vinschen
2015-10-27 23:30       ` Dr Rainer Woitok
2015-10-28  0:30     ` Eric Blake

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=22063.37889.345000.595112@woitok.gmail.com \
    --to=rainer.woitok@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=eblake@redhat.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).