Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Trying to parse expect_out(buffer)
Top Forums Shell Programming and Scripting Trying to parse expect_out(buffer) Post 302923404 by Chubler_XL on Sunday 2nd of November 2014 03:34:51 PM
Old 11-02-2014
Try this:

Code:
#!/usr/bin/expect -f
set ip "10.199.10."
set arg1 [lindex $argv 0]
append ip $arg1

#
# telnet to E5@ ip=arg1
spawn telnet $ip
set timeout 5
#login
expect "login:" { send "sysadmin\n" }
expect "word:" { send "sysadmin\n" }
#
# list the config files
expect "#" { send "show file contents config\n" }

# extract result into outcome
expect {
    -re "\r\n------+\r\n(.*)#" { set outcome $expect_out(1,string) }
    timeout { puts "config list not found: timing out!!!\n"; }
}

# process each outcome line
foreach line [split $outcome "\n" ] {
   set found [regexp {^(\S+) +config .*} $line match configfile]
   if {$found == 1 } {
       send "delete file config $configfile\r\n"
       expect "#"
   }
}

send "exit\n"
expect EOF

This User Gave Thanks to Chubler_XL For This Post:
imatinkerer
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Help with expect expect_out

This is my simple expect scritpt: #!/usr/bin/expect -f match_max 100000 set timeout -1 spawn telnet $IP expect "#" send -- "shell\r" expect "*Ready*" send -- "init\r" expect "*Ready*" send -- "readsensor \r" expect -- "*" <<< Output of this is a 2 digit number set val... (5 Replies)
Discussion started by: expect_user
5 Replies

2. Shell Programming and Scripting

expect_out(buffer) empty

I have only some info into my buffer, but after a rssi command I see the folowing lines expected into buffer but not present : rssi=-106 rssi=-109 I see in my buffer only the first part of the output, here you are a part of script : #!/usr/bin/expect -f #global expect_out match_max 10000000... (1 Reply)
Discussion started by: ugobale
1 Replies

3. Shell Programming and Scripting

expect_out buffer no such variable running script background

I am trying to use send and receive using expect. the expect_out(buffer) is working fine while it is running it as foreground. But the same script when it is ran as background, the expect_out(buffer) errored out. Is there any factor influence when we run script in foreground and in background? ... (0 Replies)
Discussion started by: shellscripter
0 Replies

4. Shell Programming and Scripting

Problems with expect_out command

expect "#" send "terminal-length 0\r" expect "#" send "show mp cpu\r" expect "#" send "show mp memory\r" expect "#" while {1} { expect "#" send "clear counters\r" sleep 30 ... (0 Replies)
Discussion started by: roh_20022002
0 Replies

5. Programming

[SOLVED] Flushing expect_out(buffer) inside a loop

Greetings, Having an issue with the expect_out(buffer). in a foreach loop through some switches I am grabbing some arp table information and writing it out to output files (1 each for each switch looped through). The first iteration works fine. the second iteration of the loop writes the... (0 Replies)
Discussion started by: SuperSix4
0 Replies

6. Shell Programming and Scripting

Parsing expect_out using regex in expect script

Hi, I am trying to write an expect script. Being a newbie in expect, maybee this is a silly doubt but i am stuck here. So essentially , i want the o/p of one router command to be captured . Its something like this Stats Input Rx : 1234 Input Bytes : 3456 My expect script looks ... (5 Replies)
Discussion started by: ashy_g
5 Replies

7. Shell Programming and Scripting

Expect_out(buffer) works but it doesn't get all lines

Hello "expect" experts I am new at Expect. I have searched for a little while how to capture multiple lines with Expect and I am almost succeeded on that but I don't get all the lines of a command's output that the script executes on a server. Here is how my script works in a nutshell - ... (6 Replies)
Discussion started by: capacho6666
6 Replies

8. Shell Programming and Scripting

Expect_out help!!!

I am trying to read a file via SSH connect and store it to expect_out(buffer). I am a virgin to expect. Help is really appreciated. Wasted almost a day :-( Code is as follows expect "system32>" send "type output.csv"; send "\r"; expect "system32>" set outcome $expect_out(buffer)... (2 Replies)
Discussion started by: cityprince143
2 Replies

9. Programming

Flushing expect_out(buffer)

Can some one tell me how to flush expect_out(buffer)? below is my code expect -re {.*} {} expect "swpackages>*" send -i $con "trial.bat \r" set outcome $expect_out(buffer) expect "*continue*" set prevreport $expect_out(buffer) send "\r \r"; problem is :- I am getting "pre" stuffs... (0 Replies)
Discussion started by: cityprince143
0 Replies

10. Shell Programming and Scripting

Jumbled output in expect_out(buffer)

I have a code like this : set ipv6_acl_max_chars test_acl_max_chars123456a789%s%d2345678ww134rt789qa23456789012345%c89012%a56789012x4r67890test_acl_max_chars1234567890.01234aabcdob34567aBC0 spawn telnet $myip expect "Login:" { send "admin\r" } expect "Password:" {send "admin\r" }... (0 Replies)
Discussion started by: ylucki
0 Replies

LEARN ABOUT DEBIAN

ovs-parse-leaks

ovs-parse-leaks(8)						Open vSwitch Manual						ovs-parse-leaks(8)

NAME

       ovs-parse-leaks - parses OVS leak checker log files

SYNOPSIS

       ovs-parse-leaks [binary] < log

DESCRIPTION

       Many  Open  vSwitch  daemons  accept a --check-leaks option that writes information about memory allocation and deallocation to a log file.
       ovs-parse-leaks parses log files produced by this option and prints a summary of the results.  The most interesting part of the output is a
       list of memory blocks that were allocated but not freed, which Open vSwitch developers can use to find and fix memory leaks.

       The  log  file must be supplied on standard input.  The binary that produced the output should be supplied as the sole non-option argument.
       For best results, the binary should have debug symbols.

OPTIONS

       --help Prints a usage message and exits.

BUGS

       The output can be hard to interpret, especially for a daemon that does not exit in normal operation.  Using  ovs-appctl(8)  to  invoke  the
       exit command that some Open vSwitch daemons support sometimes helps with this.

       ovs-parse-leaks	usually  incorrectly  reports one or more ``bad frees of not-allocated address'' errors at the beginning of output.  These
       reflect frees of data that were allocated before the leak checker was turned on during program initialization.

Open vSwitch							    August 2010 						ovs-parse-leaks(8)
All times are GMT -4. The time now is 02:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy