From owner-freebsd-isp Mon Dec 23 02:14:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA27359 for isp-outgoing; Mon, 23 Dec 1996 02:14:26 -0800 (PST) Received: from axe.cablenet.net (axe.cablenet.net [194.154.36.65]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA27333 for ; Mon, 23 Dec 1996 02:14:18 -0800 (PST) Received: (from damian@localhost) by axe.cablenet.net (8.6.9/8.6.9) id KAA11077 for freebsd-isp@freebsd.org; Mon, 23 Dec 1996 10:12:07 GMT Message-Id: <199612231012.KAA11077@axe.cablenet.net> Subject: Re: getty login prompt delay To: freebsd-isp@freebsd.org Date: Mon, 23 Dec 1996 10:12:06 +0000 (GMT) From: "Damian Hamill" In-Reply-To: <199612201657.QAA05634@axe.cablenet.net> from "Damian Hamill" at Dec 20, 96 04:57:51 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I wrote: > > I'm convinced that the reason why I am still getting handshake errors is > that upon connection getty is firing off the login prompt before the > winsock is ready for it and it's getting lost. How do I make getty > delay a while before issueing the login prompt or where are the sources > so I can patch getty if it doesn't support this feature ? I found the sources, added a delay option to gettytab and hey presto I've since been getting a 97% connection success rate. Who should I mail the patch to ? regards damian -- "There's plenty of rainforest" - A person selling Living Marxism at Edinburgh Festival. Damian Hamill damian@cablenet.net