Date: Mon, 29 Sep 1997 23:37:44 +1000 (EST) From: Carey Nairn <cpn@ccd.tas.gov.au> To: Brian Somers <brian@awfulhak.org> Cc: Terry Dwyer 61 8 9491 5161 <tdwyer@io.telstra.com.au>, questions@freefall.FreeBSD.org Subject: Re: iijppp and chat scripts Message-ID: <Pine.BSF.3.96.970929232949.988B-100000@jumpgate.cpn.org.au> In-Reply-To: <199709272223.XAA05609@awfulhak.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970929232949.988B-100000>