|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
EXPECT help with full buffer(?), or other available solutions
Post 302526405 by toeharp on Tuesday 31st of May 2011 12:04:39 PM
05-31-2011
Hey Chubler_XL ~ your post worked perfectly, thanks!!
I think I follow what you did - like other posts I've read, it's appending the buffer to a variable prior to file write... unlike other posts I've read, you're doing this per \r - also, unlike other solutions I've seen, this one worked the first time
Thanks again!
I think I follow what you did - like other posts I've read, it's appending the buffer to a variable prior to file write... unlike other posts I've read, you're doing this per \r - also, unlike other solutions I've seen, this one worked the first time
Thanks again!
|
|
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi Group,
I am struggling to increase buffer size of expect,
sometimes after increasing the buffer size, expect captures all my expected output, sometimes not, :-(
I tried
match_max 700000
set expect_out(buffer) {}
Could anybody guide me for any solution.
HTH,... (1 Reply)
Discussion started by: jaduks
1 Replies
2. 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
3. Shell Programming and Scripting
Hi All,
I have to write one expect script to login to one system.
I am using
set timeout -1
match_max 100000
spawn ssh root@hostname
Now when I do spawn ssh to that host it send some warning message and one challenge
Challenge: 111-2345
I need to read this challenge value and has... (1 Reply)
Discussion started by: Lokesh Agrawal
1 Replies
4. 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
5. Shell Programming and Scripting
Hello everyone!
This is the situation:
I execute this command from a bash script:
telnet 10.99.246.14 6001 >> output.txt
The question is:
How I do to execute this command and empty the buffer when is full?
The script is always running.
Thanks a lot! (2 Replies)
Discussion started by: bobbasystem
2 Replies
6. Shell Programming and Scripting
My cron file. Copied $PATH
# Minute Hour Day of Month Month Day of Week Command
SHELL=/bin/ksh
PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/perl/lib:/perl/lib/lib/perl5:/perl/scripts:.:/perl/lib/local:/home/popeye:/temp
0... (3 Replies)
Discussion started by: popeye
3 Replies
7. Shell Programming and Scripting
I have written an application in Tcl-Expect which spawns minicom and
sends and receives data via the serial port. Sometimes i see that the
application receives control characters along with human readable data.
A search on the internet tells me that the control characters are
nothing but the VT... (0 Replies)
Discussion started by: cityprince143
0 Replies
8. UNIX for Beginners Questions & Answers
Hi,
I am capturing command's output on remote host using Expect. The problem is that the command line arguments also getting print with the output in file and also need to print last two relevant columns (percentage used and its mounted point).
The output of $exp->before() buffer is :df... (1 Reply)
Discussion started by: suneet17
1 Replies
LEARN ABOUT FREEBSD
ddb
DDB(8) BSD System Manager's Manual DDB(8) NAME
ddb -- configure DDB kernel debugger properties SYNOPSIS
ddb capture [-M -core] [-N -system] print ddb capture [-M -core] [-N -system] status ddb script scriptname ddb script scriptname=script ddb scripts ddb unscript scriptname ddb pathname DESCRIPTION
The ddb utility configures certain aspects of the ddb(4) kernel debugger from user space that are not configured at compile-time or easily via sysctl(8) MIB entries. To ease configuration, commands can be put in a file which is processed using ddb as shown in the last synopsis line. An absolute pathname must be used. The file will be read line by line and applied as arguments to the ddb utility. Whitespace at the beginning of lines will be ignored as will lines where the first non-whitespace character is '#'. OUTPUT CAPTURE
The ddb utility can be used to extract the contents of the ddb(4) output capture buffer of the current live kernel, or from the crash dump of a kernel on disk. The following debugger commands are available from the command line: capture [-M core] [-N system] print Print the current contents of the ddb(4) output capture buffer. capture [-M core] [-N system] status Print the current status of the ddb(4) output capture buffer. SCRIPTING
The ddb utility can be used to configure aspects of ddb(4) scripting from user space; scripting support is described in more detail in ddb(4). Each of the debugger commands is available from the command line: script scriptname Print the script named scriptname. script scriptname=script Define a script named scriptname. As many scripts contain characters interpreted in special ways by the shell, it is advisable to enclose script in quotes. scripts List currently defined scripts. unscript scriptname Delete the script named scriptname. EXIT STATUS
The ddb utility exits 0 on success, and >0 if an error occurs. EXAMPLES
The following example defines a script that will execute when the kernel debugger is entered as a result of a break signal: ddb script kdb.enter.break="show pcpu; bt" The following example will delete the script: ddb unscript kdb.enter.break For further examples, see the ddb(4) and textdump(4) manual pages. SEE ALSO
ddb(4), textdump(4), sysctl(8) HISTORY
The ddb utility first appeared in FreeBSD 7.1. AUTHORS
Robert N M Watson BUGS
Ideally, ddb would not exist, as all pertinent aspects of ddb(4) could be configured directly via sysctl(8). BSD
December 24, 2008 BSD