[314] in linux-net channel archive
Re: Expect, Send, and dropped characters
daemon@ATHENA.MIT.EDU (Rob Janssen reading Linux mailingl)
Fri May 12 19:37:02 1995
To: msp@tyrell.net
Date: Fri, 12 May 1995 23:19:50 +0200 (MET DST)
Cc: linux-net@vger.rutgers.edu
In-Reply-To: <m0s9s2o-0000y1C@carpediem.org> from "M.S. Petrovic" at May 12, 95 05:34:06 am
Reply-To: linux-vger@wab-tis.rabobank.nl
From: linux@sys3.pe1chl.ampr.org (Rob Janssen reading Linux mailinglist)
According to M.S. Petrovic:
> I'm using chat as a front end to establishing a connection to a remote
> server host. Unfortunately, characters dropped from the *middle* of the
> "expect" strings often prevent the negotiation from going to successful
> completion. I have seen many references to using only the trailing
> portion of the expect string, should a leading portion be lost, but have
> never seen reference to characters within the string being dropped.
> These observations above are based on a reading of /usr/adm/messages
> during the chat script converstation.
Make sure you don't have a getty running on the line, or have created
a suitable lock file to keep it at bay. The getty may wake up when you
start chatting with the port, and eat up some characters before it
realizes it should not be doing it.
(this depends on the particular getty in use)
Rob
--
+------------------------------------+--------------------------------------+
| Rob Janssen rob@knoware.nl | AMPRnet: rob@pe1chl.ampr.org |
| e-mail: pe1chl@wab-tis.rabobank.nl | AX.25 BBS: PE1CHL@PI8WNO.#UTR.NLD.EU |
+------------------------------------+--------------------------------------+
