03-03-2017
You need \r at the end of expect commands, i.e. expect "path? (Y/N)\r"
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello to all...this is my first post (so please go easy). :)
I feel pretty solid at expect scripting, but I'm running into an issue that I'm not able to wrap my head around. I wrote a script that is a little advanced for logging into a remote Linux machine and changing text in a file using sed.... (2 Replies)
Discussion started by: v1k0d3n
2 Replies
2. Shell Programming and Scripting
Here is a snippet of code that work for me:
expect "abc" {send_log "abc found" } \
"def" {send_log "def found" } \
"123" {send_log "123 found}
however the following does not and according to the book "Exploring Expect" it should be equivalent:
expect { "abc"... (1 Reply)
Discussion started by: twk
1 Replies
3. Shell Programming and Scripting
This Expect script provides expect with a list of IP addresses to Cisco IPS sensors and commands to configure Cisco IPS sensors. The user, password, IP addresses, prompt regex, etc. have been anonymized. In general this script will log into the sensors and send commands successfully but there are... (1 Reply)
Discussion started by: genewolfe
1 Replies
4. Shell Programming and Scripting
Hi all,
I'm new with expect. I'm developing a quick script to check my sudo access on 100 servers.
So using !/bin/usr/expect doesn't work. So decided to use it as :
expect -c "set timeout -1;\
spawn ssh $IPADDR -l $USERID ;\
match_max 100000;\
expect {
-re... (0 Replies)
Discussion started by: EmersonOrci
0 Replies
5. Shell Programming and Scripting
Hey all. Sometimes I'm tasked to change some router configs for the entire network (over 3,000 Cisco routers). Most of the time its a global config parameter so its done with a loop and an IP list as its the same configuration change for all routers. This is working OK.
However, sometimes an... (3 Replies)
Discussion started by: mrkz1974
3 Replies
6. Programming
Hi,
Am very new to expect scripting..
Can You please suggest me how to call an expect script inside another expect script..
I tried with
spawn /usr/bin/ksh
send "expect main.exp\r"
expect $root_prompt
and
spawn /usr/bin/ksh
send "main.exp\r"
expect $root_prompt
Both... (1 Reply)
Discussion started by: Priya Amaresh
1 Replies
7. UNIX for Advanced & Expert Users
Not able to execute the file in remote host using except utility
I am automating the SFTP keys setp process:
So i created the expect script for controlling the output of shell
below is my main code:
Code:
#!/usr/bin/expect
set fd
set password
close $fd
set df
set app
close $df... (1 Reply)
Discussion started by: Manoj Bajpai
1 Replies
8. Programming
I have an expect script called remote that I want to call from inside my expect script called sudoers.push, here is the code that is causing me issues:
set REMOTE "/root/scripts/remote"
...
log_user 1
send_user "Executing remote script as $user...\n"
send_user "Command to execute is: $REMOTE... (1 Reply)
Discussion started by: brettski
1 Replies
9. Shell Programming and Scripting
Dear All,
I have a requirement where I have to SFTP or SCP a file in a batch script. Unfortunately, the destination server setup is such that it doesn't allow for shell command line login. So, I am not able to set up SSH keys. My source server is having issues with Expect. So, unable to use... (5 Replies)
Discussion started by: ss112233
5 Replies
10. Programming
I'm fairly new to scripting so this might not be possible.
I am using Expect with Cisco switches and need to capture the string after finding the expect request. For example, when I issue "show version" on a Nexus switch, I'm looking to capture the current firmware version:
#show version
... (0 Replies)
Discussion started by: IBGaryA
0 Replies
runtest(1) General Commands Manual runtest(1)
NAME
runtest - the DejaGnu test driver program
SYNOPSIS
runtest [ options ]
DESCRIPTION
DejaGnu is a framework for running test suites on GNU tools. It is written in expect, which uses Tcl (Tool command language). runtest is
the test driver program; use it to control what tests to run, and variations on how to run them.
You can find a comprehensive description of DejaGnu and runtest in The DejaGnu Testing Framework or its Info version, dejagnu.info.
OPTIONS
--all Print all test output to screen. By default, only unexpected results are displayed.
--baud rate
Set the baud rate for a serial line connection. Some serial interface programs (like tip) don't use this value but instead use a
separate initialization file.
--connect type
The type of connection to use. The choices are rlogin, telnet, rsh, kermit, tip and mondfe.
--debug
Turn on expect internal debugging output. All output is logged to a file called dbg.out. The output of the --strace also goes into
this file.
--help Prints out a help screen and then exits.
--host type
The configuration string for the host.
--ignore test1.exp test2.exp ...
Do not run the specified tests.
--mail 'name1 name2 ...'
Electronic mail addresses to receive test results.
--name hostname
The network hostname of the target board.
--objdir path
path is a directory containing compiled test code.
--outdir directory
The name of a directory for test log output.
--reboot
Reboot the target board when runtest initializes (if supported).
--srcdir path
path is a directory containing test directories.
--strace N
Turns on expect internal tracing to N levels deep.
--target type
The configuration string for the target.
--tool toolname
Specify the tool to be tested. toolname controls the test suite applied, and the associated initialization module.
--verbose, -v
Turns on more debugging output from test cases and DejaGnu utility code. Use more than once to increase output further.
--version, -V
Prints out the versions of DejaGnu, expect and Tcl.
-D[number]
Activate the Tcl debugger.number can be either 1 or 0. If it is 1, then the expect shell will break when it starts to run. All ^C's
drop DejaGnu back to the debugger prompt. A 0 starts DejaGnu like normal, but a ^C drops to the debugger prompt.
Any file name on the command line is assumed to be a subset
of the test names to run. Usually these are the names of the expect test driver, ie... special.exp.
Makefile style variables are used to specify tool names and their flags; these and other configuration dependent values are saved in the
file site.exp, created during configuration.
EXIT CODES
runtest sets the exit code to 1 if any of the tests failed, or sets it to 0 if all the tests passed.
SEE ALSO
The DejaGnu Testing Framework (dejagnu.info). This is the DejaGnu manual; its source is the SGML files doc/*.sgml. in the DejaGnu distri-
bution.
AUTHOR
Rob Savoye (rob@welcomehome.org)
29 Jul 2003 runtest(1)