People tend to get immersed once they start their session with terminals or powershell. The underlying reasons can vary from trying to troubleshoot an issue to installing a new feature or just making a quick status checks. However, one action can lead to another and before we know it, something is broken!<\/p>\n\n\n\n
If you know what the situation like that is, you definitely want to record your session when you go on messing around with critical systems next time. I will describe tools for linux and windows in this post. <\/p>\n\n\n\n
For linux, script<\/a> is a useful tool which comes pre-installed in most of the distributions. Basic usage of script is to call the command with a filename next in which you want to record the log of your session.<\/p>\n\n\n\n user@localhost:~$script session.log After completing your session, you can simply type exit or send \u2018Ctrl+D\u2019 key combination to terminate the logging.<\/p>\n\n\n\n user@localhost:~$exit Script logs your session in ANSI format which includes the color output of your command output. You can use ansi2txt<\/a> or ansi2html<\/a> to convert the output file to your ease of read.<\/p>\n\n\n\n
Script started, file is session.log
user@localhost:~$<\/p>\n\n\n\n
exit
Script done, file is session.log<\/p>\n\n\n\n