Make expect exit the UNIX script in erreneous condition
Hi,
I am writing a menu driven program using shell script. THe script will be collecting data by logging into the other servers and bringing back the data to home server to process it and accordingly issue commands. TO automate commands execution , I am using expect script. However I am not able to understand , how to do error handling with expect script
I tried using the code tags . Somehw there is some issue . Hence pasting the code
Last edited by Don Cragun; 12-28-2015 at 03:29 PM..
Reason: Add CODE tags.
from my main script, i am calling an expect script. there are a lot of conditions in the Expect script and it can have any exit value based on success or failure of the Expect Script. how can i check the exit status of Expect scritp in the main script. (1 Reply)
Hi All,
I am stuch in a script where a for loop is running to execute some commands for some values.
Now my problem is i have to have an if condition that if the first iteration is successful then it has to exit the for loop otherwise it has to continue normally.
my code is this:
for... (5 Replies)
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)
Hi all,
I'm trying to run the sipp simulator in crontab but after some attempt I came to the conclusion that for some reason this isn't possible (maybe due to sipp interactive nature).
This is confirmed by these posts.
Now I'm trying to launch sipp from an expect script that runs in crontab.
... (0 Replies)
Hello all, I created the below script....and it seemed to be working fine. My problem is i want the script to ignore rest of the things if my condition is not met but do not exit....
#!/bin/ksh
###########################
###########################
# Set name of the listener, this... (2 Replies)
All
i am new to linux, and try to have a simple expect script to ssh then telnet to the network equipment, and exit itself. but dont know why i hang at the last $
#!/usr/bin/expect
set timeout 10
set arg
set arg1
spawn ssh -l UserA 1.1.1.1
expect "assword:";
send "PasSwOrD\r";... (1 Reply)
Hi,
I am using Solaris OS,
I want to handle an occasional expression in expect script while logging into a remote server with ssh.
In normal scenario the expected expression is as below,
spawn ssh $user@$ip
expect "assword:"
send "$password\r"
but in a condition when the remote server... (2 Replies)
We have a requirement where in the user needs to select a option 4 from the menu and the putty window should be closed.I tried giving exit 0 ;; and this is only exiting from the script menu and showing back the prompt.Is there a way for this. (2 Replies)
Hi All,
Requirement: The below script should automatically exit at 6pm everyday without manually killing the script
Tried running with the below shell script but found the script was still running when the time was 6:15pm. The script did not exit the while loop at 6pm
The script runs... (6 Replies)
HI
cd ${back_home}
if above back_home does not exist, then script shoul exit. Please let us know how to do that (7 Replies)
Discussion started by: buzzme
7 Replies
LEARN ABOUT DEBIAN
runscript
RUNSCRIPT(1) General Commands Manual RUNSCRIPT(1)NAME
runscript - script interpreter for minicom
SYNOPSIS
runscript scriptname [logfile [homedir]]
DESCRIPTION
runscript is a simple script interpreter that can be called from within the minicom communications program to automate tasks like logging
in to a Unix system or your favorite BBS.
INVOCATION
The program expects a script name and optionally a filename and the user's home directory as arguments, and it expects that it's input and
output are connected to the "remote end", the system you are connecting to. All messages from runscript meant for the local screen are
directed to the stderr output. All this is automatically taken care of if you run it from minicom. The logfile and home directory parame-
ters are only used to tell the log command the name of the logfile and where to write it. If the homedir is omitted, runscript uses the
directory found in the $HOME environment variable. If also the logfile name is omitted, the log commands are ignored.
KEYWORDS
Runscript recognizes the following commands:
expect send goto gosub return !
exit print set inc dec if
timeout verbose sleep break call log
OVERVIEW OF KEYWORDS
send <string>
<string> is sent to the modem. It is followed by a '
'. <string> can be:
- regular text, e.g. 'send hello'
- text enclosed in quotes, e.g. 'send "hello world"'
Within <string> the following sequences are recognized:
- newline
- carriage return
a - bell
- backspace
c - don't send the default '
'.
f - formfeed
^ - the ^ character
o - send character o (o is an octal number)
Control characters can be used in the string with the ^ prefix (^A to ^Z, ^[, ^ ^], ^^ and ^_). If you need to send the ^ character,
you must prefix it with the escape character.
Also $(environment_variable) can be used, for example $(TERM). Minicom passes three special environment variables: $(LOGIN), which is
the username, $(PASS), which is the password, as defined in the proper entry of the dialing directory, and $(TERMLIN) which is the
number of actual terminal lines on your screen (that is, the statusline excluded).
print <string>
Prints <string> to the local screen. Default followed by '
'. See the description of 'send' above.
label:
Declares a label (with the name 'label') to use with goto or gosub.
goto <label>
Jump to another place in the program.
gosub <label>
Jumps to another place in the program. When the statement 'return' is encountered, control returns to the statement after the gosub.
Gosub's can be nested.
return
Return from a gosub.
! <command>
Runs a shell for you in which 'command' is executed. On return, the variable '$?' is set to the exit status of this command, so you
can subsequently test it using 'if'.
exit [value]
Exit from "runscript" with an optional exit status. (default 1)
set <variable> <value>
Sets the value of <variable> (which is a single letter a-z) to the value <value>. If <variable> does not exist, it will be created.
<value> can be a integer value or another variable.
inc <variable>
Increments the value of <variable> by one.
dec <variable>
Decrements the value of <variable> by one.
if <value> <operator> <value> <statement>
Conditional execution of <statement>. <operator> can be <, >, != or =. Eg, 'if a > 3 goto exitlabel'.
timeout <value>
Sets the global timeout. By default, 'runscript' will exit after 120 seconds. This can be changed with this command. Warning: this
command acts differently within an 'expect' statement, but more about that later.
verbose <on|off>
By default, this is 'on'. That means that anything that is being read from the modem by 'runscript', gets echoed to the screen. This
is so that you can see what 'runscript' is doing.
sleep <value>
Suspend execution for <value> seconds.
expect
expect {
pattern [statement]
pattern [statement]
[timeout <value> [statement] ]
....
}
The most important command of all. Expect keeps reading from the input until it reads a pattern that matches one of the specified
ones. If expect encounters an optional statement after that pattern, it will execute it. Otherwise the default is to just break out
of the expect. 'pattern' is a string, just as in 'send' (see above). Normally, expect will timeout in 60 seconds and just exit, but
this can be changed with the timeout command.
break
Break out of an 'expect' statement. This is normally only useful as argument to 'timeout' within an expect, because the default action
of timeout is to exit immediately.
call <scriptname>
Transfers control to another scriptfile. When that scriptfile finishes without errors, the original script will continue.
log <text>
Write text to the logfile.
NOTES
If you want to make your script to exit minicom (for example when you use minicom to dial up your ISP, and then start a PPP or SLIP session
from a script), try the command "! killall -9 minicom" as the last script command. The -9 option should prevent minicom from hanging up the
line and resetting the modem before exiting.
Well, I don't think this is enough information to make you an experienced 'programmer' in 'runscript', but together with the examples it
shouldn't be too hard to write some useful script files. Things will be easier if you have experience with BASIC. The minicom source code
comes together with two example scripts, scriptdemo and unixlogin. Especially the last one is a good base to build on for your own scripts.
SEE ALSO minicom(1)BUGS
Runscript should be built in to minicom.
AUTHOR
Miquel van Smoorenburg, <miquels@drinkel.ow.org> Jukka Lahtinen, <walker@netsonic.fi>
User's Manual $Date: 2007-10-07 18:13:51 $ RUNSCRIPT(1)