Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Traveller''s Lunchbox

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 156 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

runscript



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  file­
       name  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 mes­
       sages  from  runscript  ment  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  parameters  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
            '\r'.  <string> can be:
              - regular text, eg 'send hello'
              - text enclosed in quotes, eg 'send "hello world"'

            Within <string> the following  sequences  are  recog­
       nized:
                \n - newline
                \r - carriage return
                \a - bell
                \b - backspace
                \c - don't send the default '\r'.
                \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 ^ chracter, you must prefix it with the \
            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 sta­
            tus 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  let­
            ter 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
            matches one of the specified ones.  If expect encoun­
            ters 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 exam­
       ple  when  you  use  minicom to dial up your ISP, and then
       start a ppp or slip session from a script), try  the  com­
       mand  "!  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  unixlo­
       gin.  Especially  the  last one is a good base to build on
       for your own scripts.


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: 2003/03/30 18:55:42 $      RUNSCRIPT(1)
  

There are several different ways to navigate the tutorial.


Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.11 Seconds