From owner-freebsd-current Sat Jun 22 10:47:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA22487 for current-outgoing; Sat, 22 Jun 1996 10:47:15 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA22480 for ; Sat, 22 Jun 1996 10:47:14 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id KAA13568; Sat, 22 Jun 1996 10:47:30 -0700 Date: Sat, 22 Jun 1996 10:47:28 -0700 (PDT) From: Veggy Vinny To: Craig Huckabee cc: Brian Tao , paulo@centauro.isr.uc.pt, current@freebsd.org Subject: Re: out of ptys? In-Reply-To: <199606221531.LAA19632@mispwoso.nosc.mil> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 22 Jun 1996, Craig Huckabee wrote: > > On Thu, 20 Jun 1996, Gary Palmer wrote: > > > > > > It does? Whoops. I think the limit is actually 256 now (can someone > > > confirm this?) > > > > No problems with 256 of 'em here, so the limit is at least that. > > I've seen somewhere around 170+ allocated here (logins + screen > > sessions) on a busy night with only one of the servers accepting > > logins. I'm not sure what is involved getting more than 256 tty > > pairs, since tty[pqrsPQRS][0-9a-v] only gives you 256 devices. > > I'm running 256 here as well, and we've used most of them all at once > (during some stress testing). There's also this note in /dev/MAKEDEV: > > [in the section for pty creation....] > # This still leaves [tuTU]. > > Dunno if that means they are also available giving a max of 384. Hmmm, we have a Dual P5-100 w/128megs and somehow the machine slows down to turtle speed..... Also, for some reason, when there is 150 httpd sessions running, it seems to flood the router and then the entire network is really lagging... we're on a T1 with a Wellfleet(sp?) router, does anyone know anything about this router and how to get this problem fixed? Vince System Administration Team/GaiaNet Corporation