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:
In the output above, my expect script looks for: "system:"
What I want to capture is: "7.0(7)N1(1)" or what ever is actually returned.
I have tried using the $expect_out(0,string) without success. I have used $expect_out(buffer), but that captures way more data than I'm looking for and really don't know how to select data that gets sent to the buffer.
Thanks in advance for any advice.
Last edited by RudiC; 04-20-2016 at 05:11 PM..
Reason: Added (i)code tags.
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... (0 Replies)
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)
hi
i am writing an expect script to automate su command, my script goes like this...
#!/usr/local/bin/expect --
set password
set env_var
spawn su UNAME
expect "password:"
send "$password\r"
expect "env"
send "setenv PATHVAR $env_ver\r"
expect "env"
send "echo \$PATHVAR"
expect eof ... (2 Replies)
Hello hello, did a quick search and didn't turn up anything helpful. I've got a book I'm sure has the answers, but I don't think I'll have time to finish it before this all has to work, so here goes~ if this isn't a good place to post and someone could direct me to another forum I'd appreciate... (1 Reply)
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)
Hi
I am programing a expect script on debian, I connected to a firewall to get configuration copy via telnet or ssh but Because of firewall show configuration console wait and print --More-- need press space key at least 100.Help me please.
firewall output like this :(
This output isn't... (3 Replies)
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)
hi,
i have a problem with my expect script, here is MyScript:
#!/usr/bin/expect
set pass
set c
set command
spawn sudo $command
expect "assword"
send "$pass\r"
expect eof My problem is that when i execute MyScript with the command : "./MyScript mypassword apt-get_install_git"i get... (6 Replies)
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)
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
LEARN ABOUT DEBIAN
textdump
TEXTDUMP(4) BSD Kernel Interfaces Manual TEXTDUMP(4)NAME
textdump -- textdump kernel dumping facility
SYNOPSIS
options KDB
options DDB
DESCRIPTION
The textdump facility allows the capture of kernel debugging information to disk in a human-readable rather than the machine-readable form
normally used with kernel memory dumps and minidumps. This representation, while less complete in that it does not capture full kernel
state, can provide debugging information in a more compact, portable, and persistent form than a traditional dump. By combining textdump
with other ddb(4) facilities, such as scripting and output capture, detailed bug information can be captured in a fully automated manner.
FORMAT
textdump data is stored in a dump partition in the same style as a regular memory dump, and will be automatically extracted by savecore(8) if
present on boot.
textdump files are stored in the tar(5) format, and consist of one or more text files, each storing a particular type of debugging output.
The following parts may be present:
ddb.txt Captured ddb(4) output, if the capture facility has been used. May be disabled by clearing the debug.ddb.textdump.do_ddb
sysctl.
config.txt Kernel configuration, if has been compiled into the kernel. May be disabled by clearing the debug.ddb.textdump.do_config
sysctl.
msgbuf.txt Kernel message buffer, including recent console output if the capture facility has been used. May be disabled by clearing the
debug.ddb.textdump.do_msgbuf sysctl.
panic.txt Kernel panic string, if the kernel panicked before the dump was generated. May be disabled by clearing the
debug.ddb.textdump.do_panic sysctl.
version.txt Kernel version string. My be disabled by clearing the debug.ddb.textdump.do_version sysctl.
Kernel textdumps may be extracted using tar(1).
CONFIGURATION
The textdump facility is enabled as part of the kernel debugger using options KDB and options DDB. By default, kernel dumps generated on
panic or via explicit requests for a dump will be regular memory dumps; however, by using the textdump set command in ddb(4), or by setting
the debug.ddb.textdump.pending sysctl to 1 using sysctl(8), it is possible to request that the next dump be a textdump.
If at the ddb(4) command line, the commands textdump set, textdump status, and textdump unset may be used to set, query, and clear the
textdump pending flag.
As with regular kernel dumps, a dump partition must be automatically or manually configured using dumpon(8).
EXAMPLES
In the following example, the script kdb.enter.panic will run when the kernel debugger is entered as a result of a panic, enable output cap-
ture, dump several useful pieces of debugging information, and then invoke panic in order to force a kernel dump to be written out followed
by a reboot:
script kdb.enter.panic=textdump set; capture on; show allpcpu; bt;
ps; alltrace; show alllock; call doadump; reset
In the following example, the script kdb.enter.witness will run when the kernel debugger is entered as a result of a witness violation,
printing lock-related information for the user:
script kdb.enter.witness=show locks
These scripts may also be configured using the ddb(8) utility.
SEE ALSO tar(1), ddb(4), tar(5), ddb(8), dumpon(8), savecore(8), sysctl(8)HISTORY
The textdump facility first appeared in FreeBSD 7.1.
AUTHORS
The textdump facility was created by Robert N. M. Watson.
BSD December 24, 2008 BSD