strange expect script behavior, or am i misunderstanding expect scripting? Post: 302266553

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Misunderstanding of sort behavior

Hi everyone, I use the sort from the 5.3.0 coreutils package. I have a file consisting in 5 fields separated by a single space, with no leading or trailing blanks. I want to sort it first according to the 4th field, which contains integers (some of them negative), and secondly on the second...

2. UNIX for Dummies Questions & Answers

Strange expect problem

Hi I'm writing a script which calls an expect script to retrieve configuration files for network devices. I want to avoid using TFTP to transfer the configs if possible and so I'm redirecting the screen output to a text file. This is the expect script: #!/usr/local/bin/expect set...

3. Shell Programming and Scripting

Expect Scripting Help

Hi All, I am trying to connect a router using Expect scripting. But my script shows error.One more thing after the command telnet localhost 2000 we should press ENTER KEY once before the command prompt asks for "enable" and password.Please help correctiong my script. #!/usr/bin/expect -- ...

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 script strange behaviour

Hi people, I'm having some strange behaviour with an 'expect' script. spawn csession blah expect "Username: " send "userblah\r" expect "Password: " send "passwordblah\r" interact When I execute the script as root it runs perfectly. However, when executed as any other...

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

Calling another expect script inside an expect script

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

8. IP Networking

IP and expect scripting

Hi I am new to IP configuration and using expect script I have a requirement like I need to write a expect script that can ssh to a remote machine(linux1) using password which already has IP, once logged inside machine need to reboot remote machine(linux1) and again login to same remote...

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

10. UNIX for Beginners Questions & Answers

Expect scripting issue, works interactively when doing commands in cli, does not work in script

Hi; problem may be obvious, simple but I have to say it is somehow not easy to locate the issue. I am doing some word extracting from multiline text. Interacting in CLI seems to work without issues. First step is to add multiline text to a variable. expect1.1> expect1.1> set...

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