This post appeared originally in our sysadvent series and has been moved here following the discontinuation of the sysadvent microsite

Ever wanted to record a log of an interactive console session? Easy, just use the script utility. It’s probably already present on your system, no installation required.

To start recording, run script --timing=script.tim script.log. This spawns a new shell, recording stops when you exit from it.

To replay the log, run scriptreplay script.tim script.log. It is also possible to speed up or slow down the playback speed. For example, in order to play back the recording at half of the original speed, use scriptreplay script.tim script.log 0.5. Ctrl+S pauses the playback, Ctrl+Q resumes.

The nice thing about script is that it records everything that happens on the console, it’s not just a simple log of invoked commands. If you open a text editor like vi in the recorded session, you’ll be able to see exactly how and where you navigate the cursor, exactly how and when text was changed - including any typos that were later corrected, and so on.

For the full documentation, check out the manual pages script(1) and scriptreplay(1).

Tore Anderson

Senior Systems Consultant at Redpill Linpro

Tore works with infrastructure at Redpill Linpro. Joining us more than a decade ago as a trainee, Tore is now responsible for our network architecture and operations.

Why automate Ansible

Ansible can be used for many things. There are only a few things I have on my bucket list of things I would like to do, where Ansible cannot help me.

One of my most urgent things to handle was the increasing complexity of Ansible, its configuration and in particular the role development. As I got deeper into Ansible, more and more factors needed to be taken into consideration when setting up a role: the role structure, linting issues, molecule ... [continue reading]

Comparison of different compression tools

Published on December 18, 2024

Why TCP keepalive may be important

Published on December 17, 2024