Thats a long time to spend in it. Likely stuck trying to quit vim.
That's what a second terminal and "sudo killall -9 vi" is for.
/s in case
While 4 to 5 times doesn't seem a lot, I was able to get back to full speed within two hours of my drives failing resulting in almost zero downtime.
I treat my machines as if they were disposable. Ready to be wiped and reloaded or forgotten on the bus at any moment.
Just the part where I refer to it as easy was supposed to be sarcastic, I suppose. I don’t expect everybody to want to put that effort out.
I think it was Debian that introduced an option to scan all the floppies before starting. I never went back.
ctrl-z, bg, killall vim
;-)
ctrl-z
kill %%
That is in tcsh, I would think bash has %% too.
For years I got emails complaining about this. The common solution was to open up another window and send a kill command- except for most people, they weren't using a multiplexed windowing system, just a dumb terminal. So some folks basically got stuck for hours at a time.
Or use tmux/zellij.