Conversation
True story: I never issue "reboot" from the CLI because I once arrow-keyed up too far and rebooted a critical system into an unusable state.

So, if you look at my history, it's always "sleep 5 && reboot" to allow for a frantic "oh sh*t, Ctrl-C!" at the last moment.
10
22
54

@monsieuricon The difference b/w me and you is that you learn from those mistakes.

Oh, and perhaps that your critical systems are slightly more critical than mine 0:-)

0
0
1

@monsieuricon We install the "molly-guard"-package on all our systems after one of our collegues shut down three servers after midnight on his way to bed. 🙄
[A molly-guest is] "originally a Plexiglas cover improvised for the Big Red Switch on an IBM 4341 mainframe after a programmer's toddler daughter (named Molly) tripped it twice in one day." https://en.wiktionary.org/wiki/molly-guard

0
0
0

@monsieuricon thinking back that would have been usefull more than few times blobcatfacepalm

0
0
0

@monsieuricon I've used only `shutdown -r now`, but have never even bothered to `man shutdown` to see what else was possible.

0
0
0

@monsieuricon
That's a good trick! I live in my backscroll, and I've miscounted and run destructive things before. Up up enter rm -rf what now?

0
0
0

@monsieuricon What I try to do is make sure each gnome-terminal/ssh connection to a different machine has a different colour scheme. Since that time the "shutdown -h now" which was supposed to kill the Raspberry Pi shut down the webserver.

0
0
0
@monsieuricon
I guess this is the reason why sudo shutdown gives you a whole minute to cancel it?
0
0
0

@monsieuricon I once managed to mistype 'systemctl reboot postfix' instead of restart. Can't protect myself from everything.

1
0
0
@raimue I mean, you did succeed in restarting postfix. :)
0
0
1

@monsieuricon I normally do shutdown -r where I also provide a reason string. That also gives me time to think about what I am about to do there. And it has got an audit trail.

1
0
0
@chrissicool a laudable practice, but won't save you in the case I described (arrow-up too far by accident and execute it again when you meant to invoke some other command from history).
0
0
0