On Sun, 2005-11-27 at 13:07 -0600, Gregory P. Ennis wrote: > Dear List, > > I upgraded our gateway firewall from FC1 to FC4 this weekend. > Everything is working perfectly except some 'expect' scripts that I used > to login to a old SCO box that does not have ssh. > > The script worked perfectly on FC1, but on FC4 appears to stall at the > login prompt. It appears to me that the script is not sending the > "$env(USER)r". I tried replacing the the env variable with the exact > user name, but the script continues to fail. > > expect -exact "r > login: " > send -- "$env(USER)r" > expect -exact "$env(USER)r > Password:" > send -- "$env(PUSER)r" > expect -exact "r > > I reviewed our mailing list and did not see this reported so I thought I > would send this out to see if someone else has had the same problem. > > Greg Ennis I think I have the solution so I will post it for the list archives. It looks like the amount of data for the expect command (ie expect -exact "\rlogin") has had the maximum allowable size of the text received reduced. I had some expect command lines waiting for as much as 500 characters. When I reduced each expect command to wait for no more than 100 characters per command the scripts began working like they did on FC1. Obviously there may be other factors besides 'Expect' that is causing this on FC4, but it was an easy fix. I hope this note will save someone some trial and error time when if they use 'Expect' on FC1 and upgrade to FC4 Greg
