From owner-freebsd-hackers Wed Mar 29 06:48:18 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA19353 for hackers-outgoing; Wed, 29 Mar 1995 06:48:18 -0800 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA19347 for ; Wed, 29 Mar 1995 06:48:17 -0800 Received: (from bugs@localhost) by ns1.win.net (8.6.9/8.6.9) id JAA09983 for hackers@FreeBSD.ORG; Wed, 29 Mar 1995 09:49:52 -0500 From: Mark Hittinger Message-Id: <199503291449.JAA09983@ns1.win.net> Subject: Re: Mail... (fwd) To: hackers@FreeBSD.org Date: Wed, 29 Mar 1995 09:49:51 -0500 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1118 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Pardon my ignorance, but doesn't FreeBSD have a limit of 256 psuedo-ttys? > (Then again, this might have changed in 2.x.) That could be hard limit on > interactive sessions... > Each FreeBSD machine might have such a limit. The idea here would be to build a "cluster" design to handle your growth by adding machines. Do you really want more than 256 people on one box simultaneously? Using a terminal server front end will allow you to switch users based on incoming protocol type, load, or software version. (you also don't have to futz with serial drivers or burden your box with serial interrupts). I use Xylogics Annex-3's for our incoming dialups. Based on the account name I can switch the user to an older sysv uucp box, one of two newer FreeBSD boxes, an NT box, or PPP directly to our Cisco/T1. One philosophy of design that you definetly do not want to use is the "one giant box does it all" plan. This is an old mainframe plan and every plan has a flaw! In the 80's the centralized versus distributed debate was fought and the centralized guys lost. Regards, Mark Hittinger bugs@win.net