Re^3: Expect question

I might be wrong of course, but it looks to me like that's just the parsing of the parameter you gave to the function, not what was received from the server.

Could the problem have something to do with the "exact match" part? You can see it's trying to match against 'Connecting to <host_ip>...\r\nPassword: '

So perhaps you need something like '.*Password: ' as a pattern? (assuming it takes regexes).

Comment on Re^3: Expect question Select or Download Code

Replies are listed 'Best First'.
Re^4: Expect question by RaduH (Scribe) on Oct 29, 2007 at 15:30 UTC
I have replaced my "Password: " pattern with the entire Connecting to... blah blah string and that one is matched. The regexp does not work which seems weird. In this case it's easy to either use the entire string or even generate it before using it, so I can use the IP and a parameter, but it just doesn't feel right. Somehow I suspect I should be able to verify only the last part of a return... I can easily imagine servers that spit out a whole load of stuff before prompting you for an input and I just don't think we always need to search and match that entire speech... At least I know it's about tail matching now.	[reply]

Replies are listed 'Best First'.

Re^4: Expect question
by RaduH (Scribe) on Oct 29, 2007 at 15:30 UTC

I have replaced my "Password: " pattern with the entire Connecting to... blah blah string and that one is matched. The regexp does not work which seems weird. In this case it's easy to either use the entire string or even generate it before using it, so I can use the IP and a parameter, but it just doesn't feel right. Somehow I suspect I should be able to verify only the last part of a return... I can easily imagine servers that spit out a whole load of stuff before prompting you for an input and I just don't think we always need to search and match that entire speech... At least I know it's about tail matching now.

[reply]