Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Expect for Windows
Top Forums Shell Programming and Scripting Expect for Windows Post 302155551 by ramen_noodle on Friday 4th of January 2008 01:25:46 PM
Old 01-04-2008
You are trying to exec a local grep binary that does not exist. The exec command you are using executes on the local machine, not on the remote machine. in order to get the output of a grep on the remote host try something like (untested) :

Code:
set prompt "(\n.*# | .*> | .*\$)" 
set searchstr [lindex $argv 2]
set rfilename [lindex $argv 3]

expect {

           -re $prompt {
                           send "grep $searchstr $rfilename\r\n"
                           expect -re "\n(.*)\n$prompt" {
                                                                    send_user "\n$expect_out(buffer),$expect_out(1,string)\n"
                                                                    close $spawn_id
                                                                     wait $spawn_id
                           }
             }
}

 

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Windows expect

I am using ActiveState 8.4.16.0, I have found this code format that seems to work great: expect "Login:*" send "root\r" expect ">*" send "ksh\r" expect "#*" send "tar -xvf /dev/rmt/0m\r" expect "#" My question is, how do I set it up to fail out if one of the expect calls doesn't... (0 Replies)
Discussion started by: dave_m
0 Replies

2. 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.... (2 Replies)
Discussion started by: v1k0d3n
2 Replies

3. 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... (1 Reply)
Discussion started by: genewolfe
1 Replies

4. 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... (0 Replies)
Discussion started by: alokrm
0 Replies

5. 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... (1 Reply)
Discussion started by: Priya Amaresh
1 Replies

6. 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 ... (0 Replies)
Discussion started by: IBGaryA
0 Replies

LEARN ABOUT DEBIAN

tgn

TGN(1)																	    TGN(1)

NAME

       tgn - a network traffic generator

SYNOPSIS

       tgn [-V] [-v] [-l] [-s random seed] [-w PCAP filename] [-o output speaker] [-c packet count] [-h] [PDU definition]

DESCRIPTION

       tgn is a network traffic generator. It is command-line interface (CLI) program that does the same thing as the send_network command of the
       Network Expect framework. Refer to nexp(1) for additional details regarding the send_network command.

       The only mandatory option is a PDU definition.

       The -c switch allows to specify the number of packets to send. If -c is not provided then the number of packets to send is calculated
       automatically based on the PDU definition.

       -V causes tgn to print its version number and exit.

       The -s flag allows to specify a random seed that will cause predicatibility of pseudo-random numbers generated by tgn during execution of a
       script. In cases where tgn is used as a protocol fuzzer, this option is useful to be able to re-generate a specific test case.

       -v increases the verbosity level. Additional information may be displayed when the verbosity level is higher.

       The -l flag causes tgn to display all available network speakers and exit. See nexp(1) for a discussion of network speakers.

       The -o flag allows to select a specific network speaker for output. Use the -l option to list available speakers. By default, the "ip"
       speaker (kernel-routed IP packet delivery) is tried first and if it is not available, which can happen if tgn is not run with root
       privileges, the "hex" speaker is used.

       The PDU definition is a string that defines a PDU. It uses libpbuild PDU syntax.

EXAMPLES

	   shell# tgn -o eth0 "ip(dst = 192.168.1.1)/icmp-echo(id = 'random')"

	   shell# tgn "ip(src = 192.168.0.1, dst = <192.168.0.10, 192.168.0.11>,ttl = <1, 2>)/" 
	   "tcp(src = 'random', dst = 22..25, window = 16384,syn, seq = 'random', ack-seq = 0)"

	   shell# tgn -w /tmp/cap -c 5 "ether()/ip(dst = 1.2.3.4++)/icmp-echo(seq = 0++)" 
	   && wireshark /tmp/cap

BUGS

       tgn has not been ported to Microsoft Windows.

VERSION

       This man page is correct for version 1.0 of tgn.

SEE ALSO

       nexp-numspec(1), nexp-payload(1), nexp-ether(5), nexp-gre(5), nexp-ip(5), nexp-mpls(5), nexp(1)

AUTHOR

       Network Expect was written by Eloy Paris <peloy@netexpect.org>. However, Network Expect borrows ideas from lots of Open Source tools like
       Nemesis, Packit, hping, Expect, and Scapy. The Network Expect author is indebted to the authors of these tools for their contribution.

       This man page was written by Eloy Paris.

								 09 September 2009							    TGN(1)
All times are GMT -4. The time now is 01:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy