From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: is there a limit on how many mintty terminals can be open at once?
Date: Tue, 5 Oct 2021 06:55:48 +0900 [thread overview]
Message-ID: <20211005065548.2c02fff49d281a3166656e1d@nifty.ne.jp> (raw)
In-Reply-To: <1844552584.20211004225155@yandex.ru>
On Mon, 4 Oct 2021 22:51:55 +0300
Andrey Repin wrote:
> Greetings, Brian Inglis!
>
> > On 2021-10-03 13:58, Takashi Yano via Cygwin wrote:
> >> On Sun, 3 Oct 2021 12:25:15 -0400
> >> "Jason Pyeron" wrote:
> >>> I got the "Error: Could not fork child process: There are no
> >>> available terminals (-1)" error.
> >>> Closing N minty terminals allowed me to open exactly N more.
> >>> My google fu is poor, since I cannot seem to find relevant pages.
> >>> What is the limit?
>
> >> In current cygwin, maximum number of pty is 128.
> >> It is hard coded and not configurable by user.
> >> https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/tty.h#l15
>
> > Why would you want and how could you use 128 local terminal windows on
> > one system, where could you put them, and be able to read them, unless
> > you are building some kind of control centre, and then wouldn't GUI
> > processes forked under a windows system be more useful?
>
> Won't SSH sessions allocate pty's ?
Incoming SSH session consumes pty. Therefore, up to 128 users (or sessions)
can login to the cygwin SSH server simultaneously. This is much less than
modern Linux (e.g. 4096 on debian).
--
Takashi Yano <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2021-10-04 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 16:25 Jason Pyeron
2021-10-03 19:58 ` Takashi Yano
2021-10-04 15:37 ` Brian Inglis
2021-10-04 19:51 ` Andrey Repin
2021-10-04 21:55 ` Takashi Yano [this message]
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=20211005065548.2c02fff49d281a3166656e1d@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.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).