I have written a bash shell script. In order to create a log file when I run the script, as well as print the output to the terminal, I call it in the following manner:
This seems to work well. However, I have put some statements in the script to catch errors and exit. I have noticed that when the script exits, the
variable is always 0, regardless of the exit status specified. However, when I call the script the following way that doesn't happen:
Hello:
I'm having the following problem when I try to log in to our Tru64 system, from any machine using root or any other user.
After entering the passowrd I get the following message:
and not being directed to the shell console.
I think it has something to do with the audit process... (2 Replies)
I want to transfer files from ABC server to XYZ server in which i am successful. I would like to create a log file also by the name of current date. For some reason my script gives me an error on my scp -p command and it says LOCAL_LOG_FILE: not found and REMOTE_LOG_FILE not found. Any clues whats... (9 Replies)
Dear all
I am facing a problem that I cannot able to login through 192.168.11.6. I even unplumb it and then plumb it again also, but still facing a problem. Could anyone tell me that what is the meaning of "inet 192.168.11.6 --> 192.168.11.6". I even restart the server two time also ,but still... (7 Replies)
Hi all..
The following set of statements is used in a shell script to ftp a file to a remote machine
I want to redirect the ftp messages thrown by the first ftp statement to a log file. As you can see there is a logic downstream to decide if the ftp was a success or not. But i am not... (5 Replies)
Hi,
I have a problem with my logfile. I am redirecting my output to log file and when iam viewing as text doc it is looking with some nonsense characters...please do help me on this .thank you.
here is my logfile which it is showing different behaviour:
spawn
spawn minicom
Welcome... (6 Replies)
Hi
I have a requirement to write a script to capture all errors in a Logfile and send the file in email.
If there is any error occurred the subject of email will be ERROR , If there are no error occurred the subject of email will be SUCCESS.
So I created a Log file and put the Appropriate... (2 Replies)
Hi,
I am in trouble ... again :wall:
I formating a log file as .txt from Unix (solaris 9) and then I compress it with gzip and I use uuencode and send it in an email.
gzip -c ${fic_report} | uuencode Report_File.gz > ${attachment_file}
my problem is when I received the mail with the... (6 Replies)
Hi,
I have a log file that i'd like to monitor for a string. Now the log file rolls over everytime the server is restarted, so i'm doing a reverse list and then reading the latest log file.
So for the code, the log file is 'test1.txt'.
I check for the string and pipe to black hole (>... (2 Replies)
I need to create shell script (check system ) to display the output to the console and write these output to a log file at the same time.
My shell script is like that
Main() {
....
....
}
MainIt takes about 30s to display all the output to the console.
Then I put this command to the... (4 Replies)
Discussion started by: bobochacha29
4 Replies
LEARN ABOUT MINIX
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)