Hacker News new | ask | show | jobs
by yardie 3671 days ago
Use screen instead. Ctrl-a and "H" to enable and the same to disable. Log is saved in user directory as screen.<session>

That way I have control of when I log and what gets logged. And way easier to find than hunting for dot files.
1 comments
blastrat 3671 days ago
Yours is a good additional idea, but it is in no way a substitute. You might want to look at some history you forgot to log. Having intentional logging on top of comprehensive logging is like markup metadata, very handy too.

it makes me sad when everybody doesn't see the same things the same way. I'm just waiting now for systemd to disable bash history in favor of logging in binary form all mouse rolls intermixed with key clicks till it wipes it all out when you log out in case yours is a student account on a shared university machine. Don't worry, a GUI editor for it all is on the wishlist.

link
yardie 3671 days ago
6 of one, half dozen of another. It really depends on how you see things. For security reasons we've disabled logging. And users don't access servers at the shell anyway so no need for it there. We log app usage in app.

I find screen logging a bit more useful than shell logging. Shell only records the commands sent and not the result. Screen records everything including interactive like nano.

link
blastrat 3671 days ago
the most precious thing to a computer should be the human input, that's the thing that your brain worked on and that's what primarily should be recorded. (that's what source code is) Computers are deterministic, replaying your input should yield the same output again.

That is why it is soo important to save .bash_history (seriously, that's not a dot file you should be searching hard for)

saving other things are "nice to haves"

link