4 ms·

Why ssh? You have several virtual terminals available at Ctrl+Alt+F1/F2/etc. right?

• zdkl 9y ago
  I've had systems where those would not respond, but ssh did. I still don't understand why and it bothers me.
• sevensor 9y ago
  That works sometimes, and when it works I can usually get X unstuck without a reboot. But sometimes X gets stuck in a way that makes me unable to switch to another virtual console. Then ssh becomes my only recourse, and the only way to kill X is to reboot. This has only happened to me on systems with nvidia graphics, although it doesn't seem to matter whether I'm using nouveau or proprietary drivers.
  • pritambaral 9y ago
    > But sometimes X gets stuck in a way that makes me unable to switch to another virtual console This is the situation where I recommend the Magic-SysRq[0] keys. Alt+SysRq+r (on a system where /proc/sys/kernel/sysrq is configured) transfers keyboard control back to the kernel. There are other Magic-SysRq keys. My personal favourite is the one that invokes the OOMKiller; and there's one for remounting all filesystems read-only, and one for unconditionally rebooting the system. [0]: https://en.wikipedia.org/wiki/Magic_SysRq_key https://en.wikipedia.org/wiki/Magic_SysRq_key
    • sevensor 9y ago
      How have I been using Linux all these years without knowing this? Thank you!