redirects all script input from whatever $1 is. Thus, any programs started by this script will also be redirected to whatever $1 is. Your starting ssh in interactive mode, which shouldn't take input from a non-terminal.
You don't need this exec line:
Code:
cat $1 |
while read line
do
ssh ....
done
Or maybe you want to use ssh to execute a command and not run interactively. Is that the case?
Still after running the command this dispalys
Pseudo-terminal will not be allocated because stdin is not a terminal.
Yes that is the case want to execute a command and not running interactively.
I'm trying to figure out how I can run a script "myScript.sh" in such a way that if my remote network connection gets disconnected, the script doesn't stop functioning.
Right now I log in, run "./myScript.sh" and watch my output get pumped to a log file for about 10 hours. Only problem is that... (3 Replies)
Hi.
I was, not too long ago, an OS X home user. One of the things I remember from using the Apple-installed Terminal is: whenever an executable that took more than a split second to do its thing was running, its name would appear in the title bar in a way similar to "Terminal: ssh" or "Terminal:... (0 Replies)
Hi,
I'm new here so please excuse any stupidity that occurs in my post :P
My situation:
Have a java program which I have to run a ridiculous amount of times and put the output data into a text file.
Thought the easiest way to do this would be to delve into the world of scripts.
I am at home... (1 Reply)
What I want my script to do is to run a command in Terminal and close that same Terminal window when the process is complete.
Of course I could ad a delay of 6 seconds to complete the process, but it may not be enough every time.
To simplify my question, this is what I want to achieve.... (9 Replies)
For a small script i want it so that the terminal closes when the script has completed its tasks.
To do so i use at the end if the script the following:
echo "Hello, World!"
echo "Knowledge is power."
echo ""
echo "shutting down terminal in 10 seconds"
exit 10
however the terminal stay's... (3 Replies)
I am new to shell scripting.
I tried to run a simple shell script using Cygwin terminal in Win XP env.
The script I have written is as follows -
#!/bin/bash
a=5
] && echo "true" || echo "false"
But when I execute the script, getting some confusing error. The error I am getting are - ... (3 Replies)
Hi All,
We run Many jobs evryday using Autosys. Sometimes due to various reason we got to run the job from terminal as well (using nohup).
We observed that the job running through terminal(nohup) takes much less time then the autosys (for same job).
What can be the possible reason for such... (1 Reply)
Hello,
I am running a bash script to do an rsync back on a computer running MacOS High Sierra. This is the script I am using,
#!/bin/bash
# main backup location, trailing slash included
backup_loc="/Volumes/Archive_Volume/00_macos_backup/"
# generic backup function
function backup {... (12 Replies)
Discussion started by: LMHmedchem
12 Replies
LEARN ABOUT HPUX
script
script(1) General Commands Manual script(1)NAME
script - make typescript of terminal session
SYNOPSIS
[file]
DESCRIPTION
makes a typescript of everything printed on your terminal. It starts a shell named by the environment variable, or by default and silently
records a copy of output to your terminal from that shell or its descendents, using a pseudo-terminal device (see pty(7)).
All output is written to file, or appended to file if the option is given. If no file name is given, the output is saved in a file named
The recording can be sent to a line printer later with lp(1), or reviewed safely with the option of cat(1).
The recording ends when the forked shell exits (or the user ends the session by typing "exit") or the shell and all its descendents close
the pseudo-terminal device.
This program is useful when operating a CRT display and a hard-copy record of the dialog is desired. It can also be used for a simple form
of session auditing.
respects the convention for login shells as described in su(1), sh(1), and ksh(1). Thus, if it is invoked with a command name beginning
with a hyphen (that is, passes a basename to the shell that is also preceded by a hyphen.
The input flow control can be enabled by setting environmental variable before running Please see section for details on using this envi-
ronment variable.
EXAMPLES
Save everything printed on the user's screen into file
Append a copy of everything printed to the user's screen to file
WARNINGS
A command such as which displays the contents of the destination file, should not be issued while executing because it would cause to log
the output of the command to itself until all available disk space is filled. Other commands, such as more(1), can cause the same problem
but to a lesser degree.
records all received output in the file, including typing errors, backspaces, and cursor motions. Note that it does not record typed char-
acters; only echoed characters. Thus passwords are not recorded in the file. Responses other than simple echoes (such as output from
screen-oriented editors and command editing) are recorded as they appeared in the original session.
When there is no input flow control is not set), there can be some data loss while using However, script(1) can behave unexpectedly, if is
set and is not set.
AUTHOR
was developed by the University of California, Berkeley and HP.
script(1)