The script command is a Unix utility that records a terminal session. The scriptreplay command offers a replay function to script. The session is captured in file name typescript by default; to specify a different filename follow the script command with a space and the filename as such: script recorded_session.
The ttyrec program provides the same kind of functionality and offers several bindings.
Recorded shell sessions can be shared using online services. The advantage of sessions recorded in this format from the usual screencasts is that shell instructions can be easily copy/pasted from the player screen.
Alternatives to Script Command
One of the problems with the script command is that it only allows logging of a child process; and often there is a need to log the command in the current process without spawning a new process, such as when automation of a script is needed that can log its own output. The unix operating system makes this possible by use of pipes and redirects. Consider the following model examples:
LOGNAME="script" rm -f $LOGNAME.p $LOGNAME.log mknod $LOGNAME.p p tee <$LOGNAME.p $LOGNAME.log & exec >$LOGNAME.p 2>&1
The above script records to script.log all output of the "exec" command. However, some interactive programs (such as python) do not display their standard input when run under the resulting shell, although they do when run under the script command.
- Command line interpreter
- Shebang (Unix)
- Bourne shell
- Bourne-Again shell
- C shell
- Python (programming language)
- Filename extension, Command Name Issues section
- Scripting language
- Unix shell
- LinuxInsight - Replaying terminal sessions with scriptreplay
- The instructions at this link no longer work due to the demise of the shelr.tv service. OMG! Ubuntu! - How To Record And Share Terminal Screencasts Quickly
|This Unix-related article is a stub. You can help Wikipedia by expanding it.|