What did I last do?...How to get your command line log

  • Posted on: 6 February 2017
  • By: nblouin
Blog Tags: 

Are you one of those people who prefers interactive jobs over batch submissions?
Or perhaps you work out alot of your workflow kinks on the command line?

...and then 6 months later you have no idea how to repeat what you did?

There is an easy way to capture all of your session on MtMoran for future reference. You can even send the output to a place where you can search them in the future (like MyLogFiles for example).
Rather than relying soley on your history, check out this handy little device called "script". With this command, you can capture your entire terminal session just like the slurm*.out file when running a batch script. Try it out for yourself.


$ man script

SCRIPT(1)                 BSD General Commands Manual                SCRIPT(1)

     script - make typescript of terminal session

     script [-a] [-c COMMAND] [-f] [-q] [-t] [file]

     Script 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.


     -a      Append the output to file or typescript, retaining the prior contents.

     -c 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.

     -f      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’.

     -q      Be quiet.

     -t      Output timing data to standard error. 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 charac-
             ters were output this time. This information can be used to replay typescripts with realistic typing and output delays.

     The script ends when the forked shell 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.  Script works best with commands that do not manipulate the screen, the results are meant to emulate a hardcopy terminal.

     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).

     csh(1) (for the history mechanism), scriptreplay(1).

     The script command appeared in 3.0BSD.

     Script places everything in the log file, including linefeeds and backspaces.  This is not what the naive user expects.

     The script command is part of the util-linux-ng package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/.

Linux                            July 30, 2000                           Linux