Date: Fri, 12 Mar 2010 10:00:06 -0800
From: Cesar Crusius <cesar@cariden.com>
To: cygwin@cygwin.com
Subject: Re: Re: "can't create master tty" errors
Message-ID: <20100312180006.GF3442@sunray.mv.cariden.com>
Reply-To: Cesar Crusius <cesar@cariden.com>
References: <20100309180647.GB3442@sunray.mv.cariden.com> <416096c61003091250p186ac05bj8b0b4f7c2b224c85@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <416096c61003091250p186ac05bj8b0b4f7c2b224c85@mail.gmail.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Tue, Mar 09, 2010 at 08:50:38PM +0000, Andy Koppe wrote:
> Cesar Crusius:
> > I am using Cygwin and SSH to do automated remote builds using Visual
> > C++. It works for a few days, but invariably things start failing with
> > messages like these (this one from a build log):
> >
> > Makefile:9: MakePID: 5964
> >      1 [main] env 2748 C:\cygwin\bin\env.exe: *** fatal error - can't create master tty
> 
> The number of tty devices is limited, so the first thing to check is
> whether your build system simply leaves too many sessions open, by
> checking the output of 'ps'.
> 
> If not, it might be to do with the following. If you open a couple of
> terminals, they're assigned  tty0 and tty1. If you then close tty1 and
> open another terminal, that again becomes tty1. But if you close tty0,
> and open yet another one, that becomes tty2 rather than tty0.
> 
> That appears to be the general rule: a new terminal gets the next ID
> above the current highest one. This means, however, that if opening
> and closing of terminal sessions is interleaved in certain ways,
> Cygwin might eventually run out of terminal IDs, even if only few of
> them are actually used. High numbers in the TTY column of the 'ps'
> output would point to that.
> 
> Cgf, am I talking rubbish here?
> 
> Andy
> 

Hi there,

It happened again today. Rebooting the machine. Any other clues? This is
happening pretty frequently... Can't ssh into it or open a Cygwin
terminal, so I can't see what's going on via 'ps'.

- Cesar

--
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