• United States
Unix Dweeb

Using the script command on Linux to record command line activity

Nov 23, 20215 mins

The script command not only makes a record of what commands you run but also allows you to save the output generated so that you can examine it later or easily turn your command sequences into scripts.

pcw record audio win10 1
Credit: Rob Schultz / IDG

The Linux script command has been around for ages and provides a simple but useful service. It lets you record command line activity – both input and output. This can be very helpful in troubleshooting problems or verifying what was done later by reviewing the commands that were run along with their output.

Even if you’ve used the script command time to time, it offers more options than many of us realize. In this post, we will look at the simplest use of script and some of the options that can make it even more useful.

The easiest way to use the script command is simply to type “script” in the terminal window and press ^d when you want to stop the recording. The output, by default, will be saved in a file called “typescript”. You will see the file name that is used in the first line of output.

$ script
Script started, output log file is 'typescript'.  
$ who
shs      pts/0        2021-11-16 12:10 (
Script done.

Specify a file name

You can provide a more meaningful name if you use a command like the one shown below that adds the filename to the command:

$ script updates
Script started, output log file is 'updates'.     
$ echo running commands
running commands

Script done on 2021-11-16 13:30:19-05:00 [COMMAND_EXIT_CODE="0"]

The content of the updates file would look like this:

$ cat updates
Script started on 2021-11-16 13:35:08-05:00 [TERM="xterm" TTY="/dev/pts/4" COLUMNS="80" LINES="24"]
$ echo running commands
running commands

Script done on 2021-11-16 13:35:25-05:00 [COMMAND_EXIT_CODE="0"]

Notice that the file used to record session activity includes not only the commands typed and the output generated but also the time and date that file recording began and ended.

Append output to an existing file

If you want to append the recording of session activity to an existing file, you can use the -a (or –append) option.

$ script -a updates

Run non-interactively

When you use the -c (or –command) option, the script command runs the command given and non-interactively.

To run a single command and record the interaction, you can specify the command as shown below that uses the -c (or –command) option. Note that quotation marks are needed if the command requires more than one string. The start and end times are not included in the output when this option is used.

$ script -c date
Script started, output log file is 'typescript'.
Thu Nov 18 03:50:06 PM EST 2021
Script done.
$ script -c "find . -name loop -print"
Script started, output log file is 'typescript'.
Script done.

You can also pass a command line to script like this:

$ echo date | script
Script started, output log file is 'typescript'.
$ date
Tue Nov 16 02:02:10 PM EST 2021
Script done.

Run a shell script

In this next example, we use the -c option to run a script and save the interaction in a file named “myloop”.

$ script -c bin/loop2 myloop
Script started, output log file is 'myloop'.
Script done.

Separating input from output

On some Linux systems (like Fedora), the script command also makes it possible to separate input from output in your session recording using the -I (or –log-in) and -O (or –log-out) options. This might more easily allow you to turn the commands saved into a script since they will be in a file without the command output.

$ script -q -I in -O out
$ echo Hello, World!
Hello, World!

The -I (capital “i”) specifies the file for input and the -O (capital “o”) the file for output. Check the script man page to see what options are available to you.

The -q (or –quiet) option keeps the start and end times from being displayed on standard output (generally your terminal window). 

The input file would look like this:

$ cat in
Script started on 2021-11-18 16:01:58-05:00 [TERM="xterm" TTY="/dev/pts/0" COLUMNS="80" LINES="24"]
echo Hello, World!
Script done on 2021-11-18 16:02:06-05:00 [COMMAND_EXIT_CODE="0"]

The output file would look like this:

$ cat out
Script started on 2021-11-18 16:01:58-05:00 [TERM="xterm" TTY="/dev/pts/0" COLUMNS="80" LINES="24"]
$ echo Hello, World!
Hello, World!

Script done on 2021-11-18 16:02:06-05:00 [COMMAND_EXIT_CODE="0"]

Checking script’s version

You can display the version of script that you are running like this:

$ script -V
script from util-linux 2.36.2

Getting help

You can read the man page for the script command or ask for explanations of the script command syntax and options with the command shown below.

$ script -h

 script [options] [file]

Make a typescript of a terminal session.

 -I, --log-in            log stdin to file
 -O, --log-out           log stdout to file (default)
 -B, --log-io            log stdin and stdout to file

 -T, --log-timing        log timing information to file
 -t[], --timing[=] deprecated alias to -T (default file is stderr)
 -m, --logging-format    force to 'classic' or 'advanced' format

 -a, --append                  append to the log file
 -c, --command        run command rather than interactive shell
 -e, --return                  return exit code of the child process
 -f, --flush                   run flush after each write
     --force                   use output file even when it is a link
 -E, --echo              echo input (auto, always or never)
 -o, --output-limit      terminate if output files exceed size
 -q, --quiet                   be quiet

 -h, --help                    display this help
 -V, --version                 display version

For more details see script(1).


The script command is very handy when you want to remember, review or rerun a sequence of commands and output details on a Linux system. While the history command records the commands you enter, script is more thorough in allowing you to review command output as well as the commands that were run.

Unix Dweeb

Sandra Henry-Stocker has been administering Unix systems for more than 30 years. She describes herself as "USL" (Unix as a second language) but remembers enough English to write books and buy groceries. She lives in the mountains in Virginia where, when not working with or writing about Unix, she's chasing the bears away from her bird feeders.

The opinions expressed in this blog are those of Sandra Henry-Stocker and do not necessarily represent those of IDG Communications, Inc., its parent, subsidiary or affiliated companies.

More from this author