From owner-freebsd-hackers Thu Feb 9 12:53:21 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA17443 for hackers-outgoing; Thu, 9 Feb 1995 12:53:21 -0800 Received: from wcarchive.cdrom.com (wcarchive.cdrom.com [192.216.191.11]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA17437 for ; Thu, 9 Feb 1995 12:53:19 -0800 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by wcarchive.cdrom.com (8.6.8/8.6.6) with SMTP id MAA00423 for ; Thu, 9 Feb 1995 12:53:13 -0800 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA10479; Thu, 9 Feb 95 11:54:53 CST From: Joe Greco Message-Id: <9502091754.AA10479@brasil.moneng.mei.com> Subject: Re: uucico... To: steve@cioeserv.cioe.com (Steve Ames) Date: Thu, 9 Feb 1995 11:54:52 -0600 (CST) Cc: freebsd-hackers@wcarchive.cdrom.com In-Reply-To: <199502090027.TAA12895@cioeserv.cioe.com> from "Steve Ames" at Feb 8, 95 07:27:03 pm X-Mailer: ELM [version 2.4beta PL9] Content-Type: text Content-Length: 935 Sender: hackers-owner@FreeBSD.org Precedence: bulk > OLD: chat "" \d ogin: \L word: \P > NEW: chat "" \d ogin: \d\L word: \P > > Mind, I'm not entirely sure why that worked but it did. With full > debuggin turned on on both sides you can see what happens. Some getty's flush (or otherwise mangle) data in the input buffer right after printing "login:", a pause after the receipt of the "login:" does wonders to ensure that the text you're sending isn't victimized in this manner. I know it sounds silly. But remember that another character (' ') is printed after the ":", which most people don't wait for, and a fast modem and box on the other end can easily turn around and start pumping out the login name during this time (and the flush is not instantaneous, either). ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847