3 ms·
I go so far as to log all sessions, everything that comes across the screen. Sometimes it's a lifesaver or just convenient to be able to grep through everything
by add-sub-mul-div 3y ago
I go so far as to log all sessions, everything that comes across the screen. Sometimes it's a lifesaver or just convenient to be able to grep through everything to find a specific command, sql query, their output, etc.
One time long ago I wiped out a long crontab by using -r instead -e and got a perfect recent copy from my terminal history, so no harm done.
- Gerlo 3y agoCan you elaborate on what you mean by "everything that comes across the screen?" Does this include the outputs from your commands? If so, what do you use to do this?
- add-sub-mul-div 3y agoI use SecureCRT which has a session logging feature: https://www.vandyke.com/products/securecrt/index.html https://www.vandyke.com/products/securecrt/index.html Yes, it includes both commands entered into the terminal and also all output or whatever gets put on the screen.
- deleted 3y ago[deleted]
- eternityforest 3y agoWow, I didn't even know -r existed! Last time I touched a crontab was a few years ago when I was migrating them to timer units. The classic UNIXy stuff really does not try to hold your hand at all, so that level of logging seems pretty reasonable on systems like that.