⇤ ← Revision 1 as of 2020-05-18 10:16:47
Size: 1013
Comment: consoles are nice
|
← Revision 2 as of 2020-05-18 10:17:43 ⇥
Size: 1537
Comment: add links to guides
|
Deletions are marked like this. | Additions are marked like this. |
Line 11: | Line 11: |
Here's the links I read from: * https://www.linuxquestions.org/questions/linux-general-1/disabling-screensaver-on-tty1-virtual-console-439938/ * https://askubuntu.com/questions/138918/how-do-i-disable-the-blank-console-screensaver-on-ubuntu-server * https://unix.stackexchange.com/questions/8056/disable-screen-blanking-on-text-console * https://superuser.com/questions/152347/change-linux-console-screen-blanking-behavior * https://unix.stackexchange.com/questions/8056/disable-screen-blanking-on-text-console |
Sometimes you want to disable the console blanking out, because let's face it, we're mostly using headless servers now.
This seems to be a deeper terminal setting, and not so much a matter of invocation of the getty app itself. Given that, it's a little tricky. Everyone says to just run setterm from your bashrc, but that's not so helpful when NOBODY LOGS IN ON YOUR DAMNED VTs, MOSTLY.
Query with cat /sys/module/kernel/parameters/consoleblank, I don't know how/why this works if it's meant to be a per-VT thing.
You can pass a kernel commandline option, should work well but feels like overkill. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash consoleblank=0"
Put the magic control code inside /etc/issue, because pretty much everyone dumps that to the VT when it gets kicked into action. Super janky but should be perfect: TERM=linux setterm -blank 0 >> /etc/issue
This is really all setterm is doing, which is why you can pipe-append that to /etc/issue: echo -n -e "\033[9;0]"
Here's the links I read from: