When you spend Friday night and half of Saturday debugging a "server problem" that was caused by operator error two days ago, and them not owning up to it on the spot has just made the problem significantly worse.
Show this thread
-
Oh it gets better. Storage snapshots show a few lines of .bash_history mysteriously disappearing... The next day. Someone's getting fired.
Show this thread
Just forgot about the .viminfo entries pointing exactly at the .bash_history line numbers that were removed.
-
-
The suspense is killing me, this is better than Agatha Christie ;-)
-
Not much more left here really. I know which Yubikey was used to log in. The sad thing is I'm pretty sure the culprit knows me, and I didn't expect him to make such an amateurish attempt at hiding his screwup. He should've known better.
- Show replies
New conversation -
-
-
1. ssh xxxx@yyyy 2. unset HISTFILE 3. screw up something 4. ???? 5. PROFIT! (Still you can know who logged in and how much time, but at least no history for bash or vim
)Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.