3 ms·
This happened when I was at Google, but it was an accident. On someone's last day they ran rm -rf / to wipe their desktop machine. I can't remember whether the
by throwaway11teen 10y ago
This happened when I was at Google, but it was an accident.
On someone's last day they ran rm -rf / to wipe their desktop machine. I can't remember whether they typed it into the wrong terminal window or had mounted an external filesystem somewhere deep under their home directory and forgot about it, it was something like that. They wound up wiping some unfathomably large amount of data (I think most of a data center) before noticing what they'd done.
There were backups, but it was still a huge hassle.
- vmp 10y agoI managed to do that one time but on a much smaller scale (home server). Forgot about my network mounts, rm -Rf, noticed that it was taking longer than expected to delete just a few dirs... "oh crap." :) Luckily I run zfs with zfs-auto-snap on my home server so everything was back the way it was after a quick 'zfs restore'.
- dba7dba 10y agoOops. Wrong terminal. Always a fear of mine. I always try to pause for a second before I run a command like that.
- tedunangst 10y agoEasy solution: start a new terminal.
- darkarmani 10y agoYou could change the color of your login prompt as a visual indicator.
- tracker1 10y agoI once left a "production" connection string in my local config while fixing a bug in my last few days on a job, this got checked into source control (yeah, configuration in source control is bad)... a couple weeks after I left, someone had used that connection string to connect to the database server, and truncated a table.... needless to say, there were some things that changed after that.
- tracker1 10y agoThe someone in question was another developer on that team, who thought they were working against the dev db server.