O
The behaviour described comes directly from the Linux kernel, apparently it's from a distant past when text terminals with visualizing devices that needed to be kept out of fire were connected to such cans.See how long the Physician Terminal Extinguishes when there is no user input into it, it is possible to look at the contents of the file /sys/module/kernel/parameters/consoleblank:$ cat /sys/module/kernel/parameters/consoleblank
600
This file is only available for reading, changing the design, rewriting it, you can't. The value in it is seconds, that is, in an example, the console will go out in 10 minutes.To deactivate this conduct globally and permanently, a line should be added consoleblank=0 to kernel parameters in grub configuration and reboot the LOs (not forget about update-grub After editing. For example:$ cat /etc/default/grub | grep -v '#'
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=7
GRUB_DISTRIBUTOR=lsb_release -i -s 2> /dev/null || echo Debian
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX="consoleblank=0"
After reloading, it appears that the nucleus parameters were considered and accepted:$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.6.0-040600-generic root=UUID=544c13df-3ff3-47ba-94cc-407e414c6906 ro consoleblank=0
And the eclipse of the console changed:$ cat /sys/module/kernel/parameters/consoleblank
0
Modify this parameter for the summer, without reloading, by team setterme.g.: setterm -blank 0 or even so: setterm -blank 0 -powerdown 0 -powersave offBut there are two whole "B"s:It only works if the team setterm Introduce the physical console.Ctrl+Alt+F1and when injected through ssh not workingOn the Internet, they say that behavior setterm Changes from the core to the core and from the distributive to the distributive, that is, it's not a universal way.