Windows expect


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Windows expect
# 1  
Old 01-10-2008
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 happen? In UX it would be aomething like:

proc T1 {} {
set EXITCODE [format "NO root prompt\n" ]
send_user $EXITCODE
exit -1
}

set timeout 5

expect {#*} {send "root\r"} \
timeout {T1}

If "#" wasn't found in 5 seconds, the program would fail and the log would report "NO root prompt" Smilie
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

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

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

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

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

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

6. Shell Programming and Scripting

Expect for Windows

To All, I have installed ActiveState Active Tcl 8.4.16.0, I have a need for Expect on Windows, whereas, it is close to Epect/UX, it has differences. I am having trouble with the following command: # set X this works well in Expect/UX trying the same command in Expect/Windows, I get the... (8 Replies)
Discussion started by: dave_m
8 Replies
Login or Register to Ask a Question
posix_fadvise(2)						System Calls Manual						  posix_fadvise(2)

NAME
posix_fadvise(), posix_fadvise64() - file advisory information SYNOPSIS
Parameters fd The open file descriptor to which the fadvise operation applies. offset The begining of the specified range as a positive, byte offset. len The length of the specified range in bytes. advice Specifies advice to be applied to range. DESCRIPTION
The function is used to advise the system about the expected behavior of the application with respect to the data in the file associated with the open file descriptor, fd, starting at offset and continuing for len bytes. The specified range need not currently exist in the file. If len is zero, all data following offset is specified. It should be noted that the effect of all hints is cumulative for a given file object. All hints will be removed on processing the last close of the file object. The function may be used for large file access by a 32-bit application built with set to 64. The advice parameter is used to convey the hint to be applied to the data and may be one of the following values: Specifies that the application has no advice to give on its behavior with respect to the specified data. It is the default characteristic if no advice is given for an open file. Specifies that the application expects to access the specified range of data sequentially from the lower offsets to higher offsets. Specifies that the application will expect to access the specified specified range of data in a random order. Specifies that the application will expect to access the specified range of data in the near future. Specifies that the application will expect that it will not access the specified range of data in the near future. Specifies that the application will expect to access the specified range of data once and then not reuse it thereafter. These values will be defined in RETURN VALUE
Successful completion. Failure. is set to indicate the error. ERRORS
If the service fails, is set to one of the following values: The fd argument is not a valid file descriptor. The fd argument is associated with a pipe or FIFO. The posix_fadvise operation is not supported by the underlying file system. The value of advice or one of the other input values has been found to be invalid. A designated hint is not supported by the underlying file object. EXAMPLES
AUTHOR
was derived by HP from the IEEE POSIX 1003.1-2001 Standard. SEE ALSO
fadvise(2), fcntl(2), fadvise(5), fcntl(5). STANDARDS CONFORMANCE
posix_fadvise(2)