Using Expect for the first time Post: 303025432

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Long time since I used "expect"

Hello all, It's been a few years since I touched 'expect' and just got it on my system. In the past, I could simply do the following: (this is just a simple example) $ expect $ ls -l $ pwd $ exit ...then a default script name would be placed in my working directory. At this point I...

2. Shell Programming and Scripting

Expect and auto expect command

I need to run a remote application(GUI) in a client.i.e on running a script in the client machine i should get the GUI application which is running in the server by providing password through the script.Will expect or autoexpect command suit for this scenario? could anyone help me by posting some...

3. Shell Programming and Scripting

strange expect script behavior, or am i misunderstanding expect 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....

4. Shell Programming and Scripting

Need help with Expect script for Cisco IPS Sensors, Expect sleep and quoting

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...

5. Shell Programming and Scripting

Expect - Comparison of expect value and loop selection

Hello All, I am trying to automate an installation process using expect and sh script. My problem is that during the installation process the expected value can change according to the situation. For Example if this is a first time installation then at step 3 I'll get "Do you want to accept...

6. Programming

Calling expect script inside another expect

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...

7. Shell Programming and Scripting

Expect script to suspend expecting for a time period.

I have a simple Expect script to power a system on and off in an endless loop looking for an ERROR message at which point the script should exit. But I need to skip the first 60 seconds after each power on or off and not exit if there are ERROR messages during that time. I thought I could use...

8. Shell Programming and Scripting

Expect script idles for a long time

the following code works sometimes. other times, it behaves mysteriously. when the script sshs to a box, it is suppose to automatically begin running the command it is told to run. but in this case, after this script logs into a host, it just sits there at the prompt and does not run the...

9. Programming

Expect script returning string following a found expect.

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 ...

LEARN ABOUT REDHAT

runtest

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.  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)

								    08 Dec 1998 							runtest(1)