Transcribing system administration tasks for documentation

Submitted by dag on Wed, 2009/12/23 - 14:10

I always forget this command and it takes a while to search for it, but if you ever start doing administration work on systems and you want to keep track of what you have been doing for documentation, always remember the script command.

I am referencing it here, so I will never forget !

Which is fun because it's

Which is fun because it's what i use for the RPMforge PPC buildlogs : from the Source download to SRPM creation and submit to mock ;-)

Funnily enough, never any

Funnily enough, never any problem remembering this command, I generally remember it about 15mins into a long myriad of commands, and wondering what the hell step #3 was...


It's a shame RH refuse to package scriptreplay (last I heard anyway). Programs like vim and nano tend to render the typescript a bit unreadable with the conventional tools.

GNU screen logs

True! Another good one is to run "screen" with logging turned on - always. (Or PuTTY with logging enabled.) The point is, you'll always have a record of your work, you never know when you need to go back and look at a session to troubleshoot or repeat a particular procedure.

Or use terminal buffer

Aleksey, very true.

I myself use large xterm and putty terminal buffers for being able to go back and recollect something. And by not closing these applications, but rather hibernating the system and reconnecting my sessions so I can even look back at something from the day before, or before the weekend.

I never used screen logging and I can see how that can be useful. However script (in this particular case for documentation) allows you to enable/disable it for certain sessions and log it to separate files easily.

script and yum

The only problem I end up when using 'script' is that it gets really ugly when recording 'yum' or 'wget' download "bars".