Training, Open Source computer languages
PerlPHPPythonMySQLApache / TomcatTclRubyJavaC and C++LinuxCSS 
Search for:
Home Accessibility Courses Diary The Mouth Forum Resources Site Map About Us Contact
 
For 2023 (and 2024 ...) - we are now fully retired from IT training.
We have made many, many friends over 25 years of teaching about Python, Tcl, Perl, PHP, Lua, Java, C and C++ - and MySQL, Linux and Solaris/SunOS too. Our training notes are now very much out of date, but due to upward compatability most of our examples remain operational and even relevant ad you are welcome to make us if them "as seen" and at your own risk.

Lisa and I (Graham) now live in what was our training centre in Melksham - happy to meet with former delegates here - but do check ahead before coming round. We are far from inactive - rather, enjoying the times that we are retired but still healthy enough in mind and body to be active!

I am also active in many other area and still look after a lot of web sites - you can find an index ((here))
echoing commands while in interact

Posted by jaymzter (jaymzter), 3 March 2008
use expect to connect, then hand off control with interact. During the session we listen to run procs automatically for the user. Here's the example

Code:
proc ossi {} {
global home
global user
set scriptdir $home/ossi.sc
expect_user -re "(.*)\r"
set script [string trimleft $expect_out(1,string)]
set runcmd "$scriptdir/$script"
set logfilename $home/$script-[exec date +%H%M%S]
send script cmds here
}

spawn -noecho ssh $remote

interact {
       -echo "~ossi" {
               ossi
               }


everything works. The question centers around how the script "interacts" with the user. The user sees "~ossi" echoed to the screen, but not the name of the script they type in afterwards.

How do I enable echoing of the rest of what they type, as they type it?

P.S. - the way this is implemented, where I grab the user input within the proc, is the only way I could figure out how to capture the script args (in this case just a name) after invoking ossi.

Posted by jaymzter (jaymzter), 5 March 2008
I corrected this issue with a judicious use of the stty command within the proc



This page is a thread posted to the opentalk forum at www.opentalk.org.uk and archived here for reference. To jump to the archive index please follow this link.

You can Add a comment or ranking to this page

© WELL HOUSE CONSULTANTS LTD., 2024: Well House Manor • 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 01144 1225 708225 • FAX: 01144 1225 793803 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho