expect TCL script

10 More Discussions You Might Find Interesting

1. Red Hat

Issue in installing expect and Tcl

Hi I need to install expect in redhat. through net I came to know that I must install tcl too in order to make expect work. I have downloaded both packages but not able to install # ls -lrt total 3720 18:33 tcl8.4.20-src.tar.gz 18:33 expect5.45.3.tar.gz 18:40 expect5.45.3...

2. Shell Programming and Scripting

Convert my shell script into expect/tcl

hi experts, how will i convert the first part of my script into expect or tcl since shell script cannot be embedded into expect script ? i have 100+ servers in my serverlist. how will i call or declare it in expect or tcl ? #!/usr/sbin/expect -f serverlist=`cat $1` for i in serverlist...

3. UNIX for Dummies Questions & Answers

Expect/Tcl help

hi, I am new in Expect. I have a question about expect timeout. suppose I have a structure of expect { ".."{ send"............"} timeout{ ............... } } The silly question is if I reach timeout, how can I store the error message showing on the screen to...

4. Shell Programming and Scripting

TCL/Expect not working as expected

I am having an issue with TCL\Expect; I am passing arguments via the commandline that are read in via "lrange $argv". One of those var's is a password with characters that need to be escapaed, after escaping them an hitting enter expect is placing curly braces around my password... why?! ...

5. Shell Programming and Scripting

Help with TCL/Expect in Solaris 5.3

I'm having this problem with a very simple tcl expect script that is running on Solaris 5.3 with TCL version 8.4.7 and expect version 5.0. below is the simplified version of the code snippet, which I think has everything to illustrate the problem, the full version is at the very bottom in...

6. Shell Programming and Scripting

tcl/expect

Can someone identify what is the problem here?. no children while executing "exp_wait -nowait -i -1" (procedure "logOptions" line 45) invoked from within "logOptions" (procedure "doExecute" line 98) invoked from within "doExecute" (procedure "main" line 32) ...

7. Shell Programming and Scripting

Tcl expect HELP

In the following "for" loop I assume the the script will expect "anyway", "first" NOT in any paticular order and send "yes" when there found, breaking out of the loop when "$prompt" is found. The way it is working is like 3 individual expect lines, and they MUST be in cronological order. ANY help...

8. UNIX for Dummies Questions & Answers

Expect/Tcl help?

Does anyone know of an expect/tcl forum that is as helpful as this one is for shell scripting? Or if anyone has any expect knowledge, can you please provide some guidance on how to write to a local error log based on output from a ssh session? I have something like this: foreach host...

9. Shell Programming and Scripting

Expect with tcl/tk

hai all, i have an tcl script in which i have been reading the DUT Command prompt of an cisco switch as DUT Command Prompt : cisco* and running the test case of stp now the problem is if i have given any blank space in between the cisco or at the startup then the Expect is not identifying the...

10. Shell Programming and Scripting

TCL/Expect project questions

I am rewriting the first big script project I ever coded to clean up some issues, mainly my really clumsy bash code, and to migrate to TCL/Expect. I have a couple of questions that I could use some help with. 1.) The script needs to know where it is located. I realize that I could use "find /...

LEARN ABOUT XFREE86

script

SCRIPT(1)							   User Commands							 SCRIPT(1)

NAME

       script - make typescript of terminal session

SYNOPSIS

       script [options] [file]

DESCRIPTION

       script makes a typescript of everything displayed on your terminal.  It is useful for students who need a hardcopy record of an interactive
       session as proof of an assignment, as the typescript file can be printed out later with lpr(1).

       If the argument file is given, script saves the dialogue in this file.  If no filename is given, the dialogue is saved in  the  file  type-
       script.

OPTIONS

       -a, --append
	      Append the output to file or to typescript, retaining the prior contents.

       -c, --command command
	      Run  the	command rather than an interactive shell.  This makes it easy for a script to capture the output of a program that behaves
	      differently when its stdout is not a tty.

       -e, --return
	      Return the exit code of the child process.  Uses the same format as bash termination on signal termination exit code is 128+n.

       -f, --flush
	      Flush output after each write.  This is nice for telecooperation: one person does `mkfifo foo;  script  -f  foo',  and  another  can
	      supervise real-time what is being done using `cat foo'.

       --force
	      Allow  the  default output destination, i.e. the typescript file, to be a hard or symbolic link.	The command will follow a symbolic
	      link.

       -q, --quiet
	      Be quiet (do not write start and done messages to standard output).

       -t[file], --timing[=file]
	      Output timing data to standard error, or to file when given.  This data contains two fields, separated by a space.  The first  field
	      indicates  how  much  time elapsed since the previous output.  The second field indicates how many characters were output this time.
	      This information can be used to replay typescripts with realistic typing and output delays.

       -V, --version
	      Display version information and exit.

       -h, --help
	      Display help text and exit.

NOTES

       The script ends when the forked shell exits (a control-D for the Bourne shell (sh(1)), and exit, logout or control-d (if ignoreeof  is  not
       set) for the C-shell, csh(1)).

       Certain interactive commands, such as vi(1), create garbage in the typescript file.  script works best with commands that do not manipulate
       the screen, the results are meant to emulate a hardcopy terminal.

       It is not recommended to run script in non-interactive shells.  The inner shell of script is always interactive, and  this  could  lead	to
       unexpected  results.   If  you  use  script in the shell initialization file, you have to avoid entering an infinite loop.  You can use for
       example the .profile file, which is read by login shells only:

	      if test -t 0 ; then
		  script
		  exit
	      fi

       You should also avoid use of script in command pipes, as script can read more input than you would expect.

ENVIRONMENT

       The following environment variable is utilized by script:

       SHELL  If the variable SHELL exists, the shell forked by script will be that shell.  If SHELL is not set,  the  Bourne  shell  is  assumed.
	      (Most shells set this variable automatically).

SEE ALSO

       csh(1) (for the history mechanism), scriptreplay(1)

HISTORY

       The script command appeared in 3.0BSD.

BUGS

       script places everything in the log file, including linefeeds and backspaces.  This is not what the naive user expects.

       script  is  primarily  designed for interactive terminal sessions.  When stdin is not a terminal (for example: echo foo | script), then the
       session can hang, because the interactive shell within the script session misses EOF and script has no clue when to close the session.  See
       the NOTES section for more information.

AVAILABILITY

       The  script  command  is  part of the util-linux package and is available from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils
       /util-linux/>.

util-linux							     June 2014								 SCRIPT(1)

Shell Programming and Scripting