06-13-2007
Zazzybob writes some cracking articles - he's a good read.
But that solution may be a bit heavyweight in this case. The core of zazzybob's script is based around a command called "script" if you type "script" it will then log everything in your terminal until you ctrl+d out of it. See the man page for more details, but it should be as simple as typing "script" as you start working, and "CTRL+D" when you're finished.
Alternatively, tools like PuTTY have an option to record a transcript of their sessions.
-c
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am trying to find a way to check the current status of a file. Such as some cron job processes are dependent on the completion of others. if a file is currently being accessed / modified or simply open state I will wait until it is done being processed before attempting the next process on that... (3 Replies)
Discussion started by: Gary Dunn
3 Replies
2. UNIX for Dummies Questions & Answers
Hello All!
Does anyone know of a nice way to log commands in solaris 8.
What I need is a program or script that saves any command that a user does in solaris command prompt. So when Steven logs in on a system, it should record everything he does, from an ls to exit with timestamps. I've been... (6 Replies)
Discussion started by: dozy
6 Replies
3. Linux
I have the need to record some step by step instructions to help with instruction in using Fedora Core 3. I was wondering if there are any ways to capture X or VNC activity to a video file. It can be any of the most common formats (MPEG, DiVX/ViDX, Ogg Theora, etc...) Does anyone know of any apps... (3 Replies)
Discussion started by: deckard
3 Replies
4. Shell Programming and Scripting
is there anyway to tell when an activity is happening on a file.
i'm talking about something deeper than what ls -l can give.
when i say activity, i want to know exactly when any commands was run on a specific file. i.e, did anyone run the mail command on this file. did anyone cat this... (2 Replies)
Discussion started by: Terrible
2 Replies
5. BSD
Hi,
The output of the cat ttys on a free BSD m/c
console none unknown off secure
#
# Serial terminals
# The 'dialup' keyword identifies dialin lines to login, fingerd etc.
ttyd0 "/usr/libexec/getty std.9600" unknown on secure
ttyd1 "/usr/libexec/getty std.9600" dialup off
ttyd2... (0 Replies)
Discussion started by: mlalitha
0 Replies
6. UNIX for Dummies Questions & Answers
:confused:Hi
This was installed on the Linux box a few weeks back by a guy that no longer works for us. All worked fine until last week. Now when we connect its just a blank screen with no icons.
I get a whole bunch of errors when starting the service too:
Tue Feb 23 14:29:45 2010
... (1 Reply)
Discussion started by: wbdevilliers
1 Replies
7. Shell Programming and Scripting
I am trying to figure a way to have a log file and still keep the output in the terminal in a script.
The example below logs to a file nicely but i still want the output in the terminal as well
#!/bin/bash
#Create a log
exec >> /path/to/my/logfile
echo "hello world"
Any help would be... (3 Replies)
Discussion started by: dave100
3 Replies
8. Shell Programming and Scripting
My intention is to log the output to a file as well as it should be displayed on the console > I have used tee ( tee -a ${filename} ) command for this purpose. This is working as expected for first few outputs, after some event loggin nothing is gettting logged in to the file but It is displaying... (3 Replies)
Discussion started by: sanoop
3 Replies
9. Solaris
Dear all,
i have two users user1 and user2 i want force user1 to login first by user2 and then su - user1
i want to prevent logging user1 from console directly (5 Replies)
Discussion started by: maxim42
5 Replies
10. Linux
When unlocking a Linux server's console there's no event indicating successful logging
Is there a way I can fix this ?
I have the following in my rsyslog.conf
auth.info /var/log/secure
authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies
SCRIPT(1) BSD General Commands Manual SCRIPT(1)
NAME
script -- make typescript of terminal session
SYNOPSIS
script [-akq] [-t time] [file [command ...]]
DESCRIPTION
The script utility makes a typescript of everything printed 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 all dialogue in file. If no file name is given, the typescript is saved in the file typescript.
If the argument command is given, script will run the specified command with an optional argument vector instead of an interactive shell.
The following options are available:
-a Append the output to file or typescript, retaining the prior contents.
-k Log keys sent to program as well as output.
-q Run in quiet mode, omit the start and stop status messages.
-t time
Specify time interval between flushing script output file. A value of 0 causes script to flush for every character I/O event. The
default interval is 30 seconds.
The script ends when the forked shell (or command) exits (a control-D to exit 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. The script utility works best with commands that do not
manipulate the screen. The results are meant to emulate a hardcopy terminal, not an addressable one.
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).
HISTORY
The script command appeared in 3.0BSD.
BUGS
The script utility places everything in the log file, including linefeeds and backspaces. This is not what the naive user expects.
It is not possible to specify a command without also naming the script file because of argument parsing compatibility issues.
When running in -k mode, echo cancelling is far from ideal. The slave terminal mode is checked for ECHO mode to check when to avoid manual
echo logging. This does not work when in a raw mode where the program being run is doing manual echo.
BSD
January 22, 2004 BSD