Comment 11 for bug 869017

I'm going to revert this change. We've been carrying this is kbd since wily, so it landed in xenial, but it doesn't even work (VT still blanks here, on a newly-installed system). Debian also drops the files, so to support not blanking the console, we'd need to think of some alternate method of, for example, introducing consoleblank=0 on the kernel command-line (via grub-installer/grub2?). Another option might be to convince kernel people to patch the blankinterval value in vt.c in the kernel sources themselves.

I totally understand why people might want this feature (a server crashing is not nice. It shouldn't happen often, but it's already helpful to have the ILO show an error message and not just a blanked screen). I'm just not sure what the best way to handle it would be in light of the changes in kbd (dropping its init script, and the init script not working in the first place).

In the meantime, please consider adding consoleblank=0 in the command line for your systems. You can do this by adding it to /etc/default/grub.