10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am trying to download all files from a user authentication, password protected https site, with a particular extension (.bam). The files are ~20GB each and I am not sure if the below is the best way to do it. I am also not sure how to direct the downloaded files to a folder as well as external... (7 Replies)
Discussion started by: cmccabe
7 Replies
2. UNIX for Dummies Questions & Answers
Hi all, I have a file that contains characters. How do I get total of spesific character from that file and save the count to a variable for doing for calculation.
data.txt
1
2
2
2
2
3
3
4
5
6
7
8
5
4
3
4 (5 Replies)
Discussion started by: weslyarfan
5 Replies
3. Shell Programming and Scripting
Hello,
I have a script that checks every file with a specific extension in a specific directory. The file names contain some numerical output and I am recording the file names with the best n outcomes.
The script finds all files in the directory with the extension .out.txt and uses awk to... (12 Replies)
Discussion started by: LMHmedchem
12 Replies
4. Shell Programming and Scripting
Hi,
I have 80 large files, from which I want to get a specific value to run a Bash script. Firstly, I want to get the part of a file which contains this:
Name =A
xxxxxx
yyyyyy
zzzzzz
aaaaaa
bbbbbb
Value = 57
This is necessary because in a file there are written more lines which... (6 Replies)
Discussion started by: wenclu
6 Replies
5. Shell Programming and Scripting
Hi
i have a file which has mutiple line in it.
inside that i have a pattern similar to this
/abc/def/hij
i want to fine the pattern starting with "/" and get the first word in between the the symbols "/" i.e. "abc" in this case into a variable.
thanks in advance (13 Replies)
Discussion started by: kichu
13 Replies
6. Shell Programming and Scripting
I am trying to use send and receive using expect. the expect_out(buffer) is working fine while it is running it as foreground. But the same script when it is ran as background, the expect_out(buffer) errored out.
Is there any factor influence when we run script in foreground and in background? ... (0 Replies)
Discussion started by: shellscripter
0 Replies
7. Shell Programming and Scripting
Hi,
I have a 3rd party tool on Solaris 8. I am running it thorugh my script but I am not able to capture its output into a variable.
Like, I tried, but did not work.
output=`/usr/bin/myTool`
echo $output
Also, I tried saving in a file but when I run, output is always shown on the... (19 Replies)
Discussion started by: angshuman_ag
19 Replies
8. Shell Programming and Scripting
I am trying unsuccessfully to set into a variable a specific part of command output:
The command output will be as:
line 1: <varied>
line 2: 2 options:
option 1:
Set view: ** NONE **
or
option 2:
Set view: <different_name_of_views_always_without_spaces>
and I would like to get into... (7 Replies)
Discussion started by: orit
7 Replies
9. UNIX for Dummies Questions & Answers
I want to save the contents of a variable to a file. How can that be achieved?
I have tried with:
echo $varname > textfile.txt
but for some reason it does not print anything. (1 Reply)
Discussion started by: carl_vieyra
1 Replies
10. Shell Programming and Scripting
This is what I tried:
vara=${varb}_count
(( vara += 1 ))
Thanks for help (4 Replies)
Discussion started by: pa3be
4 Replies
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)