From owner-freebsd-current Thu Apr 4 14:36:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA09880 for current-outgoing; Thu, 4 Apr 1996 14:36:42 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA09867 for ; Thu, 4 Apr 1996 14:36:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.6.12/8.6.6) with SMTP id PAA13355; Thu, 4 Apr 1996 15:31:16 -0700 Message-Id: <199604042231.PAA13355@rover.village.org> To: Nate Williams Subject: Re: tty-level buffer overflows - what to do? Cc: Joe Greco , root@deadline.snafu.de (Andreas S. Wetzel), current@FreeBSD.org In-reply-to: Your message of Thu, 04 Apr 1996 12:12:03 MST Date: Thu, 04 Apr 1996 15:31:16 -0700 From: Warner Losh Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk : With 2 lines going full blast (sup updates!) I see *NO* overflows on my : box. Again, my box is running with about 6MB of free memory all the : time, so I rarely hit the disk, but I've done compiles on the machine to : upgrade software with no noticeable degradation of serial speed. We have 4 SLIP lines going full blast from time to time on our 386 DX-40 (with 387 math co) 8M memory and a 40MB IDE drive. There is also a SMC Ethernet card to boot that all of our mail and news travels out of. While there is little disk activity, we've never had a overflow in our logs. All the internal modems that we use have 16550A UARTs on them (or clones). This is a 1.1.5.1R system, but I doubt that matters. All of the serial lines are locked at 115200 bps. Warner