From owner-freebsd-questions Mon Sep 29 06:38:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA10671 for questions-outgoing; Mon, 29 Sep 1997 06:38:39 -0700 (PDT) Received: from jumpgate.cpn.org.au (slip3.tas.gov.au [147.109.237.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA10663 for ; Mon, 29 Sep 1997 06:38:35 -0700 (PDT) Received: from jumpgate.cpn.org.au (jumpgate.cpn.org.au [172.16.1.1]) by jumpgate.cpn.org.au (8.8.5/8.8.3) with SMTP id XAA18517; Mon, 29 Sep 1997 23:37:44 +1000 (EST) Date: Mon, 29 Sep 1997 23:37:44 +1000 (EST) From: Carey Nairn X-Sender: cpn@jumpgate.cpn.org.au To: Brian Somers cc: Terry Dwyer 61 8 9491 5161 , questions@freefall.FreeBSD.org Subject: Re: iijppp and chat scripts In-Reply-To: <199709272223.XAA05609@awfulhak.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Sep 1997, Brian Somers wrote: > > On Sat, 27 Sep 1997, Carey Nairn wrote: > > > > I don't think you have to wait for the last char in the prompt string to > > arrive before you can do a match. It may be worthwhile to try matching > > on the string "name" in the termserver's prompt assuming what you've > > shown below is the actual prompt you see. > > Or you could do a few expect/sends for different bits of the same > prompt. For example, if you've got > > login on abcde: > or > login on defgh: > > (with spaces at the end of each), you could have a chat that does > > set login "login\son\s \"\" \\s MyLogin" > > > > hi guys, > > > > > > I'm looking for a chat guru... > > > > > > When I dial in to my provider, I will get a different prompt depending on > > > which terminal server I connect to. Is there a way in the login script to > > > test for on of multiple different prompts? > > > > > > e.g. > > > > > > login to ts1, prompt is ts1name> > > > login to ts2, prompt is ts2name# > > > Both pmrompts are completely unique so Terry's suggestion won't work unfortunately. What I need is to try Brian's idea and put in a couple of different expect values and hope the terminal server doesn't hangup waiting for the timeouts. thanks guys, Carey Nairn